In AFS, if you run allocation on Preview mode on transactions J3AT or J4AE, no data is changed in tables J_3ABDSI or J_3ABDBS. In other words, no requirement documents and stock are changed in the database.
If you want to maintain allocation proposals for a better business analysis before allocating your stock on normal allocation mode, you can use modes 2 and 4 for Preview Allocation. On this case, table J_3ARESH will be updated, but your requirements and stock will NOT be changed. Table J_3ARESH is only filled and manipulated by allocation on preview mode. No other standard transactions or reports change this table.
Therefore, you can analyze the preview allocation results in J_3ARESH as your business needs by creating your own reports. SAP does not deliver any report regarding this analysis as each company has different business cases.
AFS customers usually perform ARun on Preview mode to check if it will reflect what the business was expecting. They often clear J_3ARESH before running Preview mode. After analyzing the outcome on J_3ARESH, they run Allocation on Normal mode and may use the Optimizer (J4AB) to change a few requirements for better tuning.
To refresh table J_3ARESH you should also create a custom report.
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
J3AT , SE16N , batch stock , batch number , J_3ARESH , MRP status , Preview Allocation , J_3ABDSI , J_3ABDBS , ARUN , preview mode , KBA , IS-AFS-ARUN , Allocation Run , IS-AFS , Apparel and Footwear , How To
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.