compounded infoobject

[Former Member]

Hi,

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.

Thanks

[Former Member]

Hi,

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:

ZORG_MAP

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)

Masterdata:

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.

rgrds,

Mathijs

[Former Member]

Hi Mathijs,

Your idea seems good but in my scenario Purchasing Grp needed is a navigational attribute (i have also the characteristic in the cube, this was done to model at posting and present situation) so how can I instruct the system to use the navigational attribute in the compounding ?

Thanks

[Former Member]

Hi Merzak,

Can you share the complete scenario? What Object is exactly chaning? And based on what objects is it changing?

Rgrds,

Mathijs

[Former Member]

Hi Mathijs,

Here is the situation, currently in SAP ECC each customer have multiples sales representatives, and every sales representative visits the customer only for some specific product categoies, so for a specific product category and a specific client there is only one sales  representative.

Sales representative is designed as “partner function” in the customer master data (table KNVP)

The relation between a sales representative and product categories is N:N and  evolves frequently

In the sales document cube, we have the customer, the sales representative and product, the product category  is a navigational attribute of product.

the pain point is that every time a product category for a customer changes to a new sales representative we have to repost the data, wich is very painful. so the idea is to create a new compounded infoobject with the customer and the product category (navigational attribute of product) as key and the sales representative as attribute of this new compounded infoobject.

Thanks

[Former Member]

Hi Merzak,

I think then its easy. As mentioned, create an InfoObject:

Customer (key)

Product Category (compounded)

Sales Representative (Nav. Attribute).

Enrich your sales document so the Product Category is populated as well and add your new InfoObject in the Cube, populate it with your Customer ID and make Sales Representative available as a nav. attribute.

You'll see that when you insert your new InfoObject (with Product Cat. as compounded value) the Product Category will automatically be added as well, so you cannot go without having Product Category in your Sales Documents.

Rgrds,

Mathijs

[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

Thanks