Explore topic-wise InterviewSolutions in .

Under QUICK Launch, Generate Time Data option allows the consumer to develop the Time data so that it can be employed for designing the Time-based Attribute Views.

When you select Generate Time Data, you will be supplied with two options:

• Gregorian: Mostly the data will be rendered based on From and To years alongside the granularity - Second, Minute, Hour, Day, Month mentioned.
• Fiscal: In this circumstance, the time data will be rendered based on the variant described (some organizations MAY use their time).

Standard TABLES T005T, T005U, T009, and T009B in SAP HANA are needed if you opt for the Fiscal type.

This article is all about learning about SAP HANA and the probable interview-related questions and answers you should be aware of.  We HOPE the article will help you nail your SAP HANA interview.

Useful Interview Resources:

• SAP ABAP Interview Questions
• Coding Practice

To structure and specify the relationships among attributes in a modelling view. HIERARCHIES are implemented.

Companies describe hierarchies for classification of information, letting roll-up and drill-down analysis. For instance, a sales company might assign a salesperson to a COUNTRY and a country is assigned to a region. Then the sales data can be CALCULATED and scrutinized by region, country, or salesperson.

There are two kinds of hierarchies:

• Level Hierarchies are rigid hierarchies, where you can access the root and the child nodes in the defined order. For instance, organizational structures.
• Parent/Child Hierarchies are regarded as value hierarchies, i.e, hierarchies obtained from the value of a node. Such as a BILL of Materials (BOM) includes Assembly and Part hierarchies, and an Employee MASTER record includes Employee and Manager data. The hierarchy can be analyzed on the basis of a selected parent, also, there are scenarios where the child can be a parent.

• MEASURE and Attribute
• Hierarchies
• Parameters/Variables
• New CALCULATED COLUMN.

SAP HANA can gather huge amounts of elaborate DATA from SOURCE systems, into the MEMORY directly, where mapping, synchronization, and translation, can be accomplished in real-time, without the REQUIREMENT for data duplication and pre-aggregations. This allows users to plan rapidly and iteratively using their complete, detail-level data-spending less time collecting and assembling data and more time making the critical decisions that DRIVE their business.

SAP COLLECTIONS Insight backed by SAP HANA lets you ACCESS real-time mobile association and collections account information at any given place and time. It allows you to fix collections issues, better manage your collections efforts, tighten business relationships, and get PAID quickly.

If tables of a SCHEMA for example SCHEMA_ABC are implemented to create the modelling views, then the following SQL statement must be performed before starting any such modelling views.

GRANT SELECT ON SCHEMA SCHEMA_ABC TO _SYS_REPO with the option of GRANT
Consider _SYS_REPO as “the activation guy”. It takes your models and makes the required runtime OBJECTS from them. Thus user _SYS_REPO requires the allowance to choose YOUR tables/views. (If _SYS_REPO user is unable to decide on the tables added in the from-clause of the view-definition, it will FAIL to describe that view). If different customers REQUIRE to choose this view (It is quite obvious this is always the scenario, else the views would not make any sense), then _SYS_REPO ought to have the extra allowance to grant the selection further (with the grant option).

After all your models that access data in your schemas has been activated, _SYS_REPO wants to OFFER you and other users read access to the activated models.

In HANA, there are 3 kinds of SCHEMAS.

• User-DEFINED Schema: These are DEVELOPED by the user, DBA or System Administrator
• SLT Derived Schema: During the configuration of SLT, it DEVELOPS the schema in the HANA system. All the tables imitated into the HANA system are included in this schema
• System Defined Schema: System Defined schemas are provided with the SAP HANA database and include information on the HANA system. _SYS_REPO, _SYS_BIC, _SYS_BI, _SYS_STATISTICS are the system schemas.

• ACTIVATE – Implement the inactive objects.
• Redeploy – Implements the active objects in any of the scenarios:
  • If your RUNTIME OBJECT becomes CORRUPTED or deleted, and you need to build it again.
  • If your runtime problems while object ACTIVATION, and the object status shows active.

When an object is activated, it BECOMES accessible for reporting and analysis. After the view has been SUCCESSFULLY activated, a run-time object is built in the _SYS_BIC schema.

For instance, let’s say there exists a calculation view CV_VIEW1 in package “MyPackage”. After this view is activated, a run time object (column view) will be developed in _SYS_BIC schema having the NAME “MyPackage/CV_VIEW1”. This column view is IMPLEMENTED while PERFORMING the data preview of the calculation view. 

• Run-length ENCODING
• Cluster encoding.
• Dictionary encoding.

The following types of Input parameters are supported.

• Currency: This can be used during currency conversion where the end-user should mention a source or target currency.
• Date: It is Used to get BACK dates from the end-user with the help of a calendar TYPE input box.
• Static List: This can be used during the time the end-user NEEDS to have a setlist of values to select from.
• Attribute Value: If an Input Variable owns this type, it serves a similar purpose as a NORMAL Variable.
• Note: If none of the above is applicable you do not have to mention an Input Variable type. It can be left blank.

With the accessibility of Multi-CORE CPUs, more elevated CPU execution speeds can be attained. 

Furthermore, HANA Column-based storage makes it effortless to perform operations in parallel with the help of MULTIPLE processor cores. 

Data is ALREADY vertically partitioned In a column store. This implies that operations on various COLUMNS can readily be processed in parallel. If numerous columns ought to be explored or aggregated, each of these processes can be assigned to a separate processor core. Additionally, by dividing the column into numerous sections that can be processed by various processor cores, operations on one column can be parallelized. With the help of the SAP HANA database, queries can be accomplished rapidly and parallelly.

• Raw DATA: It shows all ATTRIBUTES ALONGSIDE data in a tabular FORMAT.
• Distinct Values: It shows all attributes alongside data in a graphical format.
• Analysis: It depicts all measures and attributes in a graphical format.

• Modelling studio in HANA executes numerous tasks like:
• States which TABLES are saved in HANA, the FIRST part is to obtain the meta-data and then PREPARE data REPLICATION jobs
• Handle Data Services to GET through the data from SAP Business Warehouse and other systems
• Handle ERP instances connection, the existing release does not support connecting to different ERP instances
• Employ data services for the modelling
• Accomplish modelling in HANA itself, essential licenses for SAP BO data services.

SAP HANA contains an in-memory computing engine and the data is AVAILABLE right away without the need for any backup. During HARDWARE failure or power CUTOFF, to evade the chance of misplacing data, the persistence layer ACTS as a saviour and saves all the data in the hard drive that is not volatile.

• Variables are attached to COLUMNS and are employed for filtering with the help of WHERE clauses. They can just include the VALUES available in the Columns they associate to. Variables do not affect the performance,
• HANA Input parameters are used to drive the execution on the basis of user input. Occasionally, you might not want a variable to simply limit the data of a view. But you might also want to take input from the customer and PROCESS it, returning dynamic data on the basis of the user selection. Input Parameters makes this achievable.