ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Assignments in resource report incorrect: DWH_INV_ASSIGN_PERIOD_FACTS issue


Article ID: 126273


Updated On:


Clarity PPM On Premise Clarity PPM SaaS


Assignment values on the time scale of the Resource Allocations and Assignments report are incorrect after running an incremental instance of the Load Data Warehouse (DWH) job.

The Load DWH job produces inconsistent data tables results. The incremental job runs successfully but produces different data table values & counts between each hourly run.

Steps to Reproduce:

  1. Run a full instance of the Load DWH job
  2. Once the job completes, 

    run this query in PPM database and confirm that it returns x number of rows. 
    select * from DWH_INV_ASSIGN_PER_FACTS_V
    where ASSIGNMENT_KEY in (5142739)

    run the equivalent query in the DWH database and confirm that it returns the same x number of rows. 
    where ASSIGNMENT_KEY in (5142739)
  3. Go to the project having the task with this assignment. 
  4. In the Gantt, create a new task at the bottom of the list.
  5. Leave all the defaults, and assign any resource, change the ETC to 5 hours. Save the change, and click on Save and Return
  6. Look for the task that has the assignment from the two queries above.
  7. Make any change to the TASK, such as Close or Open for Time Entry, Save and Return
  8. Run the Time Slice job - this step is optional and not required to reproduce the issue
  9. Run an incremental instance of the Data Warehouse job

Expected Results: The two queries above still return the same results
Actual Results: The Clarity query returns the same results, but the DWH query returns 0 rows


Caused by DE48508. This is due to fact records being removed from the DWH_INV_ASSIGN_PERIOD_FACTS table in the Data Warehouse.


Release: 15.6, 15.6.1, 15.7
Component: Clarity Data Warehouse


DE48508 is fixed in 15.7.1 and also in patch and higher.

Workaround: Run a full load instance of the Data Warehouse job as this will re-include the missing fact records.

Additional Information

See also