Activity Level History Or Slowly Changing Dimension Data Not Moving To Data Warehouse Through The Scheduled ODI ETL (LOAD_PLAN_DAILY)
(Doc ID 2388649.1)
Last updated on MARCH 30, 2019
Applies to:
Primavera Analytics Cloud Service - Version 17.11.2.0 and laterPrimavera Analytics - Version 17.11.2.0 and later
Primavera Data Warehouse - Version 17.11.2.0 and later
Information in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
When turning on Activity Level history - Activity Daily, Activity Weekly or Activity Monthly - for a P6 EPPM project, the ODI scheduled ETL (LOAD_PLAN_DAILY) for a P6 EPPM source is not writing data (inserts or updates) for both Slowly Changing Dimension (SCD) history tables or the underlining activity fact history table (example, W_ACTIVITY_HISTORY_F).
Additionally, if data for a project is present in the history tables, changes to data are not reflected in the history tables executing the scheduled ETL (LOAD_PLAN_DAILY) when using activity level history.
EXPECTED BEHAVIOR
When turning on Activity level history for a P6 EPPM project, data should be written to the underlining SCD (*_HD) tables as well as the underlining activity fact history table (W_ACTIVITY_HISTORY_F).
STEPS TO REPRODUCE
The following steps can be utilized to duplicate this issue:
- Login to P6 and create the following project data:
- Create a project **Do not yet enable history for the project
- Create a single WBS record
- Create 4 activities underneath the WBS
- Link all activities with start to finish relationships
- Schedule Project.
- Publish the Project
- Execute 'Publish Security' **This will move security records into W_PROJECT_SECURITY_S
- Execute LOAD_PLAN_DAILY for P6 **This will move the new project into DW
- Set the project within P6 to Activity level history:
- On Project > EPS page, right-click project
- Click 'Set Project Preferences'
- Click Anaalytics & Services page
- Select one of following from History Level dropdown:
- Activity (Monthly)
- Activity (Weekly)
- Activity (Daily)
- Select OK
- Publish the project
- Execute LOAD_PLAN_DAILY for P6
- Results:
- w_project_d properly displays history_level="HL_TASK_MN"
- w_project_history_f properly displays the project record
- all history dimension (*_HD) tables do not display results. Example: w_project_hd, w_activity_hd
- w_activity_history_f does not display the activity records. This is because the merge_history package bases is insert from records existing in the _HD tables (which do not have rows)
- Results:
- Execute LOAD_PLAN_INITIAL_LOAD
- Results:
- All SCD and activity level history tables now display results for the projects configured to use activity level history.
- Results:
- Adjust the activity name within P6 for one of the activities which now have data present in the w_activity_hd table.
- Publish the project
- Execute LOAD_PLAN_DAILY for P6
- Results:
- The w_activity_hd table does not reflect the activity name change.
- Results:
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |