cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Prevent expired batch allocation during operation release in process order

Former Member
0 Kudos
2,914

Hello Team

Good day. I am working for pharma client and have came across an issue like Business would like to prevent expired batch allocation to component at the time of operation release. Currently we are using QA07 with background job which is picking batches which will be going to expire or already expired based on initial run days ( our case is 1 day) and moved those batches from unrestricted to blocked stock which is working absolutely fine.

As per their process they are creating Process orders in one month advance and later released. What is happening here is, batch which will be near to expire and allocated to process order getting picked up via QA07 background job if it is falling under initial time frame so, business would like to exclude allocated batch during QA07 execution reason being is that consumption and other activities should be done before batch movement from unrestricted to block stock. I have checked configuration but no luck it will be great if you can advise here how to tackle this requirement via any enhancment, user exist or configuration.

As manual work around i had suggested to use MB1B move stock blocked to unrestricted. Appreciate your response here.

View Entire Topic
Former Member
0 Kudos

Hello All,

Thank you all for your feedback and answers. I decided to proceed with below options

1. Enhancement by copying QA07

2. Increase time frame period max by 90 days

Hence closing this thread.