IBP Demand Adding a new key field in CUSTOMERPRODUCT master data and Modifying the planning Levels?

[former_member588111]

Hi,

In IBP the CUSTOMERPRODUCT master data has the key field of customer ID and product ID. Now for the same customer ID + product ID it can have more than 1 Sales Org. I added a new attribute under the CUSTOMERPRODUCT which is "Sales Org". When loading the master data from BW via CPI, it creates a rejection error due to master data duplication.

My plan is to create a new master data called "Sales Org" and will add this to the compound master data CUSTOMERPRODUCT which will now make 3 key fields (customer+ Product + SalesOrg). However, this will affect the planning levels because i have to make the "Sales Org" as root as well.

The reason why the Sales Org is needed because the sales planners make their input for promotion at the "Sales Org" level.

Has anyone tried to do this? Is this an ideal solution? Please advise.

[former_member367912]

Hi Jerson,

Other approach could be don't change the standard MDT CustomerProduct and create a completely new MDT for eg "CUSTOMERPRODUCTRSALESORG" in which you can make 3 key fields (customer+ Product + SalesOrg).

After this you need to create new planning levels just like it exists for CUSTOMERPRODUCT while in this you need to add extra salesorg as key in planning levels.

Both the approach either using existing CUSTOMERPRODUCT or NEW MDT CUSTOMERPRODUCTRSALESORG will work.

Regards,

Akhilesh Agarwal

[Irmi_Kuntze · Accepted solution]

hi Jerson

I strngly agree with Akhilesh: dont change the standard MDT but create a new one, and with that create new planning levels as weel, I gave done that a couple of times

Nit only is it not possible to change the root of an existing mdt that holds already sata

It is less work to create new than to adjust

And you may run into issues with supply planning if you adjust olanning kevel that are used there

I am not fully sure where to find it officially, but there is a good how-to paper by the Deland Product Management for the topic (maybe in the best practise content?) that describes step by step as this is a common issue

Irmi

[anil_gupta8]

If you make sales org as key then planning level also need to be change key figure data need combination of product customer sales org

I did this for adding ship to customer along with prod and customer and need create new planning level and then to adjust planning level in existing key figure I hope this helps

Anil