That's the standard behavior of the standard system to check at the lowest level if mentioned in sales order. Example if your SO is at plant level only then it would check at this level, If it's with plant and storage location then check would be at storage location instead of plant level and results could be different as plant might have three Sloc with more quantity. Same applies for batch which again is further lowest level as it is checking for specific batch in that storage location.
If you want this check to be at plant level then keep your sales order at this level itself else you will have to check for exit/badi to do this. Using exit/badi then needs good amount of testing as results might be over-confirmation etc. coz batch might have less quantity but plant stock would be more.
Manipulate Batch number for 1 product it is OK. We can consider particular batch number. When all the materials are considered how can manipulate with respect to each sales order..
In APO business wants batch details.
Now business stopped this requirement of not considering Batches in sales orders.
While doing unconfirmation with BOP orders were getting unconfirmed but batch details were not removed. So, they wanted to remove batch details also from sales orders. It was achieved with ECC customizing.
And they want batch determination should happen based on available stocks and batches. But it is not happening.
Any idea what should be considered in re ATP or batch BOP to consider new batches.
We have achieved this scenario by doing customization in ECC.Batch determination is done in ECC itself. So, we have applied the logic at the time of batch determination in ECC for a sales order.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.