Pharma: shelf life with remaining 4 months should not be considered for planning

[subramanian_subramanian]

Hi,

Implementation in Pharma : FG Shelf life with remaining 4 months should not be considered for FG planning.

How to exclude this stock while planning for FG. FG planning is Make to stock.

BR

Subbu.

[former_member184574 · Accepted solution]

Hi Subbu,

Requirement is not clear..For FG normally we enter forecast i.e. PIR's in Make to stock..

I am not sure what do you mean by exclude stock while planning FG..means already existing stock with expiry of 4 months is not to be considered during MRP run ? or during delivery against the sales order it should not consider the stock of expiry of less than four months.?.

can you please elaborate the requirement in detail..

Thanks

Kumar

[subramanian_subramanian · Accepted solution]

Hi Kumar,

Thanks for your reply.

Yes you are right, stock with expiry of less than or equal to 4 months should not be considered during MRP run.

It is a Make to stock planning.

We have planned to use 40 strategy.

Assume total FG stock available is 1000. where 400 is with less than or equal to 4 months shelf life.

Assume PIR for FG, we would be giving is 10000, it should not generate the requirements for 9000. it should generate for 9600, since the 400 is less than 4 month shelf life, remaining 600 will have greater than 4 months shelf life.

Do we have any thing on standard. Do we need to move the stock with 4 month expiry to a different storage location, where we can exclude MRP. any other options.....

BR

Subbu.

[Caetano · Accepted solution]

Hi Subbu

Did you check already the document from my previous reply? It describes exactly how to exclude the expired batches using batch determination.

Also, MRP does not consider any batch characteristics, including the expiration date. If you want to make those batches not relevant to MRP, you must manually move them to a storage location not relevant to MRP or use BAdI MD_CHANGE_MRP_DATA.

BR

Caetano

[subramanian_subramanian · Accepted solution]

Hi Caetano,

Thanks for the document. I have gone through it and understood the concept of excluding the expired batches.

There would be many FGs with this situation, how can we pull all the FGs that falls under this criteria and move it to MRP excluded storage location automatically.

Pls can you explain us still better.

BR

Subbu.

[Caetano · Accepted solution]

Hi Subbu

You must create a custom program to move the expired batches to another storage location and it must be executed periodically.

Maybe it would be easier to create an implementation of BAdI MD_CHANGE_MRP_DATA, to exclude the expired batches from MRP. Method CHANGE_MDPSX_MARD should be useful.

BR

Caetano

[subramanian_subramanian]

Hi,

Thanks to Caetano, Kumar & Mani..

We have achieved this with below with customized program....

Exclude those batches from MRP run whose difference between the (expiration date &
current date ) is less than or equal to its procurement time mention in MRP-2
view of material master.

Before running MRP, one need to execute the program with following option:

Input data will be plant, material type or list of material:

   System should execute following logic:

1) In a plant list all material with given material type

2) Execute the BAPI for find out the characteristic value of EXB_MRP from class
type 001of material class (BAPI_OBJCL_GETDETAIL_KEY)

3) If EXB_MRP = Y , then list out all such material.

4) For such a material identity those batches which are available in stock other
than ‘9999’

5) All such batches characteristic of shelf life expiry date need to be derived
from BAPI

6) Calculate ( Expiry Date  - Today’s Date)
= Difference

• PLIFZ  ), batch of
  the material will be transferred to the 9999 storage location which will be
  excluded from MRP run.
• PLIFZ  ), batch of the material will be transferred
  to the 9999 storage location which will be excluded from MRP run.

   7) Run the MRP on materials

   😎 Transfer posting from 9999 storage location to original storage location :
Selection criteria

   On execution transfer the material back to required storage location.

BR

Subbu.

[former_member184655]

Dear Subbu,

Thanks for sharing this work around solution which will be very helpful to others.

I salute you for sharing this.

Regards

Mangalraj.S

[former_member184574]

Hi,

Check this link..may help you out..

MRP Shelf Life Planning in ECC - YouTube

Thanks

Kumar

[Mani72]

Hi Kumar

Thanks. Quite effective presentation in 1 min.

Here, in this approach, Planned Orders are directly created, but is another approach.  One need to model what kind of response is required - Ind. Requirement, Planned Order, Dep. Requirement etc. And how do we tag these requirements separately so that the user is aware that these requirements are due to Shelf Life based planning.

Is this application shown in the video custom developed or is it something available for everyone with some OSS note etc from SAP?

Regards

mani.

[Mani72]

Dear Subbu,

In one of my clients, the idea implemented was to use a 'custom program' that will determine these batches that will need to be excluded from the Planning run.

This custom program will then create additional 'independent requirements' with a separate requirements type equal to the quantity of the batch.  This Program is executed before the Planning run to create this additional requirements so that the batch quantity in the stock is nullified.

Hope this helps.

mani.

[kiran_kumar179]

Subbu,

As far I know restricting the stock based on Shelf life from MRP is not possible.

Either you need to Keep this stock in Blocked or Separate storage location to do so.

Br

KK

[Caetano]

Hello

This selection is made during the batch determination. The following document explains in detail the setup of a batch determination based on the shelf life:

BR

Caetano