Академический Документы
Профессиональный Документы
Культура Документы
Purpose
This page will provide an example on how to integrate shelf life dates for back stocks in PP/DS, when the Date of Manufacture of batch
is not informed
Overview
The relevant characteristics and dependencies are shown, in APO and in ECC. Batches are created and integrated into APO, and the shelf
life dates are shown. The example follows the steps described in note 810694.
Table of Contents
Purpose
Overview
Example Creation
Background Information
Batch Level Customizing
Organizational Areas in APO and ECC
Create The Shelf Life Class with the Relevant Characteristics
Generate and Check the Class Dependency
Assign the Dependency to the Batch Class
Assign the Batch Class to the Material and Make Batch Management Required
Integrate the Master and Transactional Data to APO
Master Data
Transactional Data
Create and Classify a Batch, then Add Stock Quantity to It
Verify the Availability Date and the Shelf Life Dates for the Batch Stocks at the Product View
Related Content
Related Documents
Related SAP Notes/KBAs
Recent Correction Notes
Example Creation
Background Information
The example assumes the involved materials, BOMs, work centers, routings/recipes, and production versions are already maintained - no
details will be provided on this
If you are extending an existing Batch Class instead of creating a new one and there are already some batches in the system, it is required
to reclassify the batches
If the batches are sent to APO without correct classification, they will have no Shelf Life dates in APO and suffix 01.01.1970 or 31.12.1969
will be added to the stock number. Furthermore, this batch stock will not be used to cover any demands in the system, be it via pegging or
during heuristic planning - this can lead to unwanted exceess planned production, unexpected under coverage or product/receipt too late
alerts, as well as unclear Days' Supply calculations
The Batch level on ECC side should be set to Unique at Material Level, such that Batch Class Type 023 is used, given Class Type 022 is
not supported in APO
To make sure the setting is correct, execute transaction OCHA, then execute action "Specify Batch Level and Activate Status
Management"
In the new screen, click Batch Level button. Then, select option Unique at Material Level if it is not already selected, and save
Press Back button to return to the previous screen. If you had to change the setting in the previous step, button Batch level -> conversion
is now enabled and you need to run it to update the related database tables
Please, notice as soon as you execute the conversion, it is not possible to change the Batch Level back to "Unique at Plant
Level" anymore
The shelf life dates are integrated to APO as characteristics, therefore Organizational Areas must be defined in both environments for the
class types to be integrated.
Firstly, on ECC side, execute transaction O1CL, select table MARA in the list and double click folder Organizational Areas. Then, create a
new entry for Class Type 023
In APO side, also in transaction O1CL, select /SAPAPO/MATKEY entry in the list and double click Organizational Areas folder. Here, an
entry should be created for Class Type 230 (or 232)
Go to Characteristics tab and add the shelf life characteristics. Notice that only for the LOBM_APO* characteristics the Organizational Area
must be specified, such that only them are integrated to APO - integration of the other LOBM* characteristics is not recommended in this
scenario. Save!
Notice that, while LOBM_APO_SL_MAX and LOBM_APO_SL_UTC must be added to the class, LOBM_APO_SL_MIN is optional.
The shelf life dates to be sent to APO and assigned to the LOBM_APO* characteristics are calculated with
dependency SL_UTCMINMAX_COMPUTE
Notice that this step does not have to be executed everytime you create a new shelf life class. Rather, it's usually not necessary
to run it more than once.
The dependency can be generated by running program RSL_UTCMINMAX_MAINTAIN in transaction SE38
In transaction CU02, make sure that Dependency SL_UTCMINMAX_COMPUTE has status Released
In transaction CU66, make sure that Function SL_UTCMINMAX_COMPUTE has status Released
In transaction CU02, make sure that dependencies SL_UTC_COMPUTE, SL_MIN_COMPUTE and SL_MAX_COMPUTE have
status Locked
This is done because in this scenario the shelf life dates will be calculated with the Class dependency SL_UTCMINMAX_COMPUTE, not
with the characteristic dependencies. Example:
Assign the Dependency to the Batch Class
In transaction CL02 when changing the class in Basic data tab, go to menu Extras → Object Dependencies → Assignments
Assign the Batch Class to the Material and Make Batch Management Required
In transaction MM02, maintain the Batch Class in Classification View
For the purpose of this example, the batch and stock quantity will be created and posted manually
In transaction MSC1N, create a batch in the desired Plant and Storage Location (0001 and 0001, in this case)
Specify the expiry date (SLED) and Available From and press enter
Set flag Item Ok, then click Check button to verify whether there are any errors
If there are no errors, click Post button, and check that it was posted successfully
Execute transaction MMBE for the batch and check that it does contain the quantity
Verify the Availability Date and the Shelf Life Dates for the Batch Stocks at the Product
View
Notice that Versions tab appeared - this tab will be shown when there are classified batches in the system
Check that the Maximum Shelf Life Date/Time was successfully integrated to APO for batch YOG1
Go to tab Versions. Specify Created From date earlier than the date the batches were created on and press Enter
Check that for YOG1 the Shelf Life dates (Reference Timestamp of Batch, Maximum Shelf Life in Seconds) are shown, and that the
Classification Status is green
Related Documents
SAP Help Planning with Shelf Life Data in PP/DS
SAP Help Shelf Life Data
SAP Help Dynamic Pegging Considering Shelf Life Data
SAP Help Planning with Shelf Life Data in SNP