IBP for demand

[carlos_perez8]

Hi all

For customers moving for APO to IBP using sales org, or distribution channel as a characteristic what should be the best practice?

Where to maintain these levels?As a customer attribute?specific MD?

Thanks in advance

[Irmi_Kuntze · Accepted solution]

two possibilities are usually chosen:

1) use CUSTID and load it with a concatenation of Customergroup@SalesOrg@DistrChannel.

Plus have sales org and distr channel and customer group (if relevant) as single master data types, plus as attribute to CUSTID so you can select by them and cannot make wrong entries due to the check to the MD type

Advantage: Same information for supply side of S&OP

Disadvantage: CUSTID itself becomes not so nice to read / usability - which is why I usually have the additional attributes and not use CUSTID for display to the end user.

2) create new MD types for sales org and distr. channel, and a new planning level that has them as root in addition to CUSTID. There might be some documentation on the how-to in the best practice content, not 100% sure
advantage: better visibility

disadvantage: On S&OP supply side only the aggregated value for the CUSTID, whatever is in there, not the sales org and distr channel any more

____________

Concept differs a bit depending when you need any other non-standard roots, and whether you need attributes from MVKE (salesorg specific master data) such as salesorg-specific material status. In that case, having sales org as root in the planning level, and Sales-Product as additional compound MD type might be helpful