Mismatch between actual cost on Cost Plan Breakdown and Expense Line

[lasse3]

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.

[vishal_8_shah]

Hi Lasse,

Did you receive anything back from the HI problem record? We experience the exact same issue with the "expense lines" data load.

The expense lines for the last day of month gets double counted for the original month and the next month.

It would good to know if support has resolved by any chance.

Thank you for posting work-around.

Regards,

Vishal Shah

[ITSMgal]

Hi Vishal -

Have you logged an incident? I have found that the more people who report the same issue, the higher the priority it gets.

[vishal_8_shah]

Hi Emily,

Yes, I have.

Ref # INT3228190

Thank you.

Regards,

Vishal Shah

[akankshaaggarwa]

Hi Vishal

This problem 'PRB720499' has already been fixed in Jakarta. This will also be added to Istanbul Patch 6 and Helsinki Patch 10.

Workaround mentioned in initial post is not the right solution.

Thanks

Akanksha

[lasse3]

Hi Akanksha,

Thanks for the update. I am looking forward to see what the proper solution to this issue is 🙂

Kind regards

Lasse