Planning Standard Lots with Consideration of Shelf Life Data

Use

To create procurement proposals with consideration of shelf life conditions for uncovered product requirements, you use heuristics based on the /SAPAPO/HEU_PLAN_STANDARDLOTS algorithm for planning standard lots ; for example, the standard heuristics SAP_PP_002 and SAP_PP_SL001.

In a planning process that considers shelf life conditions, you can use the heuristic for planning standard lots as follows:

You can execute the heuristic using an infinite detailed scheduling strategy. To solve planning problems that have resulted from infinite scheduling, you execute a PP/DS optimization after the heuristic.
You can execute the heuristic using a finite detailed scheduling strategy. You then solve planning problems using the detailed scheduling planning board and push production.

Prerequisites

You set the Plng w/ shelf life indicator in the product master
To enable the heuristic to consider the shelf life conditions, you must have set the planning with shelf life indicator in the heuristic settings. SAP provides the standard heuristic SAP_PP_SL001 for planning with standard lots with shelf life with the indicator set.

Features

The planning process is the same as with planning without shelf life. The following table shows the special features during planning with shelf life conditions for each planning step.

Planning step	Features when planning with shelf life conditions
Net requirements calculation	The net requirements calculation only offsets stocks, receipts and requirements with compatible shelf life data. For the net requirements calculation you must have defined the minimize alerts procedure, that is, you should not have set the Consider fixed receipts first indicator in the heuristic settings.
Procurement quantity calculation	You must have adjusted the parameters relevant to the procurement quantity calculation in the location product master to the shelf life conditions. The following parameters must be smaller than the shelf life of a receipt: Parameters that control the grouping of requirements, such as the period in the period lot-sizing procedure, the target days’ supply or the reorder days’ supply The safety days’ supply that prescribes a time buffer between an availability date and a requirements date If these parameters are larger than the shelf life, the heuristic creates a warning in the planning log. Whether the heuristic can actually schedule a planned order in the desired lot size without violating the shelf life conditions depends on the resource availability and the detailed scheduling strategy (see below).
Source of supply determination ( PPM and mode selection )	The heuristic selects the production process model and the modes that lead to an availability date that is as late as possible without violating the shelf life conditions, for a planned order to be recreated.
Detailed Scheduling	So that the heuristic can schedule the newly created procurement proposals, you must have defined the planning direction Backward or Backward with Reverse in the relevant strategy profile . The desired availability date of the procurement proposal is the requirements date minus the maturation time; from this date, the heuristic searches into the past for a scheduling date. Whether the heuristic can actually schedule a planned order so that it covers the uncovered requirements for which it is created without violating the shelf life conditions, depends on the detailed scheduling strategy, the resource availability, the component availability and the procurement quantity of the planned order. For example, with large lot sizes and finite scheduling, the heuristic may not be able to schedule the planned order on time. Consequences: Shelf life conditions can be violated, requirements can remain uncovered or the newly created planned orders create surpluses. The heuristic cannot correct these planning problems.
Reuse	The heuristic always carries out planning again; that is, it always creates new procurement proposals, without reusing existing, unfirmed procurement proposals. Therefore the heuristic uses the reuse mode Delete unfirmed receipts , independent of the reuse mode you have defined.