Investment Allocation Job - Purpose & Overview

book

Article ID: 22834

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

What is the purpose and functional details of the 'Investment Allocation' job in Clarity?

Environment

Release: All 
Component: Clarity Project Management

Resolution

The Investment Allocation job updates the INV_INVESTMENTS table for the LABOR_ACTSUM, LABOR_ETCSUM, LABOR_BASESUM and LABOR_EACSUM fields based on the labor resources allocated to the investment.
The data computed and stored in these fields only pertain to investments that can have actual team members and can have actual effort posted directly into the investment.  
  • It calculates the sum of the Estimate To Complete values for all the investment's labor assignments and stores the value in the LABOR_ETCSUM field. 
  • It calculates the sum of the Estimate At Completion (Total Effort) values for all the investment's labor assignments and stores the value in the LABOR_EACSUM field.
  • It calculates the sum of the Actual values for all the investment's labor assignments and stores the value in the LABOR_ACTSUM field. 
  • It calculates the sum of the Baseline values for all the investment's labor assignments and stores the value in the LABOR_BASESUM field.
The Project Object has attributes that use these database fields as data source, a typical usage is configuring the Actuals attribute on the Project List view.  As noted above, the data in these fields are only computed and stored on investments with direct labor team members and direct posted actuals.  Therefore, if you are looking for an 'aggregated' or 'rollup' value on a Program, Master Project or Parent Investment (hierarchy investment) within the List View, you will not see the data 'rollup' or 'aggregated'.  For any aggregation related to a hierarchy on any Investment type, in Classic, navigate to the Project, Hierarchy tab for this information.

Additional Notes:
  • If this job is not run, the Actuals column on Project List page does not get updated with new actuals that have come in since the last time the job was run. (See Actuals missing on Project List page for one or more projects for more details on the symptoms of this issue)
  • The job only processes active investments.  (This was implemented starting with Clarity PPM v12.1.0 as fix for CLRT-46880)
  • This job may influence data or performance in Demand Management.
  • You can run this job immediately or on a scheduled basis.
  • When a XOG write action is performed to update projects, the Investment Allocation job is automatically executed so that after the successful XOG action, the end-user is able to immediately see all updated data on the project(s).

  

Prior to 16.0.2:

  • Job Name = Investment Allocation  
  • The job does not process Custom Investment Types (CITs) 
  • Parameters: None
  • Investment-level Fields for Labor data updated by this job: 
    • Actuals Sum for Labor Resources (number)
    • Actuals for Labor Resources (time-varying) 
    • ETC Sum for Labor Resources (number) 
    • ETC for Labor Resources (time-varying) 
    • EAC Sum for Labor Resources (number)
    • EAC for Labor Resources (time-varying) 
    • Current Baseline Sum for Labor Resources (number)
    • Current Baseline for Labor Resources (time-varying)
    • Current Baseline Variance Sum for Labor Resources (number)  
    • Current Baseline Variance for Labor Resources (time-varying) 

  

Release 16.0.2: 

  • Job Renamed to 'Update Investment Allocations and Usage
  • Job Description = ‘Update Labor Allocations, Actuals, ETC, Total Usage, Baseline Usage and Baseline Variance on Projects, CITs and NPIOs.’ 
  • New Job Parameters (single-value lookups) added to the job:
    • Investment name 
    • Manager name
    • OBS Unit
    • OBS Mode 
  • Investment-level Fields for Labor data updated by this job: 
    • Actuals Sum for Labor Resources (number)
    • Actuals (time-varying) 
      • Field Name Changed in 16.0.2
      • Prior to 16.0.2 Field Name = 'Actuals for Labor Resources'
    • ETC Sum for Labor Resources (number) 
    • ETC (time-varying) 
      • Field Name Changed in 16.0.2 
      • Prior to 16.0.2 Field Name = 'ETC for Labor Resources' 
    • EAC Sum for Labor Resources (number)
    • Total Usage (time-varying) 
      • Field Name Changed in 16.0.2 
      • Prior to 16.0.2 Field Name = 'EAC for Labor Resources' 
    • Current Baseline Sum for Labor Resources (number)
    • Current Baseline for Labor Resources (time-varying)
    • Current Baseline Variance Sum for Labor Resources (number)  
    • Current Baseline Variance for Labor Resources (time-varying) 
    • (new) Allocation (time-varying)
      • Investment total allocations for labor resources
    • (new) Hard Allocation (time-varying) 
      • Investment total hard allocations for labor resources
  • The ‘Current Baseline Usage’ and ‘Current Baseline Variance’ fields are NOT shown in the Modern UX. The other fields are seen in both Classic & Modern 

  

Scheduling Recommendation:

  • Execute this job after processing Timesheets and Financial Actual transactions.
  • Select at least 1 parameter to target updating specific investments by a single investment, by Investment Manager or by OBS Unit.  
  • If NO parameters are selected, it will process all active investments and could take a long time to execute.  
  • You may want to update the job definition to make this job incompatible with the Time Slicing and Time Slicing Sync job if you run into issues with deadlocks. 

 

  

Additional Information

The user associated with the scheduled job run will show up on the Project Audit Trail, if enabled.

See also: