C_BW4H_2404 SAP Certified Associate - Data Engineer - Data Fabric Questions and Answers

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

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

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.

•SAP Analytics Cloud analytics designer: This tool can help you create web-based dashboards with interactive visualizations using Javascript. You can use the analytics designer to create custom applications that leverage the power of SAP Analytics Cloud models and APIs12.

References:

•1 https://blogs.sap.com/2020/11/05/data-visualization-best-practices-in-dashboard-design-using-sap-analytics-cloud/

•2 https://blogs.sap.com/2021/12/15/sap-analytics-cloud-sac/

•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

•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