n PROD with diff config for a single indiv customer segment

[former_member585690]

Hi Gurus,

We're using an IS Mill solution on ECC with variant configuration and PDS. CDP has been implemented to carry out a characteristics based planning using std heuristics, SDS & block, CDP allowing to propagate the relevant characteristics values provided at SO level upstream our supply chain.

Problematic:

As in our model, characteristic value assignments for configuration are using multiple values (what is not allowed by CDP), decision was taken when production order are beeing created, to take as reference the SO configuration: it is only a reference = not a separate instance that would be freely adjustable. Production order covering Sales requirement are thus having a static instance of configuration, at any time based on the SO item configuration.

It would by basically required for a given individual customer segment to create multiple production order having their own configuration instance which would potentially differ from the configuration of the SO (i.e. PROD 1 using PDS A and PROD 2 using PDS B, where A & B are refering to different input component)

Question:

Is such a requirement applicable? What would be the effective impacts (pegging, CDP planning, CIF, other? ...) Does have any other SAP customer a similar requirement?

Thanks for your valuable inputs.

BR,

Pascal.

[frank_horlacher]

Have a look at note 1364697. It shows a way to have multiple values at characteristic requirements for dependent demands in characteristic propagation.

[former_member585690]

I may put it like this:

In our model, characteristic value assignments for SalesOrder configuration on ECC side are using multiple values, does APO get it in standard? If not (referring i.e. to snote 792893), is there any workaround?

Concerning the resulting impacts to have differing configuration instance between Sales requirement and PROD receipts, I have a little idea especially reviewing snote 526883 (CDP: Unspecified characteristics in planning and pegging), additional inputs would be anyway welcomed.

BR,

Pascal.