My Oracle Support Banner

Data Warehouse / Analytics Cannot Distinguish Code Or UDF Mappings Between Multiple P6 EPPM Data Sources In A Single Data Warehouse Schema (Doc ID 2428980.1)

Last updated on APRIL 13, 2022

Applies to:

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

Symptoms

ACTUAL BEHAVIOR
When Data Warehouse is holding multiple datasources for P6 EPPM, W_XLAT_S (the translation table holding code/udf mappings) will get updated to reflect the translations for the associated datasource when the ETL is executed.

This makes W_XLAT_S incapable of distinguishing mappings (udf or code) between multiple P6 EPPM schemas. This also results in Analytics from reflecting proper translation-to-mapping IDs.

Example using project code mappings:

This will create issue/confusion when creating analyses since the incorrect translation name is displayed.

The issue gets compounded when the translations are being mapped to non sequential values because now it will display a single list of translations for all P6 EPPM datasources, where the translation name will update for the datasource ID an ETL is executed against but leave the non-mapped ID values the same (since they relate to other P6 EPPM datasources). This can cause duplicated names/translations to display (if a code/udf share names between environments but map to different IDs), or display mappings that dont relate between datasources. See Project Activity And UDF Codes Missing Or Write To Wrong ID In Star Schema After ETL Run (Doc ID 2430317.1).

EXPECTED BEHAVIOR
The translations for code/udfs must properly distinguish between multiple P6 EPPM environments.


STEPS TO REPRODUCE

  1. Setup Data Warehouse for two P6 EPPM datasources
  2. For datasource 1, map 3 codes/udf (to ID 1,2,3)
  3. For datasource 2, map 3 codes/udf (to ID 1,2,3) with different names
  4. Execute ETL for datasource 1
  5. Execute ETL for datasource 2
  6. Note the translation names for datasource 1 are no longer valid in W_XLAT_S.

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
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.