You can NOT turn a display attribute into a navigation attribute. Which setting of this attribute could be the reason? (2)

Question

Options

• ACase-Sensitive
• BHigh Cardinality
• CAttribute Only
• DUseable InfoProvider

• A
  9% (2)
• B
  18% (4)
• C
  73% (16)

Explanation

In SAP BW, two settings on an InfoObject will block its promotion from display attribute to navigation attribute:

C (Attribute Only) flags the InfoObject as usable only as an attribute of another characteristic - it is explicitly excluded from navigation attribute use because navigation attributes must behave like standalone characteristics in the query layer, which "Attribute Only" prevents.

D (Useable InfoProvider) relates to the requirement that a navigation attribute's underlying InfoObject must be capable of participating in the query infrastructure (essentially acting as a virtual InfoProvider). If this capability is absent or conflicting, BW cannot wire up the navigation join that makes the attribute navigable.

A (Case-Sensitive) is a distractor - it only controls string-comparison behavior for master data, with no structural impact on attribute type. B (High Cardinality) is also a distractor - it is a SAP HANA storage/performance hint, not a restriction on how an attribute can be classified.

Memory tip: Navigation attributes need "reporting freedom" - they must act like characteristics in a query. "Attribute Only" explicitly revokes that freedom, and a missing InfoProvider capability removes the infrastructure that makes navigation possible. If either is true, navigation is blocked.

No community discussion yet for this question.