Data Warehouse W_UDF_PROJECT_D And W_UDF_PROJECT_F Tables Are Not Populated From ODI ETL Causing Analytics To Return No Data If Adding Project UDFs

(Doc ID 2326711.1)

Last updated on NOVEMBER 09, 2017

Applies to:

Primavera Analytics Cloud Service - Version 17.7 and later
Primavera Data Warehouse - Version 17.7 and later
Primavera Analytics - Version 17.7 and later
Information in this document applies to any platform.

Symptoms

ACTUAL RESULTS
----------------------------------------------
After running an ODI ETL (either a daily ETL or a a full ETL running the initial load plan), mapped project UDFs are not brought into the STAR W_UDF_PROJECT_D or W_UDF_PROJECT_F tables. This results in any OBIEE analysis using a subject area with the UDFs (for example, Cost Sheet Analysis with Project UDFs added) from not returning any data.



EXPECTED RESULTS
----------------------------------------------
After running an ODI ETL (either a daily ETL or a a full ETL running the initial load plan), mapped project UDFs should be brought into the STAR W_UDF_PROJECT_D or W_UDF_PROJECT_F tables.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:

  1. Login to the Data Warehouse ETL web based application.
  2. Execute an ETL for Unifier
  3. Once the ETL completes:
    1. Login to OBIEE
    2. Select New, Analysis, Create Direct Database Query
    3. In Connection Pool, enter: Oracle Primavera P6 Data Warehouse Connection Pool
    4. In SQL Statement, enter: select processid, processname, infomsg, infotype, rows_processed, datasource_id from etl_processinfo where tablename = 'W_UDF_PROJECT_D' order by 1 desc;
    5. Select "Bypass Oracle BI Presentation Services Cache"
    6. Select Validate SQL and Retrieve Columns
    7. Select Results
    8. Notice no rows are processed from the rows_processed column
    9. Repeat steps a-h running select processid, processname, infomsg, infotype, rows_processed, datasource_id from etl_processinfo where tablename = 'W_UDF_PROJECT_F' order by 1 desc;
Note: This also occurs when executing the LOAD_PLAN_INITIAL_LOAD via ODI Studio.



Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms