Negative Actual Revenue Transactions in MUX

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

Negative Actual Revenue Transactions not reflected in MUX when the value becomes 0

STEPS TO REPRODUCE

 

1. Create a Project that spans from January to May 2024 for example

2. Financially enable it

3. Add a team member and financially enable the resource too

4. Create a transaction:

Quantity 20

Cost 0

Rate 100

5. Run the following jobs:

Post transactions to Financials

Post to WIP

6. In Classic UI, go to the project and create a cost plan spanning from January to May

7. On the Amounts by Period TSV attribute add the Actual revenue field

Notice the transaction data populated: value 2000 (20x100)

8. In Modern UX, go to the project financial plan and add the Actual Revenue Per Period Metric

Notice the transaction data is also visible 

9. Create a new transaction for the same date as the prior transaction

Quantity 10

Cost 0

Rate -100

10. Run the Post Transactions to Financials and Post to WIP jobs

11. In Classic UI check the project financial plan

The Revenue value is reduced to 1000 (2000-(10x100))as expected due to the previous negative transaction

12. Check the same in MUX

This is also in sync

13. Create one more negative transaction same as the previous one:

Same day

Quantity 10

Cost 0

Rate -100 

14. Run the Post Transactions to Financials and Post to WIP jobs

15. Check the Classic UI project financial plan 

Revenue is 0 for March as expected. (1000-(10x100))

16. Check now the same in MUX

      The latest transaction has not been deducted and still shows 1000

 

Expected Results: The transaction is to be deducted from the MUX plans and to be in Sync with the plans in Classic

Actual results: The latest transaction has not been deducted and both plans in MUX and Classic are not in sync

Cause

This is caused by DE79915

Resolution

This is fixed in 16.2.2

Additional Information

Once on this state, the Actual revenue Per Period metrics in MUX are editable and changes done get saved.
In Classic if you do any changes to the field after saving they revert back to 0, but the values entered in Classic appear in MUX