SAP C_BW4H_211 SAP Certified Application Associate - Reporting, Modeling and Data Acquisition with SAP BW/4HANA Exam Practice Test

Separating master data from transactional data in SAP BW/4HANA has the following benefits:

• It allows different data load frequency for master data and transactional data, which can improve the performance and flexibility of data loading processes. For example, master data can be loaded daily or weekly, while transactional data can be loaded hourly or near real-time.
• It ensures referential integrity on your transactional data by using SID values that link the transactional data to the master data. This way, the transactional data can be consistent and accurate across different InfoProviders and queries.
• It provides language dependent master data texts that can be displayed in different languages according to the user’s preference. This way, the master data can be more user-friendly and understandable for different audiences.

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. Rank: This node type is only available for graphical modeling of SAP HANA HDI Calculation Views(XS Advanced), but not for SAP HANA Calculation Views(XS Classic). It allows you to rank the data based on a measure and a ranking rule12.

•D. Graph: This node type is only available for graphical modeling of SAP HANA HDI Calculation Views(XS Advanced), but not for SAP HANA Calculation Views(XS Classic). It allows you to model graph data and perform graph operations such as shortest path, neighborhood search, and pattern matching13.

References:

•1 https://help.sap.com/docs/SAP_HANA_PLATFORM/fc5ace7a367c434190a8047881f92ed8/050f14f7a6d94d2da905b0a4072ba546.html

•2 https://help.sap.com/docs/r/e8e6c8142e60469bb401de5fdb6f7c00/2.0.03/en-US/9b9b4b8e0c4d4f0a9c3e7f8a3b5d9b9d.html

•3 https://help.sap.com/docs/r/e8e6c8142e60469bb401de5fdb6f7c00/2.0.03/en-US/e8b26f49218648eaa8e2ce9b54a8b812.html

•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