C_BW4H_214 SAP Certified Associate - Reporting, Modeling and Data Acquisition with SAP BW/4HANA Questions and Answers

•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. Use fewer drill-down characteristics in the initial view: This can improve the query performance by reducing the amount of data that needs to be transferred and displayed at the start of the query execution. The user can drill down to more details later if needed1.

•D. Use mandatory characteristic value variables: This can improve the query performance by restricting the data selection to a smaller set of values that are relevant for the user. The user can also change the variable values later if needed1.

•E. Use include functions in the restricted key figures: This can improve the query performance by avoiding unnecessary calculations and aggregations that are done when using exclude functions. Include functions are also more efficient than selections or restricted key figures when filtering data1.

References:

•2 https://blogs.sap.com/2015/04/20/query-performance-optimisation-tips-in-bw-73/

•1 https://blogs.sap.com/2022/02/02/query-performance-optimization-in-bw-few-tips/

•3 https://help.sap.com/doc/00f68c2e08b941f081002fd3691d86a7/2022.12/en-us/0471d0ecea4e4677ba29d9ac1496c24c.html

•4 https://blogs.sap.com/2021/06/02/sap-bw-4hana-performance-optimization-part-i/

•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. 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

•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. Characteristic value: This type of variable can use the SAP HANA Exit processing type to determine default values for variables using an AMDP class implementation. This can improve the performance and flexibility of queries that are generated as external SAP HANA views12.

•D. Hierarchy node: This type of variable can use the SAP HANA Exit processing type to determine default values for variables using an AMDP class implementation. This can improve the performance and flexibility of queries that are generated as external SAP HANA views12.

References:

•1 https://help.sap.com/docs/r/107a6e8a38b74ede94c833ca3b7b6f51/1.0.8/en-US/b77f3073e9d842d6959e03e74dcefa09.html

•2 https://blogs.sap.com/2017/09/29/usage-of-sap-hana-exit-variables-for-a-standard-reporting-scenario/