Net Requirements Calculation If you have set a requirement-oriented planning basis for a particular horizon, the system executes a net requirements calculation in the planning run. Here, the system calculates the quantity of product to be planned to be transferred to the selected procedure.
Using the BAdI /SAPAPO/SEQ_MULTI_02, you can implement an alternative method to the net requirements calculation described here.
You have specified a
requirement-oriented planning basis
for a horizon in the procedure package. See also:
Defining the Planning Basis
In the
Demand
tab page in the
Pegging
section, you have entered the value
100.000:00
in the field
Maximum Lateness of a Receipt
.
The net requirements calculated by the system for a horizon includes the receipts and requirements that lie in the horizon, before the horizon and in the period of adjustment.
For the receipts, the system differentiates between the following orders:
Non-firmed orders
Output-firmed orders
These are orders which you have created manually or for which you have set the
Output firmed
indicator in the order processing function.
Activity-firmed orders
These are orders for which you have firmed the order activity of the planning segment. You can execute this type of firming in the sequence schedule using an expert function.
Note
In planning, orders which are output and activity-firmed are treated in the same way as orders which are only activity-firmed.
The assignment of an order to a horizon depends on the start date of the order activity which is executed in the planning segment. This start date must lie in the horizon and the availability date of the order must also lie in the same horizon.
In APO, the net requirements are calculated as follows:
The calculation of the net requirements for a product is executed in a first step using the following formula:
All requirements (requirements that lie before the horizon, in the horizon and in the period of adjustment)
- Orders that lie before the horizon
(pegging strategy –
Use Earliest Receipts
)
- Orders for which the order activity in the planning segment in the horizon or in the period of adjustment is firmed (use pegging strategy according to the setting in the product master)
- Firmed orders which lie in the period of adjustment (use pegging strategy according to setting in the product master)
----------------------------------------------------------------------------
= Net requirements
If you have not specified a pegging strategy in the product master in the
Reqmts
tab page the system uses the strategy
Use Earliest Receipts (First in First out)
for the orders that lie before the horizon. Here, to cover a requirement, the system uses the earliest receipt in the pegging interval. That is, first the first receipt in the pegging interval, then the second, and so on.
You can define the strategy “
Use On-time Receipts
” or “
Use Earliest Receipts (first-in-first-out)”
in the product master for the purchase requisitions and firmed orders.If you have set the pegging strategy “
Use on-time receipts
”, the system uses the receipts closest to the required time in the pegging interval to cover a requirement. Starting from the requirements date, the system therefore first searches up to the start of the pegging interval.If the system does not find any receipts going in this direction, it then starts from the requirements date and searches to the end of the pegging interval.
Then the system uses the following formula to calculate the excess of output-firmed orders :
Product net requirements
- Firmed orders in the horizon
----------------------------------------
= Excess firmed orders
In a last step, the system calculates the quantity of product to be transferred to the procedure you have set for the horizon.
Product net requirements
+ Orders with a firmed activity in the horizon
+ Excess of firmed orders
---------------------------------------------------------------------
= Quantity to be transferred to the procedure