Show TOC Entering content frame

Process documentation Consumption in SAP APO Locate the document in its SAP Library structure

Purpose

This topic provides information about how consumption works in the SAP APO system.

 

Process Flow

This graphic is explained in the accompanying text

...

       1.      The customer requirement consumes the planned independent requirement quantity that lies either directly before it or directly after it. You specify whether the system checks against planned independent requirements in the future or in the past by setting the Consumption Mode field on the Demand tab page of the location-specific product master.

       2.      If the planned independent requirement quantity that lies directly before the customer requirements does not cover the customer’s requirement, then the system looks for the next closest planned independent requirements either in the future or the past.

       3.      During this process, the system refers to the consumption periods maintained in the product master (see above). The consumption periods determine the intervals (for backward or forward consumption) within which customer requirements consume planned independent requirements. Customer requirements which lie outside the consumption period are not consumed.

Note

If no consumption periods have been maintained, only those requirements are consumed that lie in the same planning period as the availability date of the customer requirements.

The assignment of customer requirements to planned independent requirements is carried out dynamically. This means that if requirements are rescheduled, the assignment is deleted and redefined.

Note

There are several different types of quantities in sales orders and similar documents. In general the SAP APO system uses the required quantity.

 

There are four quantities that are important in connection with planned independent requirements in SAP APO and that enable the system to administer consumption dynamically:

·        Planned quantity

This is the original forecast amount for which the forecast was created.

·        Assigned quantity

This is the quantity in the forecast that has been consumed by other order categories, for instance sales orders. Note that this quantity is not stored, it is calculated at runtime. 

·        Open planned quantity

This is the planned quantity that has not been assigned or withdrawn from stock.

·        Withdrawal quantity

This is the quantity that has produced/procured and for which a goods issue has been posted in SAP R/3.

Leaving content frame