Restrict Batch Entry in Subcontracting GR (543) and Return (542) to Match Exact 541 Batch

[alateomkar]

Hi Experts,

In our subcontracting process, we often send the same material under multiple batches (e.g., Batch A and Batch B) using multiple 541 movements for the same PO and same material.

However, during goods receipt (543) or component return (542), the system currently allows users to enter any of those batches, even if it doesn’t match the batch that was actually sent in the corresponding 541 document for that quantity.

This leads to issues like:

• Incorrect batch reconciliation

• Vendor stock mismatch

• Incorrect consumption reporting

💡 Requirement:

We want the system to:

• Allow only the exact batch (from 541 movement) for which the quantity is being received or returned.

• If a user tries to post a GR or return using a different batch, even from the same PO and material, the system should throw an error and block the posting.

• This should apply for MIGO and MB1B, for 543 and 542 movement types respectively.

Has anyone implemented such a batch-level validation in subcontracting scenarios?
Are there any standard options, BAdIs, or enhancement points you would recommend to achieve this?

Appreciate your guidance!

[Lakshmipathi]

Try the solution given here  for the same requirement.