Ansicht
Dokumentation

APO-PPS-BF: Planning with Shelf Life Data ( RELNAPO_30A_SP1_PPS-BF_S )

Fill RESBD Structure from EBP Component Structure   Vendor Master (General Section)  
This documentation is copyright by SAP AG.

Short text

APO-PPS-BF: Planning with Shelf Life Data

Use

As of Release 3.0A (First Customer Shipment and Support Package 1) shelf life data can be transferred from an OLTP System (for example, an R/3 System) to APO, where it can be processed and taken into account in PP/DS scheduling.

The goals of planning with shelf life data are:

• To recognize that stock is about to expire

• To only deliver/commit products to customers if the required shelf life criteria has been met

• To only assign stock or a manufacturing order to a consumer if the consumption takes place within the usability period

The shelf life is visualized in the product view and in push production.

Shelf Life Information in R/3

The following objects carry shelf life information in R/3:

• Material master
  If a value is entered in the "Total shelf life" field in the R/3 material master (General plant data/Storage 1 view), the "Planning with shelf life" indicator is set in the APO product master and the total shelf life is transferred to the "Shelf life" field.

• Batch
  If the material to be produced is to be handled in batches in R/3 and the availability and expiration date characteristics are defined for the creation time, this data is transferred to APO.

• (Configured) Sales order
  If the required minimum and maximum shelf life is defined as characteristics with values in the sales order, this data is also transferred to APO.

Shelf Life Information in APO

Along with the information about total shelf life transferred from R/3, the following information in the product master can be created or adjusted in APO:

• Maturity time, that is, the time required by the product after the good receipt until it can be used (availability time); the maturity time and the usability time together make up the shelf life period (ending with the expiration date)

• The required minimum shelf life, possibly already taken from R/3

• The required maximum shelf life, possibly already taken from R/3

This data serves as default values for receipts (for example, a manufacturing order generated in APO) and requirements (for example, a planned independent requirement), for which no values have been transferred from R/3 or the OLTP System.

In PP/DS planning, a comparison is made between product receipts and product requirements taking the shelf life data or requirements into account. If there is a valid intersection, the receipts are linked to the corresponding requirements.

Example

A product receipt requires 5 days of maturity time starting from today. It can then be used for 20 days. The expiration time is in 25 days. The requirements are as follows:

Requirement A: required in 15 days, required minimum shelf life of 6 days, required maximum shelf life of 12 days

Requirement B: required in 20 days, required minimum shelf life of 6 days, required maximum shelf life of 12 days

Requirement C: required in 10 days, required minimum shelf life of 6 days, required maximum shelf life of 12 days

The product receipt which reaches its expiration date in 25 days is only linked with requirement A since it fulfills both conditions (minimum shelf life date in 21 days, maximum shelf life up to 27 days).

BAL_S_LOG - Application Log: Log header data   General Material Data  
This documentation is copyright by SAP AG.

Length: 3736 Date: 20240426 Time: 124916     sap01-206 ( 66 ms )