
Key Account (DEMFCSTACCOUNT) is used for forecasting and customer-facing teams to collaborate on demand. It is possible that the customer forecast collaboration process is also carried out at this level.
Only the top customer accounts are given detailed attention. The rest can be grouped under a catch-all ID, for example, ALLOTHER.
Note
The attributes, planning levels, and values defined are examples and will require additional modeling from sample planning area SAPIBP1.
Forecast consumption is carried out as a pre-step before supply planning.
The supply customer is aligned with the class of service, that is, customer grouping is done by location, rather than by individual key account:
- Fair-share works better with fewer demands
- Supply planners care more about product mix and positioning inventory than customer fulfillment of individual key accounts within a class of service
- Run-times for optimizer
- Fewer customer-product combinations to manage
- Response - needs more granular customer to represent sales order confirmations; allocations may be performed at the key account
Note
The terms "crossover" and "discount" are neither technical nor SAP terms. They simply convey how protection is provided across time buckets between demand layers.
Demand prioritization is not just for a product, but applies to all products in a network. Penalties and costs drive both:
- Production and distribution decisions
- Better use of common constraints such as capacity and material

Key figures related to demand and fulfillment from the IBP supply perspective are listed here for quick reference - for more information, see the online help.

Like customer demand, independent demand also has its share of key figures.

With modeling, there is a great degree of flexibility - follow the guidelines from the picture to achieve a better cost model and a better-performing solution.













