SAP Business Warehouse (BW) Data Modeling Quiz

ZUSERLIST is a custom SAP transaction code designed to retrieve and display user IDs created on a specific date in the BI environment. SU01 is the standard user maintenance transaction but doesn't provide date-filtered listing capability. RSU01 and RSMO are not the correct transactions for this purpose - they serve other functions in SAP systems.

A Data Model provides a conceptual description of data objects, their attributes, and the relationships between them. It's an abstract representation that defines the structure and organization of data independent of any physical implementation. A Data Warehouse is a physical storage system. An InfoCatalog is metadata about available data. An InfoSet is a specific view or dataset definition, not the conceptual model itself.

In SAP BW/BI, aggregates can only be created for InfoCubes. Aggregates are pre-summarized data structures that improve query performance. InfoCubes are the physical data store that supports aggregation. Multiproviders are logical views that combine multiple providers but don't store data. DSOs (DataStore Objects) and Virtual Providers don't support aggregate creation.

SAP InfoCubes have a maximum limit of 16 dimensions including 3 fixed dimensions (Unit, Time, and Point of Delivery). This leaves 13 custom dimensions available for modeling. The 16-dimension limit is a structural constraint in SAP BW architecture. Options B (24), C (20), and D (18) all exceed the actual limit.

A Dimension in SAP data warehousing is a logical grouping of related characteristics that belong together semantically. For example, a 'Customer' dimension might group characteristics like Customer ID, Customer Name, Region, and Industry. Dimensions improve query performance by enabling star schema optimization. A Fact contains key figures. Keyfigures are numeric metrics. Attributes are properties of characteristics.

Virtual Provider InfoCubes are specifically designed for real-time reporting in SAP BW. They allow data to be read directly from the source system without being physically stored in the cube. Standard InfoCubes store data physically and are not real-time capable. Real-time InfoCubes exist but are for planning scenarios, not operational reporting.

The activation queue table (technical table name ends in '_AQ') is specific to standard DSOs (DataStore Objects). It temporarily holds data before activation, when changes are moved from the new table to the active table. Write-optimized DSOs bypass activation entirely. Direct update DSOs also don't use the activation queue mechanism.

Normalization in data modeling is fundamentally about eliminating redundancy and preventing update anomalies. While it can improve performance in some cases, that's not the primary purpose. It's not about aesthetics or complying with multidimensional rules - those are different concerns.

In SAP BW InfoCubes, key figure values in the fact table are linked to dimension records using DIM_IDs (dimension IDs). Each fact record contains DIM_IDs that point to the corresponding SID (surrogate ID) values in the dimension tables. SIDs are used within dimensions, not to link key figures. Semantic IDs are a different concept altogether.

SAP BW InfoCubes have a maximum limit of 233 key figures. This is a hard technical constraint in the system. 254 is a common byte limit but doesn't apply here. The other numbers are incorrect.