Mismatch between actual cost on Cost Plan Breakdown and Expense Line

lasse3
Mega Guru

I noticed that in Helsinki (Patch 5) the total actual cost for a given project on the Cost Plan Breakdown (cost_plan_breakdown) and the Expense Lines (fm_expense_line) did not add up. For some reason the Expense Lines gave a much lower number than the Cost Plan Breakdown. I double checked all the numbers and found that the Expense Lines were the correct numbers. I then looked into the PPMFundManager script include that converts the Expense Lines into the Cost Plan Breakdown and found that some postings where counted double. Due to the way that the query is constructed it appears that if you add an expense line on March 31st it will count in both March and in April, meaning the the cost will be allocated twice on the Cost Plan Breakdown.

Here is an encoded example of the query generated on line 70 to 76 in the PPMFundManager script included:

task=53e09cd00f7da2403915fe5ce1050e9b^date<=2016-04-30^date>=2016-03-31^expense_type=capex^state=processed

The correct query should be:

task=53e09cd00f7da2403915fe5ce1050e9b^date<=2016-04-30^date>2016-03-31^expense_type=capex^state=processed

So line 73 needs to be corrected from:

expenseLines.addQuery('date', '>=', startDate);

To:

expenseLines.addQuery('date', '>', startDate);

I have reported this on HI, but wanted to share it on the community in case somebody else is also struggling with this exact issue.

9 REPLIES 9

ITSMgal
ServiceNow Employee
ServiceNow Employee

Just a reminder on the cost plan breakdown - this table stores record level data, project level rollups, and portfolio level rollup. Make sure to pay attention to the type field in the breakdown when doing any reporting,



cost rollup.png


Thanks for the feedback Emily. I am aware of the above. The issue is however not a matter of distinguishing between Breakdown types, more precisely the issue is that an expense line is included in two financial periods if posted on month end, eg. March 31st it is included in M03 and M04.


ITSMgal
ServiceNow Employee
ServiceNow Employee

Please let us know if / when you get technical support resolution to this issue!


I have confirmation from ServiceNow support that they have been able to reproduce the issue in an out of box instance and that they have raised a problem record 'PRB720499' for this issue. Hopefully development will look into this shortly. Until then I gues the workaround is to modify line 73 as described in my initial post.