Production Order transactions must remain a permanent cost in the project

Question

Hi,We have a client using Production Orders who also tracks production costs against Projects.They have a unique accounting requirement where the WIP Account and WIP Production Order Variance Account on the Production Order are configured to use the same GL account.The issue occurs when the Production Order is completed/closed. Acumatica reverses the Production Order costs from the Project and posts the amount to the same COGS account, but the offsetting entry is posted to the Non-Project (X) Project. As a result, the cost is no longer reflected against the original Project as desired.One solution I’m considering is creating a Generic Inquiry, Import Scenario, and Business Event to automatically generate a reclassification that moves the COGS amount back to the appropriate Project once the Production Order is completed.Has anyone encountered a similar requirement or found another way to handle this using standard Acumatica configuration? I’d be interested to hear if there is a cleaner approach before implementing the automated reclassification.Thanks in advance for any suggestions!

ranjithduraisamy72 · Accepted Answer

​@fpantelidakis07I believe this is expected behavior. I encountered a similar scenario, although it was not exactly the same. I created a Business Event and Import Scenario to generate a Project Transaction. In that process, I imported two lines: one line reduced the value of Project X using a negative amount, while the second line increased the value of the appropriate project.I tested this scenario in 24R1, and I don’t believe there have been any significant changes in the product.

dgodsill97 · Answer

Only changes to the WIP account are posted to a project. The WIP account is set to zero when you close a production order with the change to the balance by debiting or crediting the WIP Variance, Since a production order can only be closed once, a business event to create a project only transaction can work - a project only transaction does not update the GL. The BE can be triggered by the closing event (AMProdEvnt) or by the creation of the WIP Adjustment transaction.

Sign up

Social Login

Login to the community

Social Login