nerdexam
SAP

C_BW4HANA_27 · Question #21

You have created a Custom Characteristic with me technical name "COSTOBJ". Depending on the controlling area, you need to have different attribute values assigned. How do you design the model? (1)

The correct answer is A. Compound the characteristic for Controling Area with the characteristic "COSTOBJ". Compounding in SAP BW means a characteristic's key values are only unique in combination with a superior (compound) characteristic. Option A is correct because adding the Controlling Area as the compound characteristic of COSTOBJ means the system treats each COSTOBJ value as…

BW/4HANA Modeling

Question

You have created a Custom Characteristic with me technical name "COSTOBJ". Depending on the controlling area, you need to have different attribute values assigned. How do you design the model? (1)

Options

  • ACompound the characteristic for Controling Area with the characteristic "COSTOBJ"
  • BJoin the characteristic "COSTOBJ" and the Controlling Area in a BW query
  • CDefine Controlling Area as a navigation attrbute for the characteristic "COSTOBJ"
  • DCompound characteristic "COSTOBJ" Rh the characteristic for Controlling Area.

How the community answered

(29 responses)
  • A
    83% (24)
  • B
    3% (1)
  • C
    10% (3)
  • D
    3% (1)

Explanation

Compounding in SAP BW means a characteristic's key values are only unique in combination with a superior (compound) characteristic. Option A is correct because adding the Controlling Area as the compound characteristic of COSTOBJ means the system treats each COSTOBJ value as unique per Controlling Area - allowing different attribute values for the same COSTOBJ key across different controlling areas, which is exactly the requirement.

Option B is wrong because joining in a BW query is a reporting-time workaround, not a data model solution - it doesn't make master data attributes context-dependent by Controlling Area. Option C is wrong because navigation attributes allow you to navigate to related data from a characteristic, but they don't enable the same characteristic key to carry different attribute values depending on another characteristic. Option D reverses the compounding relationship - it would make COSTOBJ the superior characteristic of Controlling Area, which is logically backwards; Controlling Area should be the parent that gives COSTOBJ its context.

Memory tip: Think "parent before child" - the Controlling Area is the parent that gives COSTOBJ meaning, so Controlling Area is compounded into COSTOBJ (not the other way around). If you open InfoObject COSTOBJ and attach Controlling Area there as its compound characteristic, you've done option A correctly.

Topics

#characteristic compounding#custom characteristics#attribute values#controlling area

Community Discussion

No community discussion yet for this question.

Full C_BW4HANA_27 Practice