wilel06

CA PPM Tuesday Tip: Populating cost plan does not recognize mid-month dates in the rate matrix.

Discussion created by wilel06 Employee on May 5, 2015
Latest reply on May 6, 2015 by navzjoshi00

When creating a cost plan by populate and there are multiple rates in a month for a resource(s) the cost will be based on the rate on the first day of the month.

For example:  You have a ‘catch all’ rate in the Rate Matrix from 1/1/2015 to 12/31/2015 with asterisk in each column with a rate and cost of $0

Then you create a new row in the Rate Matrix for the specific resource matched from 1/15/2015 to 12/31/2015 with a rate of $50.

When the cost plan is populated the cost for January will be $0 even if there are units covering the whole month.

 

Steps to Reproduce

  1. Create Resource
    2. Financially enable the Resource (does not matter what options are chosen)
    3. Create Rate Matrix
    a. Assign columns in this order
    i. Resource Role
    ii. Transaction Class
    iii. Resource Class
    iv. Input Type Code
    v. Resource
    b. Create 2 Rows
    i. Row 1
    a. dates 1/1/2015-12/31/2015
    b. All Columns with *
    c. $0 for all Rates
    ii. Row 2
    a. Dates 7/10/2013-12/31/2013
    b. Resource Role = *
    c. Transaction Class = LABOR (or something)
    d. Resource Class = *
    e. Input Type Code = *
    f. Resource = resource you created
    g. $2 for all rates
    4. Create Project with dates 7/1/2013-9/30/2013
    a. Financially enable the project include location/department
    b. Assign the resource you created to the Team
    c. Set allocation segments
    i. 7/1/2013-7/9/2013 = 0%
    ii. 7/10/2013-9/30/2013 = 100% so the resource has some allocation hours
    5. Run Rate Matrix Extraction Job
    6. Create a Financial Cost Plan on the Project - From Investment Team

 

 

 

Expected Result:

January would have some cost

 

Actual Result:

January cost is $0

 

Work Around:

Change the from date in the rate matrix to the 1st of the month.

 

 

This issue has been reviewed as defect CLRT-72717 and will not be addressed at this time as the work around is acceptable.

Outcomes