TSV type attribute 'cost' has invalid segment start or finish dates on cost plans.
search cancel

TSV type attribute 'cost' has invalid segment start or finish dates on cost plans.

book

Article ID: 370768

calendar_today

Updated On:

Products

Clarity PPM SaaS

Issue/Introduction

In MUX, cost plans where the investment is in a different entity using different fiscal periods the periods cannot be edited even using the correct period type.
Receive Error: TSV type attribute 'cost' has invalid segment start or finish dates.

STR:

1. Create a new entity and set the fiscal periods to be different than the default entity.
   - In my example the default entity had Calendar periods 
   
2. New entity fiscal periods went from the 15th of the month to the 14th of the next month.
   Annual periods followed the current year but started on the 15th of the year.

3. Create a project and financially enable it to use the new entity

4. In MUX create plan.  

5. Note that the View Options are Monthly (as is in the plan) and using Cost Plan Start and Cost Plan Finish and showing the periods for the Default Entity.

6. Create a line on the manual plan and enter a value in one of the per-period metrics.   


Expected Result:  Value saves
Actual Result:   Error: TSV type attribute 'cost' has invalid segment start or finish dates.

You can populate the plan but you cannot make any changes to the per-period metrics.


Workaround:  You would need to change the default entity to enter the monthly per-period metrics.

Resolution

Reported as DE94894 and requesting a solution other than changing the default entity or editing the values in Classic.