General Objective : For Polymer Additives, for the same product, the material code is different depending on the sourcing.

Today the sourcing management for these materials is done in DIP using a supersession. 

This is done in 3 steps :

1/ A supersession is done in DP => Forecast on 1 code only

2/ in DIP, the netting is done with data (Forecast and Order Book) grouped on the "main" code.

It is as if the netting was done at Product Group@shipto level.

3/ The final demand after netting can be splitted on the different codes with Proration % input by the user (monthly bucket)

→ The sales requirements for each material@shipto is recalculated. /!\ Order book is considered as a minimum for each material, except if the cancel order option has been ticked.

A condition allows to filter the relevant SKU  = Multisourced customer

A SKU is flagged as Multisourced customer if :

• Its Product Group*Site is linked to several MPS
• Its Product Group*Site has substituted items in DP

More details in this doc

Design in DIP :

Example for one Product group * Site : 

For other explanations and examples, see the linked wiki page in the user's Wiki :

f. Supersession PA - multiple codes for sourcing management