C_BW4H_2404 Sample Questions Answers

An architecture overview model is a high-level diagram that shows the main components and data flows of a solution. It helps to identify the required data sources and how they are connected to the target system. An architecture overview model can also show the main business processes and scenarios that are supported by the solution. An architecture overview model is useful for scoping, planning, designing, and communicating a solution.

•B. ADD: This delta method indicates that the DataSource provides consistent information for this target. It means that the DataSource delivers additive delta records with after images, which are updated directly in the delta queue. This can support sum aggregation for key figures12.

•D. AIE: This delta method indicates that the DataSource provides consistent information for this target. It means that the DataSource delivers additive delta records with after images, which are updated in the extraction queue and then transferred to the delta queue. This can support sum aggregation for key figures13.

References:

•1 https://wiki.scn.sap.com/wiki/display/BI/Delta+type+in+BW+Extractors

•2 https://help.sap.com/doc/saphelp_nw73ehp1/7.31.19/en-US/4f/18f6aa3fca410ae10000000a42189d/content.htm

•3 https://help.sap.com/doc/saphelp_nw73ehp1/7.31.19/en-US/4f/18f6b13fca410ae10000000a42189d/content.htm

The delta merge process is used to transfer data modifications from the delta storage to the main storage in SAP HANA database. It can be initiated in SAP BW/4HANA in the following ways:

•By using a specific process type in a process chain, called Trigger for DB Merge. This process type can be added to a process chain and linked to the loading processes that require a delta merge. The process type allows specifying the object type and name for the delta merge.

•By using the SAP BW/4HANA data load monitor, which is a web-based tool for monitoring and managing data loads. The data load monitor has an option to trigger a database merge for an object after a successful data load.

What is required before you can integrate an HDI Calculation View (data category Dimension) into another HDI Calculation View (data category Cube with Star Join) of the same HDI container?"

A. Create a synonym for the HDI Calculation View (data category Dimension).

B. Build the design time file of the HDI Calculation View (data category Dimension) to generate a runtime object.

C. Create a synonym for the HDI Calculation View (data category with Star Join).

D. Build the runtime object of the HDI Calculation View (data category Cube with Star Join) to generate a design time file.

Answer: B

•B. Reporting is done based on a union of the inbound and active tables: This is a behavior that is specific to the Data Mart DataStore Object modeling property. The query reads data from both the inbound table and the active table of the DataStore object, which means that it is not necessary to activate the data to be able to see all the data. The data read is consistent and stable, since data is only included up to the first inconsistent request12.

•D. The records are treated as if all characteristics are in the key: This is a behavior that is specific to the Data Mart DataStore Object modeling property. No keys can be specified for this type of DataStore object, but when the data is activated, it is grouped according to the aggregation behavior of all characteristics. Therefore, key figures cannot be overwritten and only additive deltas can be loaded12.

References:

•1 https://help.sap.com/docs/SAP_BW4HANA/107a6e8a38b74ede94c833ca3b7b6f51/1961a9b62f054cc5a4f0d98485b82fa9.html

•2 https://help.sap.com/docs/r/dd104a87ab9249968e6279e61378ff66/11.1.0/en-US/9cf20bb96e254f6b9b5bf1c9c1413f35.html

The feature of generating an external SAP HANA view is used to expose SAP BW/4HANA objects as SAP HANA calculation views, which can be consumed by other SAP HANA tools or applications. The following SAP BW/4HANA objects support this feature:

•Open ODS view, which is a flexible object that can be created on top of any source system and can be used as a source for other objects such as CompositeProviders or BW queries. An Open ODS view can have an external SAP HANA view generated automatically during activation or manually using the context menu option Generate External SAP HANA View.

•Composite Provider, which is a powerful object that can combine data from different InfoProviders using join or union operations. A Composite Provider can have an external SAP HANA view generated automatically during activation or manually using the context menu option Generate External SAP HANA View.

•A. High Cardinality is set in InfoObject B: This is an object property that prevents you from changing InfoObject B into a navigational attribute for InfoObject A. A characteristic with high cardinality cannot be used as a navigation attribute for another characteristic, and therefore it cannot have navigation attributes itself12.

•B. Attribute Only is set in InfoObject B: This is an object property that prevents you from changing InfoObject B into a navigational attribute for InfoObject A. A characteristic that is marked as an exclusive attribute can only be used as a display attribute for another characteristic, but not as a navigational attribute. In addition, the characteristic cannot be transferred into InfoCubes34.

•D. Conversion Routine “ALPHA” is set in InfoObject A: This is an object property that prevents you from changing InfoObject B into a navigational attribute for InfoObject A. A characteristic that has a conversion routine cannot have navigational attributes, because the conversion routine would have to be applied to the navigational attributes as well, which is not possible5 .

References:

•1 https://help.sap.com/docs/SAP_BW4HANA/107a6e8a38b74ede94c833ca3b7b6f51/f851415842154e59a5f038e458b97a0b.html

•2 https://help.sap.com/doc/saphelp_nw75/7.5.5/en-US/f8/51415842154e59a5f038e458b97a0b/content.htm

•3 https://help.sap.com/doc/saphelp_scm700_ehp02/7.0.2/en-US/63/f3c416bcbf4730bb86e62ef8a54e17/content.htm

•4 https://answers.sap.com/questions/1149854/difference-display-attribute-and-navigational-attr.html

•5 https://help.sap.com/doc/saphelp_nw75/7.5.5/en-US/42/f93a83ae5546d3a7cfd7ff09e25a2b/content.htm

•https://answers.sap.com/questions/10121838/infoobjects-attributes.html