C_HAMOD Exam Questions: Free SAP System Tasks [2026]

Step-by-Step Execution:

1. Select the Union node combining your data sources.
2. Add a new target column (e.g., AMOUNT_TYPE) to the union output.
3. Right-click the newly created target column and select Manage Mappings.
4. Enter a distinct constant value for each underlying data source to explicitly tag them.
5. Deploy the view and use the constant column in your query filter to trigger pruning.

Example Values:

• Target Column: AMOUNT_TYPE
• Constant for Source 1: 'Actual'
• Constant for Source 2: 'Plan'

Expected Result: When a reporting tool issues a query with a filter expression specifically requesting AMOUNT_TYPE = 'Actual', the SQL optimizer ignores the 'Plan' data source, saving processing time and resources.

Quick Mistakes:

• Forgetting to explicitly include the constant column in the WHERE clause of the calling query, meaning no pruning will occur and both sources will be processed.
• Confusing explicit constant pruning inside the calculation view with implicit pruning, which requires creating a separate Pruning Configuration Table.

Exam Insight:

• Tests knowledge of performance optimization techniques within calculation views.
• Essential for understanding how the SQL optimizer evaluates union nodes and how explicit tagging restricts data source access at runtime.

Step-by-Step Execution:

1. Open an SQL console connected to your target SAP HANA database.
2. Write the CREATE VIRTUAL TABLE statement.
3. Specify your target local schema and the desired virtual table name.
4. Append the AT keyword followed by the remote source, remote database, remote schema, and remote object names separated by dots.
5. Enclose identifiers in double quotes to preserve case sensitivity.
6. Execute the SQL statement to provision the catalog object.

Example Values:

• Remote Source: EXT_HR_SYS
• Remote Database:
• SQL Syntax: CREATE VIRTUAL TABLE "HR_SCHEMA"."VT_EMPLOYEES" AT "EXT_HR_SYS".""."PUBLIC"."EMPLOYEES";

Expected Result: A new virtual table is successfully created in the local schema. It stores only metadata, allowing local users to run SQL queries that fetch data dynamically from the remote system.

Quick Mistakes:

• Forgetting to enclose the value in double quotes when the remote database or remote schema is not applicable for the adapter type.
• Omitting the target schema name if the session user is not meant to be the default schema owner.
• Running the statement without having the CREATE VIRTUAL TABLE privilege on the specified remote source.

Exam Insight:

• Tests the strict SQL syntax required for creating virtual tables and understanding that the keyword must always be quoted when skipping hierarchical elements like the database or schema name.

Step-by-Step Execution:

1. Open the calculation view and navigate to the Parameters tab in the Semantics node.
2. Open the Input Parameter/Variables Mapping feature by launching the Manage Mapping dialog.
3. Select the mapping type Views for value help for variables/input parameters from the dropdown list.
4. Locate the variable used for the value help view on the left side and the variable defined in the current calculation view on the right side.
5. Drag a line between the left and right side to map them, or click auto-map if the names match exactly.

Example Values:

• Mapping Type: Views for value help for variables/input parameters
• Source Variable (Left): IP_PRODUCT_GROUP (from external Value Help view)
• Target Variable (Right): IP_PRODUCT_GROUP (in main Calculation View)

Expected Result: At runtime, when the user selects a Product Group, this value is passed through the mapping to the value help calculation view, filtering the subsequent list of Products to show only those belonging to the selected group.

Quick Mistakes:

• Selecting "Data Sources" as the mapping type instead of "Views for value help for variables/input parameters".
• Attempting to cross-map an input parameter to a variable (the system strictly requires mapping variables to variables and input parameters to input parameters).
• Leaving the value help pointing to the main calculation view, which forces the system to scan the entire dataset just to populate the prompt list.

Exam Insight:

• Tests the understanding of parameter mapping types and dynamic value help configuration.
• Essential for knowing how to build user-friendly, high-performing cascading prompts without competing with the main calculation view for data processing resources.

Resolution:

1. Right-click the calculation view file in the Explorer pane.
2. Choose Data Preview With Other Database User.
3. Select a standard database user connection that has a defined session client.

Prevention Tip: Use a dedicated database user connection instead of the default technical user when previewing client-dependent models.

Resolution:

1. Open the flowgraph in the graphical editor of SAP Business Application Studio.
2. Select the Projection node and review the filter condition.
3. Wrap the variable name in double dollar signs (e.g., $$P_COUNTRY$$) and redeploy.

Prevention Tip: Always enclose flowgraph variable names in double dollar signs when referencing them in SQL expressions.