What are benefits of separating master data from transactional data in SAP BW/4HANA? (2)

Question

Options

• AImprove runtime of staging processes
• BAvoid generation of SID values
• CEnsure referential integrity on your data
• DEnsure high cardinality on your data

• A
  92% (22)
• B
  4% (1)
• D
  4% (1)

Explanation

Separating master data from transactional data in SAP BW/4HANA improves staging runtime (A) because master data changes infrequently - isolating it means transactional loads don't trigger unnecessary reprocessing of stable attributes, texts, and hierarchies, allowing parallel and more targeted loading processes. Referential integrity (C) is enforced because transactional records (e.g., sales figures) are validated against existing master data records (e.g., valid customer IDs), preventing orphaned or inconsistent entries in your data warehouse.

Why the distractors are wrong:

• B is incorrect - SID (Surrogate ID) generation is a core part of BW/4HANA master data processing and still occurs regardless of separation; you cannot "avoid" it this way.
• D is incorrect - cardinality (the number of unique values in a column) is a property of the data itself, not a result of how master and transactional data are architecturally separated.

Memory tip: Think "FAST & CLEAN" - separation makes staging Faster (A) and keeps your facts Clean with valid references (C). Master data is the "dictionary"; transactions are the "sentences" - keeping the dictionary separate means you only update it when needed, and every sentence always points to a real word.

No community discussion yet for this question.