Skip to main content

We are experiencing an odd behavior related to the cost projections module, Projected Completed (%), and importing previous revisions. I’ll try my best to explain this one…

When I import an Excel file that has Projected Completed (%) already populated from a previous revision… certain rows (screenshot below) aren’t adding up properly. It shows 100% complete, but why is there still values in the Projected Quantity to Complete (11.22)

 

 

If I manually override that 0 and enter ‘1’  in the Projected Cost to Complete, this happens. Gets closer to the real number. 

 

Then if I switch it BACK to 0… it’s correct.

 

I have seen other odd behaviors where it’ll be marked as 100% completed but there is still a Projected Cost to Complete therefore it throws off quantities remaining…

Like this one - because it’s 100% there shouldn’t be anything in the Projected Cost to Complete column?

 

The reason we’re exporting / importing right now is so that project managers can create a revision each week and not have to re-establish Projected Completed (%) each time but update actual costs. I know this is slated to address in 2023 R1 but figured I’d bring light to this issue as well.

@brandontfrank  Thanks for bringing this up. It is much better to make a case for issues like this so we get visibility and can escalate to development to find a root cause and fix.  Would you mind entering a case please.  Thank you.

I have a client too where for some lines in their cost projection the Cost to Complete is not correct.

The Cost at Completion should match the Actual + Committed, but instead it has the Budgeted Cost loaded. 

Help says 

Projected Cost at Completion = Projected Cost to Complete + Actual Cost + Revised Committed Cost – Invoiced Committed Cost

When you update the cost to complete to 1, and then back to 0, it sets the Cost At Completion correctly, so something is wrong in when the calculation is fired on creating the cost projection. It appears to be labour line costs, so suspect its due to commitments maybe?

If I also choose the Recalculate button, same incorrect result, so only workaround is to change the cost to complete value, and then back to 0 at this point to get the right result.

I have a client too where for some lines in their cost projection the Cost to Complete is not correct.

The Cost at Completion should match the Actual + Committed, but instead it has the Budgeted Cost loaded. 

Help says 

Projected Cost at Completion = Projected Cost to Complete + Actual Cost + Revised Committed Cost – Invoiced Committed Cost

When you update the cost to complete to 1, and then back to 0, it sets the Cost At Completion correctly, so something is wrong in when the calculation is fired on creating the cost projection. It appears to be labour line costs, so suspect its due to commitments maybe?

If I also choose the Recalculate button, same incorrect result, so only workaround is to change the cost to complete value, and then back to 0 at this point to get the right result.

 

@lbarker we ended up working with @aaghaei to completely revamp the code, interface, and calculations for the cost projections module. The out of box experience had calculations that weren’t making sense and not sufficient especially for general contractors who self perform work. Wish Acumatica would look into some of the customization work he’s created on the cost projections and incorporate that for all customers.

Reply


Terms & ConditionsCookie settings