You expeCt to have more than 2 billion records as master data references for a characteristic your data model and want to use the high cardinality option. What do you need to Consider in reporting?…

Question

Options

• AThe SID table reference is vald for navigational attributes
• BLocal SID values are created automatically durng reporting, which Can impact the response time.
• CThe High Cardinality property needs to be defined the Composite Provider
• DUsing a hierarchy of this characteristic for navigation wa impact response tine.

• A
  6% (2)
• B
  3% (1)
• D
  92% (33)

Explanation

When High Cardinality is enabled on a characteristic, SAP BW bypasses the standard SID (Surrogate ID) generation process to support values exceeding 2 billion. Hierarchies depend on SID-based navigation internally; without those SIDs being maintained normally, the system must perform costly additional processing during query execution when you navigate via a hierarchy, directly degrading response time - making D the key consideration for reporting.

Why the distractors are wrong:

• A is incorrect because High Cardinality characteristics do not maintain standard SID table entries, so navigational attributes (which rely on SID joins) are not supported in the usual way.
• B is a plausible-sounding distractor, but local SID creation during reporting is not the documented primary impact - it conflates internal processing details with the real concern.
• C is wrong because the High Cardinality property is set on the InfoObject/characteristic itself, not on the Composite Provider; the provider simply inherits it.

Memory tip: Associate "High Cardinality → No stable SIDs → Hierarchy Navigation Hurts." The letter chain H-C → H-N-H (High Cardinality → Hierarchy Navigation Hurts) can anchor this: whenever you skip SID generation to handle massive volumes, hierarchies pay the price at query time.

No community discussion yet for this question.