Prevent expired batch allocation during operation release in process order

[Former Member]

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.

[Caetano · Accepted solution]

Hello

If you use QA07 without the indicator Block batch, system will not move the batches to restricted stock, it will only show a list of the batches about to expire. You can manually choose what will happen with this batch.

Another alternative is to change your process and post the goods issue to the order earlier, as soon as the batch is determined, using CO27.

If none of these options are suitable for you, you can create a copy of program RQAAAS10 and change it to avoid the consumption of batches allocated to an order.

Regards,

Caetano

[Former Member · Accepted solution]

Hello Caetano,

Thank you for your feedback on my query.To prevent expired batch allocation block batch indicator needs to be checked on QA07 Screen. I will check with business if they are willing to change SOP or not. If they are not willing to change SOP then i will go ahead with implicit enhancement option to meet below requirements :

• 1.If batch is fully allocated to process order and falling under initial run days should not move to block stock

• 2.If batch is partially allocated to process order and falling under initial run days should move reaming stock only from unrestricted to block stock

i have prepared below logic :

Enable Implicit enhancement on QA07 execute using BADI INSPECTIONLOT_UPDATE

Either need to maintain plant specific entry in TVARV or utilize existing ZTECH table

Compare RESB table with MCHB table for reserved batch and put condition if both entries match then exclude batch during QA07 executionà This is applicable for fully reserved batch

Partial allocated batch: Compare RESB table with MCHB table for reserved batch and put condition if both entries match then exclude batch with reserved quantity and move remaining quantity to block stock based on calculations like Available quantity from (MCHB) table – Reserved quantity from (RESB) table.

Could you please check this logic and let me know your thoughts or Shall i prepare new transaction like ZQA07 which will be copy of program RQAAAS10 (as given by you).? Do you have any specific BADI for QA07 ?

Your expert advise will be appreciate here.

Thanks,

Mayur.