Additional Blogs by Members
cancel
Showing results for 
Search instead for 
Did you mean: 
Former Member
0 Kudos

SHELF LIFE MAINTENANCE AT PLANT LEVEL 

Business Situation : Out of 10 plant locations producing a material only 1 plant location has bad Manufacturing conditions / storage conditions / sterility conditions as compared to the others. As a result the batches of material produced at this plant have a shorter shelf life than the batches produced at other locations. The Total Shelf Life field has been maintained in the material master keeping in mind the manufacturing conditions of the majority of the plants. As a result, the users at this particular plant have to manually keep changing the Batch Shelf Life Expiration Dates on every single batch produced.        

Shelf Life required on Material / Batches at specific plant       

!---------------------------------------------------------!    

Shelf life Maintained in Material Master        

!---------------------------------------------------------------------! 

Business Requirement : The business needs an automated way to maintain the shelf life expiration dates on batches produced at this one plant in such a way that it takes into account the shorter shelf lives for the materials produced at this plant. 

Proposed Solution : 

Option 1 :  Remove entry from the Total Shelf Life field in Material Master.  

Advantage – This will prevent Shelf Life Expiration Dates from being calculated automatically at Goods Receipt from production. Users can then maintain whatever shelf life expiration date they want.  

Disadvantage – This will create a lot more work for users at all 10 plant locations because they will have to add up the shelf life to the production date at every Goods Receipt. 

User Acceptance – Not acceptable.  

Option 2 : Create a Control Table with Material #, Plant, Local Shelf life & Y/N fields. Users / Central Data Team will maintain the table with relevant information provided by the Plant users. The plant users will be submit the request to maintain the table to central data team. The proposed solution is to create a batch job (a custom / enhanced program) which will run everyday at 00.00 Hours & check for the confirmed process orders (101 Material movement). The batch job will check all goods Movement (101) made against a process orders and check the process order confirmation status, system will check the control table and if the material is maintained in the control table system will replace the shelf life date value for that batch with the value maintained in the control table.

Material Master Shelf Life – MARA Table Entries

123456 : 30 Days

145698 : 40 Days

MaterialPlantLocal Shelf LifeD/W/YY/N
123456010123DY
145698010128DN

 D/W/Y – Days / Week / Year If this is seasonal change, then users can select the option Y/N, “Y” means need to change the shelf life for the batches & “N” means don’t need make any changes with the batch shelf life value. This will save the users time of submitting the request every time for changes to Central Data maintenance team with all the information all over again. 

Before Batch Job Run : 

MaterialPlantBatch #Mfr DateSLED
1234560101000002587906/01/201007/01/2010
1234560101000002588006/02/201007/02/2010
1456980101000003133306/02/201007/12/2010
1456980101000003133406/03/201007/13/2010

 

  After Batch Job Run : 

MaterialPlantBatch #Mfr DateSLED
1234560101000002587906/01/201006/24/2010
1234560101000002588006/02/201006/25/2010
1456980101000003133306/02/201007/12/2010
1456980101000003133406/03/201007/13/2010

Advantage – System will do the Shelf Life Expiration of the batches automatically in background, eliminate the chances of errors / mistake. Eliminates manual calculation work, 

Disadvantage – Control Table need to be maintained. 

User Acceptance – Accepted.