We would like to implement Quota arrangement. We do have AFS, but we checked that
the issue remains the same for either AFS and non AFS materials leading to believe that it is not AFS related.
Configuration and master data setup was done according to below steps:
Configuration:
1. MRP-> Planning-> LotSize Calculation > Check Lot-Sizing Procedure -> Splitting quota box checked for used Lot size
2. Customize AFS Control Source Allocation : PURCHASING-AFS SOURCE
ALLOCATION-DEFINE SOURCE ALLOCATION CONTROL -> Checked box for ‘source allocation standard’
Master Data setup:
MM02-PURCHASING-SOURCE LIST checked
MM02-PURCHASING-QUOTA ARR USAGE selected ‘Y’ – configured to included PO, PR, MRP. In testing we tried using different usage and the issue still remained in all cases.
MM02-MRP1 - LOT SIZING PROCEDURE (SELECT ONE THAT HAS SPLIT QUOTA IN CUSTOMIZING)
ME01 - MAINTAIN SOURCE LIST
MEQ1 - MAINTAIN QUOTA
Everything is working correctly with exception of Allocated Qty. It is counting both Purchase requisition qty and PO that has been created
with reference to that same Purchase Requisition resulting in double counting. The double counting does not happen at the time of PO creation via conversion from Purchase Requisition, but at the time of PO released via ME28. This is causing incorrect Allocation qty accumulation. We have tried closing Purchase Requisition manually right after it was converted to a PO. However, that did not correct the Allocated Qty. In debugging mode we see that when we are releasing PO(ME28) internally then program is checking schedule line qty and again updating quota arrangement not considering PR qty is used in the PO.
There is SAP program RM06Q003 program to correct incorrect allocation of quota quantity. However, it’s not a good practice to run this program every day. We need to fix the incorrect allocation of quota quantity in our system permanently by preventing the issue from happening. We can't afford to have incorrect allocations at any given time waiting for the correction program to run. It will be misleading for our users and will result in incorrect allocations.
Is there a permanent solution that will prevent this issue from happening and allow us to trust the data at all times without extra correction
steps?
Thank you for your thoughts on this.