Cost Plans created with different Per-Period Metrics than the cost plan period type do not show in DWH correctly.
search cancel

Cost Plans created with different Per-Period Metrics than the cost plan period type do not show in DWH correctly.

book

Article ID: 248677

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

If a cost plan is created as monthly but before the costs are added to the plan the per-period metrics are changed to annual (which should peanut butter spread the values) only  the first month of each year shows in the DWH.

 

 

Steps to Reproduce: 

1.  Create a Custom Investment and Include it in DWH
2.  Create an instance of the custom investment
3.  Create a cost plan for that instance
    - Make it for 2 years (1/1/2022-12/31/2023)
 - Make period type = MONTHLY
 - Grouping Attributes:  Cost Type, Transaction Class
4. Change the Per-Period Metrics to Annual
   - Cost Plan Start and Cost Plan Finish for the dates
   - Cost in the  per-period metric
5. Add values for each year (2000, 4000)
6. Run full load of DWH   


Expected Results: In creating an ad-hoc view or viewing reports such as Financial Forecast Review by Investment you should see Planned Cost of 6,000


Actual Results:  Financial Forecast Review by Investment Planned = 424.66.  This is the total of the cost for 1/1/2022 and 1/1/2023. The other months are not in the DWH
                 

Workaround: Do not change the Per-period metrics when populating the plan

Environment

Release : 16.0.2, 16.0.3

Component : Clarity Data Warehouse

Cause

If the values in the cost plan are entered in Annual when the plan is actually monthly, the values will spread based on days and show correctly in Clarity. However the DWH is only getting values for the first period of each year.

 

Resolution

Reported as  DE66346 and it was determined that if you have the option Consistent Fiscal Periods across Entities checked on System Options you will experience this behavior.

Documentation has been updated to leave the option unchecked unless you experience performance issues with Load DW job when populating plan data facts.