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

SAP Data Warehouse Cloud is a cloud-based data service that enables business users to create agile models from different sources and access data in real time. Business users can use the graphical user interface or the SQL editor to create data models, join data from various sources, and enrich data with business semantics. Business users can also use SAP Analytics Cloud to visualize and analyze data from SAP Data Warehouse Cloud. SAP Data Warehouse Cloud supports business users by providing self-service capabilities, pre-built business content, and flexible consumption options. References: 123

•Run the program RODPS_OS_EXPOSE in SAP ERP for the Data-Source: This program can enable a generic DataSource in SAP ERP to be used as an ODP_SAP DataSource in SAP BW/4HANA by exposing it to the ODP framework. This allows the data to be transferred via RFC or HTTP calls without using a PSA layer12.

References:

•1 https://blogs.sap.com/2020/12/25/operational-data-provisioning-simplified/

•2 https://help.sap.com/docs/SAP_BW4HANA/107a6e8a38b74ede94c833ca3b7b6f51/c6afacb707764885a6fb62f511c24f34.html

•A. You cannot use navigation attributes for this characteristic: This is a disadvantage of setting the High Cardinality flag for a characteristic. A characteristic with high cardinality cannot be used as a navigation attribute for another characteristic, and therefore it cannot have navigation attributes itself12.

•C. SID numbers are created at runtime which might negatively affect the reporting performance: This is a disadvantage of setting the High Cardinality flag for a characteristic. A characteristic with high cardinality has no persistent SID values and no SID table, which means that the SID numbers are generated on the fly during query execution. This can have a negative impact on the reporting performance, especially if the characteristic is used in filters or aggregations13.

References:

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

•2 https://help.sap.com/docs/SAP_BW4HANA/107a6e8a38b74ede94c833ca3b7b6f51/88a51330c046426091f3730d0c42c0de.html

•3 https://blogs.sap.com/2019/01/14/high-cardinality-characteristics-in-bw4hana/

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.

•D. Flexible Enterprise Data Warehouse Core layer: This is the layer of the layered scalable architecture (LSA++) of SAP BW/4HANA that is designed as the main storage for harmonized consistent data. The Flexible Enterprise Data Warehouse Core layer contains the Corporate Memory and the Quality & Harmonization layers, which are used to store and harmonize data from different sources and systems. The data in this layer is modeled using DataStore objects (advanced) and InfoObjects, and can be accessed by different data marts for reporting and analysis purposes12.

References:

•1 https://help.sap.com/doc/saphelp_nw75/7.5.5/en-US/4a/124597ca771b41e10000000a421937/content.htm

•2 https://help.sap.com/doc/r/dd104a87ab9249968e6279e61378ff66/11.0.8/en-US/0062afefa6db41eaa9460afef1894beb.html