My Oracle Support Banner

Code Values Do Not Get Brought Into Data Warehouse When The Code Type Name Contains A Long Dash In The Name (Doc ID 2431521.1)

Last updated on AUGUST 03, 2018

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 a mapped P6 EPPM UDF or Code name contains a long dash, it is stored in the P6 EPPM extended schema as a short dash but the Analytics Administration Application / star Configuration Wizard treats it as a long dash (as it technically should).

This creates a situation where the code or udf name value is inserted into the ETL_PARAMETER table with a long dash, but causes the EXTRACT2STAGING
procedure insert statement to fail on it's match when writing to the associated staging table (for example, with UDFs, W_UDFTYPE_DS) since the
value is stored with a short dash in the extended schema.

In the end:

EXPECTED BEHAVIOR
When a long dash is added within P6, it seems to reflect it as a long dash but treats it as a short dash when copy/pasting from the field in P6 and/or selecting the value in the associated table.

The Data Warehouse Analytics Administration Application and star Configuration Wizard will need to do the same thing (treat long dashes as short dashes) so that it is added into ETL_PARAMETER as a short dash allowing the match between both applications.

 

STEPS TO REPRODUCE:
Using Project Text UDF as example to reproduce:

  1. Open MS Word and enter text with a "-" between words. this will convert the short hyphen into a long hyphen.
  2. Update a Project UDF with the text typed from step 1:
    1. Login to P6
    2. Click Administer > Enterprise Data > Projects > Project UDFs
    3. For a text UDF, copy the text from step 1 and paste into 'User Defined Field' name field
    4. Save changes
  3. Map the udf to Analytics:
    1. Login to the Analytics Admin app
    2. Browse to datasource > UDFs
    3. Click Project > Text
    4. Move the udf to the enabled grouping.
    5. Save changes
  4. Execute ETL
  5. Note that the code values are not present when attempting to execute an analysis

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!


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