SAP C_HANADEV_18 SAP Certified Development Associate - SAP HANA 2.0 SPS06 Exam Practice Test

Answer : C, D

To produce sales value for the month using sales order line items (sales price per item x quantity sold), you can use a calculated column of a calculation view that performs the multiplication of the two columns and applies a transparent filter and a non-equijoin to restrict the data to the desired month. A transparent filter is a filter condition that is applied to the data source of a view node and is propagated to the subsequent nodes. A non-equijoin is a join condition that uses operators other than equality, such as greater than, less than, or between. For example, you can use a transparent filter to filter the sales order line items by the month of the order date, and then use a non-equijoin to join the sales order line items with the sales price table by the order date and the valid from and valid to dates of the sales price.Reference:Transparent Filters,Non-Equijoins,Create Calculated Columns.

Answer : A, C

Filter expressions can be used in a calculation view to restrict or modify the data that is displayed or processed by the view.Filter expressions can be used in the following nodes of a calculation view12:

Aggregation: An aggregation node is a node that applies aggregation functions, such as sum, count, or average, to the data that is passed from the previous node. Filter expressions can be used in an aggregation node to filter the data before or after the aggregation, or to define the aggregation level or the measure attributes. For example, you can use a filter expression to show only the sales data for a specific region or product category, or to calculate the average revenue per customer.

Union: A union node is a node that combines the data from two or more nodes that have the same structure and data types. Filter expressions can be used in a union node to filter the data from each input node, or to filter the data from the output node. For example, you can use a filter expression to exclude the duplicate rows from the union result, or to show only the data that matches a certain condition from each input node.

The other options are not correct because filter expressions cannot be used in these nodes of a calculation view. A star join node is a node that joins a fact table with one or more dimension tables, based on the common key attributes. A star join node does not support filter expressions, but it supports input parameters, which are variables that can be used to filter the data at runtime. A rank node is a node that ranks the data according to a specified order and criteria. A rank node does not support filter expressions, but it supports rank filters, which are conditions that can be used to limit the number or percentage of rows in the rank result.Reference:

SAP HANA Platform, SAP HANA Modeling Guide for SAP HANA Web Workbench, Calculation Views

SAP HANA Platform, SAP HANA Developer Guide for SAP HANA Web IDE, Developing Database Modules, Developing Calculation Views, Using Filter Expressions

Answer : B, C

You can use declare exit handlers in a SQL Script procedure to handle generic SQL exceptions or specific SQL error codes. An exit handler is a custom handler that defines a block of code to be executed when an exception occurs in the procedure. You can declare an exit handler for a generic SQL exception, which is any error that is raised by the database system, such as syntax errors, constraint violations, or division by zero.You can also declare an exit handler for a specific SQL error code, which is a numeric code that identifies the type and severity of the error, such as 301 for unique constraint violation, or 1299 for no data found12.

The other two options, generic SQL conditions and specific SQL conditions, are not valid arguments for declare exit handlers. A condition is a named exception that can be declared by using a condition variable and optionally associated with an SQL error code. A condition can be used to signal or resignal an exception in the procedure, or to register a continue handler, which is a custom handler that defines a block of code to be executed when an exception occurs, but does not exit the procedure.However, a condition cannot be used to register an exit handler, as the syntax requires an SQL error code or a generic SQL exception12.Reference:1:Exception Handling | SAP Help Portal2:Exception Handling Examples | SAP Help Portal

Answer : D

According to the SAP HANA Performance Guide for Developers1, the .hdinamespace file is a JSON resource that defines the naming rules for the run-time objects in a multi-target application. The name parameter specifies the common name-space prefix for the objects, while the subfolder parameter determines whether the name of the sub-folder is added or ignored in the run-time name space. If you want to keep the names of the objects as short as possible, you should set the subfolder parameter to ignore, so that the name of the sub-folder is not appended to the name-space prefix and the object name. For example, if you have a table named CUSTOMERS in a sub-folder named SALES, and you set the subfolder parameter to ignore, the run-time name of the table will be com.sap.hana.example::CUSTOMERS, where com.sap.hana.example is the name-space prefix defined by the name parameter. If you set the subfolder parameter to append, the run-time name of the table will be com.sap.hana.example.SALES::CUSTOMERS, which is longer and more complex.For more information on the .hdinamespace file and the naming rules, see [The HDI Name-Space Configuration File]2and [Run-Time Name Spaces in SAP HDI]3.

Answer : A, C, D

To specify the target currency for currency conversion in calculation views, you can use one of the following methods:

In a column: You can associate the measure with an attribute column that contains the target currency code. For example, if you have a table that stores the sales amount and the currency code for each transaction, you can use the currency code column as the target currency for the sales amount measure.

With an input parameter: You can create an input parameter that allows the user to select or enter the target currency code at runtime. For example, if you want to display the sales amount in different currencies based on the user's preference, you can use an input parameter as the target currency for the sales amount measure.

With a fixed value: You can associate the measure with a fixed currency code that is available in the currency table. For example, if you want to display the sales amount in a single currency, such as USD, you can use a fixed value as the target currency for the sales amount measure.Reference:Associate Measures with Currency,How to perform Currency Conversion in SAP HANA,Implementing Currency Conversion.

Answer : C, D

A calculation view of type ''SQL Access Only'' is a calculation view that is not visible to the reporting tools and does not support multidimensional reporting. However, it can be directly accessed via SQL and used as a modelled data source for another view. This type of calculation view is useful for scenarios where you want to perform complex calculations or transformations on the data, but do not need to expose the result to the end users or analytical applications. You can use the SQL Access Only calculation view as an intermediate step in your data modelling process, and then use another calculation view with data category Cube or Dimension to provide the final output for reporting or analysis. The other options are incorrect because a calculation view of type ''SQL Access Only'' cannot be directly exposed to all client tools or used for multidimensional analysis. These features are only available for calculation views with data category Cube or Dimension.Reference:

Supported Data Categories for Calculation Views- SAP Help Portal

Quick Reference: Calculation View Properties- SAP Help Portal

SAP HANA Modeling Guide for SAP HANA Studio- SAP Help Portal

New Hierarchy SQL enablement with Calculation Views in SAP HANA 1.0 SPS 10- SAP Blogs

HA300 - SAP HANA 2.0 SPS06 Modeling- SAP Training

Answer : D

According to the SAP HANA Developer Guide, a multi join is a join that can be defined only with multi-column join in calculation views. A multi join allows you to join multiple data sources using multiple join conditions. You can specify the join type, the join cardinality, and the join columns for each pair of data sources. A multi join is useful when you need to join data sources that have complex relationships or different granularities. The other options are incorrect, because:

A dynamic join is a join that can be defined with either single-column join or multi-column join in calculation views. A dynamic join allows you to join two data sources using a join condition that is evaluated at run time based on the user input. You can specify the join type, the join cardinality, and the join columns as parameters or variables.

A text join is a join that can be defined with either single-column join or multi-column join in calculation views. A text join allows you to join a data source with a text table that contains language-dependent descriptions of the data. You can specify the join type, the join cardinality, and the join columns as well as the language column and the language code.

A temporal join is a join that can be defined with either single-column join or multi-column join in calculation views. A temporal join allows you to join a data source with a history table that contains time-dependent versions of the data. You can specify the join type, the join cardinality, and the join columns as well as the validity columns and the validity period.