Hello everyone,
I’m facing an issue and would appreciate your support.
The scenario occurs in the following sequence:
-
Oct 5: Received 100 qty, unit cost 100.
-
Oct 10: Issued 10 qty.
-
Oct 1 (backdated): Received 50 qty, unit cost 120.
Expected Result:
After running Adjust Cost – Item Entries, the system should automatically adjust the issue transaction on October 10 to reflect the backdated receipt on October 1, resulting in an updated issue cost of 120.
Actual Result:
After running Adjust Cost – Item Entries, the issue transaction on October 10 remains at a unit cost of 100, and no adjustment entries are created until the issue is manually re-applied to the October 1 receipt.
I tested this scenario and observed the following behavior:
After running Adjust Cost – Item Entries, the issue transaction on October 10 still remains valued at 100, and no adjustment entries are generated.
I tried to unapply the issue transaction on October 10 from the receipt on October 5 (which was automatically applied by the system when the issue was posted). However, after unapplying, the system automatically re-applied the issue on October 10 to the receipt on October 5 again.
Only when I manually unapplied the issue on October 10 from the receipt on October 5 and re-applied it to the receipt on October 1 did the system recalculate the issue cost on October 10 as 120 after running the cost adjustment.
This indicates that the system does not automatically reapply FIFO layers when a new backdated receipt is posted. The original application between issue and receipt remains fixed unless it is manually unapplied and reassigned. Therefore, the Adjust Cost process alone does not re-evaluate the costing layer linkage once the issue has been applied.
Could there be any setup or parameter affecting this costing behavior?
Thank you in advance for your help.
Best regards,
Thanh Nguyen.
