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

•C. SAP ABAP Connection: This is what you need to use to combine data from a non-sap system and an InfoCube of your SAP BW powered by SAP HANA system using SAP Data Warehouse Cloud. You can use an SAP ABAP connection to connect to your SAP BW system and access the InfoCube data as a remote table. You can then join this remote table with the data from the non-sap system that you have already loaded into SAP Data Warehouse Cloud using a graphical view12.

References:

•1 https://help.sap.com/doc/00f68c2e08b941f081002fd3691d86a7/release/en-US/0c9d6f0a6c4a4b8e8b3f7e5c0a3d6f9d.html

•2 https://help.sap.com/doc/00f68c2e08b941f081002fd3691d86a7/release/en-US/5c9a6c8b6c4a4b8e8b3f7e5c0a3d6f9d.html

•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

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. Forexample, 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.

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

SAP Data Warehouse Cloud is a cloud-based data service that enables business users to create agilemodels 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

•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

•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

•A. SAP Data Services: This tool can leverage the Write Interface for DataStore objects (advanced) to push data into the inbound table of DataStore objects (advanced) using RFC or HTTP calls. This can improve the performance and flexibility of data integration scenarios12.

•B. SAP Landscape Transformation Replication Server: This tool can leverage the Write Interface for DataStore objects (advanced) to push data into the inbound table of DataStore objects (advanced) using RFC or HTTP calls. This can improve the performance and flexibility of data replication scenarios13.

References:

•1 https://help.sap.com/docs/r/107a6e8a38b74ede94c833ca3b7b6f51/2.0.6/en-US/8127edbcf2fa488ba04dfc1751d5261d.html

•2 https://blogs.sap.com/2020/08/17/sap-bw-4hana-write-interface-enabled-adso-connected-to-a-3rd-party-tool/

•3 https://help.sap.com/docs/r/107a6e8a38b74ede94c833ca3b7b6f51/2.0.4/en-US/8127edbcf2fa488ba04dfc1751d5261d.html

•C. Accelerated SAP BW/4HANA implementation using ready-made models: This is an advantage of using SAP BW/4HANA business content. Business content provides a preconfigured set of application-specific information models based on consistent metadata in SAP BW/4HANA. It can be used without adjustment, be adjusted or enhanced by the customer, or serve as a template to help the customer create his own data models. This can speed up the implementation process and reduce the development effort12.

•D. Ability to combine business content objects with custom-defined objects: This is an advantage of using SAP BW/4HANA business content. Business content objects can be integrated with custom-defined objects using CompositeProviders or other modeling tools. This can enable flexible and agile data modeling and analysis according to the customer’s specific needs13.

References:

•1 https://www.sap.com/documents/2020/06/3cbbd4de-9a7d-0010-87a3-c30de2ffd8ff.html

•2 https://help.sap.com/docs/SAP_BW4HANA_CONTENT/06e872f914a44d77b6c692b0273ca400/20b4b01f5baf46af8fbd439c741adf00.html

•3 https://help.sap.com/docs/SAP_BW4HANA/107a6e8a38b74ede94c833ca3b7b6f51/f851415842154 e59a5f038e458b97a0b.html

•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