Skip to Content
author's profile photo Former Member
Former Member

compounded infoobject


I need to compound a characteristic (A) with a navigational attribute of another characteristic (B__C)

So if I create the compounded infoobject with A and C, will I need to add C to the infocube or A and B are enough?

The idea avoid having is C in the cube, as with every organizational change we need to repost the data.


Add comment
10|10000 characters needed characters exceeded

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Oct 17, 2015 at 03:33 PM


    Can we make this more pragmatic? What are you trying to achieve? Assuming that i know what your trying to do with an example. Let's say if you have an object "Organization" based on "purchase organziation" and "Purchasing Group". If you don't want "Organizaion" in your cube because he business rules might change, create a new Infobject:


    Organization Mapping (ZORG_MAP) (Key)

    Purchasing Org. (Compounded)

    Purchasing Grp. (Compounded

    Organization (Nav. Attribute)

    Put ZORG_MAP (and compounding objects) in your cube, don't populate ZORG_MAP itself (will remain empty). Load your mappings according to your business rules into the masterdata table of ZORG_MAP. Now make "Organziation" avaiable in your cube as Nav. Attribute in your cube (ZORGMAP__ORGANIZATION).

    Because you use compounding it will automatically show (join) the correct value with the correct transnational data record.

    an Example:

    Transaction data:

    Document Nr Purch. Org. Purch. Grp. ZORG_MAP 1234 XX01 XX1 (empty)


    ZORG_MAP (key) Purch. Org. Purch. Grp. Organization (empty) XX01 XX1 ORGANIZATION A

    Its actually joining on the key: Empty, XX01, XX1.

    Hope this helps.



    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Mathijs,

      the problem is "Product Category" in the new compouned characteristic (C) can change, the correct one is mappend as navigational attribute of material. so the system will populate a wrong SID for C when loading the infocube.

      in the infocube we have :

      material, customer, C, amount

      product category is a navigantional attribute of material

      sales representative is a navigantional attribute of C (C is not mapped for the infocube and is loaded as master data)

      business rules:

      product category of a material can change

      sales representative for a (product category,client) can change