To display the "COUNTRY" of a "CUSTOMER" in a master data report, you need to establish a relationship between these InfoObjects. Below is an explanation of the correct answers:
B. Generate external views for "CUSTOMER", "CITY", "COUNTRY" join them in another calculation viewThis approach leverages SAP HANA's native capabilities to model data relationships. By generating external views for each InfoObject ("CUSTOMER", "CITY", "COUNTRY"), you can create a calculation view that joins these views based on their relationships. This method is particularly useful for real-time reporting and ensures optimal performance by utilizing SAP HANA's in-memory processing.
[: The SAP BW/4HANA Modeling Guide highlights the ability to generate external HANA views for InfoObjects and combine them in calculation views for advanced reporting scenarios., , C. Combine "CUSTOMER", "CITY", "COUNTRY" in a Composite Provider using a sequence of left outer join operatorsAComposite Providercan be used to combine data from multiple InfoObjects or InfoProviders. By defining a sequence ofleft outer joins, you can link "CUSTOMER" to "CITY" and "CITY" to "COUNTRY". This approach is suitable for scenarios where the data resides in different InfoProviders or when you need to create a unified view for reporting., Reference: The SAP BW/4HANA Query Design Guide explains how Composite Providers can use join operators to combine data from multiple sources, enabling complex reporting scenarios., , D. Add "COUNTRY" as a transitive attribute for "CUSTOMER" in InfoObject definitionAtransitive attributeallows you to define indirect relationships between InfoObjects. By adding "COUNTRY" as a transitive attribute of "CUSTOMER", you can directly access "COUNTRY" in reports without explicitly modeling the intermediate relationship with "CITY". This simplifies the reporting process and ensures that the relationship is maintained automatically., Reference: The SAP BW/4HANA InfoObject Modeling Guide describes the concept of transitive attributes and their role in simplifying master data reporting., , Incorrect OptionsA. Include "CUSTOMER" to the rows in the BW Query on "CUSTOMER" activate the Universal Display Hierarchy settingTheUniversal Display Hierarchysetting is used to display hierarchical relationships in a query. However, it does not address the requirement to display "COUNTRY" as an attribute of "CUSTOMER". This option is irrelevant to the scenario., Reference: The SAP BW/4HANA Query Design Guide confirms that Universal Display Hierarchy is specific to hierarchical data and does not apply to attribute relationships., E. Combine "CUSTOMER", "CITY", "COUNTRY" in an Open ODS View using a sequence of associationsWhileOpen ODS Viewssupport associations to model relationships, they are not designed to handle complex attribute relationships like those required in this scenario. Open ODS Views are better suited for real-time reporting on raw data rather than master data attributes., Reference: The SAP BW/4HANA Modeling Guide states that Open ODS Views are limited in their ability to model complex attribute relationships., , ConclusionThe three correct options to realize the scenario of displaying the "COUNTRY" of a "CUSTOMER" in a master data report are:, Generate external views for "CUSTOMER", "CITY", "COUNTRY" and join them in another calculation view., Combine "CUSTOMER", "CITY", "COUNTRY" in a Composite Provider using a sequence of left outer join operators., Add "COUNTRY" as a transitive attribute for "CUSTOMER" in InfoObject definition., These approaches leverage the flexibility and power of SAP BW/4HANA and SAP HANA to model and report on complex master data relationships., ]
