BW430 - SAP BW/4HANA Modeling Flashcards
~Which of the following guidelines should be considered in an enterprise-wide implementation of BW on HANA?~
- How will the different data models be incorporate
- Utilize the LSA++ layers in the design of the EDW
- Which language and currencies will need to be considered
- What will the system and transport landscape be comprised of
- Which users will be logging onto the system
(+)How will the different data models be incorporate
(+)Utilize the LSA++ layers in the design of the EDW
(+)Which language and currencies will need to be considered
(+)What will the system and transport landcsape be comprised of
-Which users will be loggin onto the system
~All of the points are consideration for enterprise-wide EDW projects except for the user names. Naming of users that will be logging on is a project level activty and not an enterprise-wide consideration.
Read more in the lesson, Defining the Sequence of SAP BW Projects, in course, BW33OH.
Read more in course BW430 SAP BW/4HANA Data Modeling, Unit: Process of Modeling, Lesson: Defining the Sequence of SAP BW Projects.~
~Data model definition is an activity carried out in the realization phase of a BW Project.~
- True
- False
-True
(+)False
~You are correct! Data model definition is carried out in the business blueprint phase of a BW project. Read more in the lesson, Planing the Phases of a SAP BW Projects, in the course, BW33OH.
Read more in course BW430 SAP BW/4HANA Data Modeling, Unit: Process of Modeling, Lesson: Planning the Phases of an SAP BW/4HANA Project.~
~Designing a data model helps to reject requirements that are not feasible.~
- True
- False
(+)True
-False
~You are correct! A data model cannot be designed based on requirements that cannot be realized. Read more in the lesson, Developing a Logical Data Model, in the course, BW430
Read more in course BW430 SAP BW/4HANA Data Modeling, Unit: Process of Modeling, Lesson: Developing an SAP BW/4HANA Data Model.~
~In the SAP BW data model, master data is stored separately in attribute, text and hierarchy tables that are linked together using the surrogate ID (SID).~
- True
- False
(+)True
-False
~You are correct! The link between the different master data tables is the surrogate ID. Read more in the lesson, Listing Tables in the SAP BW Data Model, in the course, BW33OH.
Read more in course, Unit: , Lesson: .~
~Time-dependent and time-independent attributes are stored in the same X table which uses Data From and Data To as key fields.~
- True
- False
-True
(+)False
~Time-dependent attributes are stored in the Y table which uses Data To field in the key. Time-independent attributes are stored in the X table without any dates in the table key. Read more in the lesson, Listing Tables in the SAP BW Data Model, in the course, BW33OH.
Read more in course, Unit: , Lesson: .~
~Which of the following statements regarding internal and external hierarchies are true?~
- Internal hierarchies have no link to Master Data tables
- Internal hierarchies are used to display characteristics without using an external hierarchy
- External hierarchies are defined in Business Explorer Query Designer on the hierarchy tab
- External hierarchies are defined as “external” because the date is sored outside of BW on the OLAP server
- External hierarchies are stored in BW Master Data tables
(+)Internal hierarchies have no link to Master Data tables
(+)Internal hierarchies are used to display characteristics without using an external hierarchy
-External hierarchies are defined in Business Explorer Query Designer on the hierarchy tab
-External hierarchies are defined as “external” because the date is sored outside of BW on the OLAP server
(+)External hierarchies are stored in BW Master Data tables
~Internal hierarchies have no link to master data because they are created “on the fly” when the query result is presented to the user. External hierarchies are stored in BW Master data tables. External hierarchies are not defined in Query Designer, they are stored in the BW hierarchy tables. External hierarchies are external to the query execution and they are not stored in the OLAP server. Read more in the lesson, Using Hirarchies in SAP BW Characteristics in the course, BW33OH.
Read more in course, Unit: , Lesson: .~
~Temporal conditions can be defined on columns of the following data types: timestamp, date, and text.~
- True
- False
-True
(+)False
~Temporal conditions can only be used with data types of timestamp, date, and integer. Temporal conditions on text are not possible. Read more in the lesson, Using Hierarchies in SAP HANA Views, in the course, BW33OH.
Read more in course BW430 SAP BW/4HANA Data Modeling, Unit: Implementing Native SAP HANA Views, Lesson: Modeling Master Data in SAP HANA Views.~
~Unlike the classic star schema where facts are stored in the fact table, in SAP HANA, multiple views may be used to representing the central fact view in a virtual data model.~ -True -False
(+)True
-False
~You are correct! Rather than persisting data in a central fact table, SAP HANA can provide the data using views using a star join. Read more in the lesson, Using Measures in SAP HANA Views, in the course, BW33OH.
Read more in course BW430 SAP BW/4HANA Data Modeling, Unit: Implementing Native SAP HANA Views, Lesson: Modeling Transactional Data in SAP HANA Views.~
~Which of the following is required to perform currency conversion in an SAP HANA informational model?.~
- An inner join is required between the Open ODS View measures and the exchange rate table
- A set of technical tables are required to store currencies and exchange rate types and rates
- Setting a semantic type to a measure so the amount always includes a currency
- Storing the currency and the exchange rate on the day of the transaction will improve perfomance
- An interface to define how the currency conversion should be processed
-An inner join is required between the Open ODS View measures and the exchange rate table
(+)A set of technical tables are required to store currencies and exchange rate types and rates
(+)Setting a semantic type to a measure so the amount always includes a currency
-Storing the currency and the exchange rate on the day of the transaction will improve perfomance
(+)An interface to define how the currency conversion should be processed
~Modeling currency conversion in SAP HANA includes the use of the technical tables for currencies and rates, setting of a semantic type to include currency and an interface needs to be used to determine how the conversion is to take place. Inner joins of a measure with the exchange rate table is not possible. Storing of daily exchange rates alongside transactional date would not be an effective design. Read more in the lesson, Using Measures in SAP HANA Views, in the course, BW33OH. Read more in course BW430 SAP BW/4HANA Data Modeling, Unit: Implementing Native SAP HANA Views, Lesson: Modeling Transactional Data in SAP HANA Views.~
~Non-cumulative key figures are values calculated according to a particular period of time. The value is then incremented or decremented based on an inflow or outflow.~
- True
- False
(+)True
-False
~You are correct! Non-cumulatives do not cumulate as normal key figures because their value is dependent upon a stipulation of a time for the accumulation to make sence. Examples of non-cumulatives are stock on hand at month end or opening balances in the general ledger. Read more in the lesson, Creating Key Figures for Non-Cumulatives, in the course, BW33OH. Read more in course BW430 SAP BW/4HANA Data Modeling, Unit: Advanced Modeling in SAP BW/4HANA, Lesson: Defining Inventory Scenarios.~
~Which of the following are the correct terminology about hierarchies?~
- An entity in a hierarchy is called a node
- Nodes that have no parents are called orphan nodes
- Nodes that have no children nodes are called leaf nodes or leaves
- A relationship between a node and its parent node is called a family tree
- A hierarchy with leaves on different levels is an unbalanced hierarchy
(+)An entity in a hierarchy is called a node
-Nodes that have no parents are called orphan nodes
(+)Nodes that have no children nodes are called leaf nodes or leaves
-A relationship between a node and its parent node is called a family tree
(+)A hierarchy with leaves on different levels is an unbalanced hierarchy
~You are correct! In a hierarchy, entities are called nodes, childless nodes are leaves, and hierarchies with leaves on different levels are unbalanced. Nodes without parents are called root nodes. A relationship between a parent and child node is a link. Read more in the lesson, Using Hierarchies in SAP HANA Views, in the course, BW33OH. Read more in course BW430 SAP BW/4HANA Data Modeling, Unit: Implementing Native SAP HANA Views, Lesson: Modeling Master Data in SAP HANA Views.~
