Data Warehouse W_XLAT_S Table Are Not Populated With Actual Code or UDF Mappings After Running A Daily ETL (Through ODI) For A P6 Datasource

(Doc ID 2336469.1)

Last updated on DECEMBER 06, 2017

Applies to:

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

Symptoms

ACTUAL RESULTS
----------------------------------------------
After running an ODI Daily ETL, mapped codes or UDFs are not brought into the STAR W_XLAT_S table. This results in any P6 EPPM Subject Area referencing a code or UDF mapping to not display the proper translation name when creating a new Analysis.



EXPECTED RESULTS
----------------------------------------------
After running an ODI Daily ETL, mapped codes or UDFs should be brought into the STAR W_XLAT_S table and allow proper translations to display for P6 EPPM subject areas while creating a new analysis.


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

  1. Login to the Data Warehouse ETL web based application.
  2. Execute a Daily ETL for P6 after mapping codes or UDFs
  3. Once the ETL completes, note that that any P6 EPPM subject area does not display the proper translation name while creating a new analysis.

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