Enterprise Resource Planning Blogs by Members
Gain new perspectives and knowledge about enterprise resource planning in blog posts from community members. Share your own comments and ERP insights today!
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Planning based on batch expiry date - Shelf life planning in SAP S4 HANA PPDS

RaghavanKathamuthu
Active Contributor
a month ago
628

Intro:

This blog can show how the SLED in batch can be considered while running the planning in SAP. Have a look

Main part

Configuration Prerequisites:

  1. Material-level batch management to be active

RaghavanKathamuthu_10-1730745267095.png

RaghavanKathamuthu_11-1730745267096.png

RaghavanKathamuthu_25-1730745803013.png

If conversion is graded out then leave it. This will activate the batch status in batches

  1. Activation of Advanced planning

SIMG - Advanced Planning - Basic Settings - Activate Advanced Planning and Scheduling  - Activate Advanced Planning and Scheduling

RaghavanKathamuthu_13-1730745267098.png

  1. Characteristic dependent planning.

SIMG - Advanced Planning - Basic Settings - Define Configuration Schema (CDP or Variant Configuration)

RaghavanKathamuthu_14-1730745267099.png

  1. Organization Area. (O1CL)

SIMG - Cross-Application Components - Classification System  - Classes  - Maintain Object Types and Class Types

RaghavanKathamuthu_15-1730745267101.png

RaghavanKathamuthu_16-1730745267103.png

  1. The report RVBCOR08 is to be run to create the APO characters and class types.

RaghavanKathamuthu_17-1730745267104.png

RaghavanKathamuthu_18-1730745267105.png

This report will create the SLED-related characters, Object dependencies, and Functions in the background. Have a look SAP Help . You can do it via config SIMG - Logistic general - Batch management - Batch Valuation - Update Standard Characteristics

  1. Integration model to be created in CFM1 to transfer the characters. Here the Model Name and APO application are just like the character field. You can give whatever you want. Logical system you can get it from SCC4. Have a look

RaghavanKathamuthu_19-1730745267107.png

In the Next screen click Generate Integration Model

RaghavanKathamuthu_27-1730746272200.png

  1. Integration model to be activated in CFM2

RaghavanKathamuthu_20-1730745267109.png

In the Next screen click Activate Integration Model and start.

RaghavanKathamuthu_28-1730746320735.png

  1. Business sets to be activated in SCPR20.

/SAPAPO/APO_ON_ERP, /SAPAPO/APO_ON_ERP_CDP and /SAPAPO/APO_ON_ERP_SWITCHED

RaghavanKathamuthu_21-1730745267110.png

This will add to the /SAPAPO/MATKEY table in O1CL

RaghavanKathamuthu_22-1730745267112.png

In APO PPDS class type 023 is converted to 230 and 300 to 400 when moving class from ECC to APO. But in Hana, PPDS 023 is not converted to 230. Have a look 2927766 

Master data:

Class characters are to be created with the organization area.

RaghavanKathamuthu_23-1730745386272.png

RaghavanKathamuthu_0-1730745267030.png

  • LOBM_VFDAT against this a OD will be assigned - SL_MAX_COMPUTE
  • LOBM_VERAB - SL_MIN_COMPUTE
  • LOBM_HSDAT  -SL_UTC_COMPUTE
  • LOBM_APO_SL_MIN
  • LOBM_APO_SL_MIN
  • LOBM_APO_SL_UTC

RaghavanKathamuthu_29-1730747301647.png

You can check object dependencies in CU01. Cross-check that all are in the released state.

The APO reference characters are to be created with the organization area. These characters are used to transfer the SLED from ECC to PPDS and this will not be displayed in the ECC batch.

Material master to be created with the self-life planning heuristic and advanced planning checkbox

RaghavanKathamuthu_1-1730745267037.png

Assign the class to the material master and batch management in the work scheduling view.

Self-life to be maintained in Plant storage location data.

RaghavanKathamuthu_2-1730745267041.png

Now the master data will be moved to PPDS. (/N/SAPAPO/MAT1)

RaghavanKathamuthu_24-1730745522050.png

Work center to be created with the advanced planning check box. Once created in ECC it Will be moved in the background (/N/SAPAPO/RES01)

RaghavanKathamuthu_3-1730745267045.png

The routing and the production version are the same. Meanwhile, the Product data structure is to be created in PPDS via CURTOADV_CREATE with the check box absolute transfer

RaghavanKathamuthu_4-1730745267052.png

GR for the product ‘PPDS’ in MIGO is to be done with the class characters and Date of Manufacture.

RaghavanKathamuthu_5-1730745267063.png

The self-life will be added to the batch master with the help of reference characters (LOBM*).

RaghavanKathamuthu_6-1730745267068.png

This in turn moved to PPDS via APO characters, CIF, and will be shown in Product view /N/SAPAPO/RRP3

RaghavanKathamuthu_7-1730745267076.png

Now the requirements need to be created. You can just click the edit button on top of the product view screen and give the requirements in negative value with date. Click enter. On creating the requirements, the required self-life date will be calculated for the new requirement based on the requirement date and SLED in the material master.

RaghavanKathamuthu_8-1730745267085.png

Now the requirement SLED will be compared with the Batch SLED to create the new receipts.

After running the Heuristic, below are the requirements and receipts.

RaghavanKathamuthu_9-1730745267094.png

Here one new planned order has been created, as the required SLED (31.01.26) does not come under the stock SLED (04.11.25).

Troubleshooting - If the SLED is not shown in PPDS check the organization area assigned in class. Check the O1CL for the organization area.

Check whether CIF is not maintained in CFM1 for class characters and activated in CFM2 or not.

Check general PPDS implementation 3369134 . Check Configurations

Conclusion:

I hope this may help you get an idea of self-life planning in PPDS. Please comment if there are changes to be done

 

Labels in this area
Popular Blog Posts