Business Process UDF Mapping, Which Exceeds the Default Number of Allowed Mappings, Not Brought Into Data Warehouse via ODI ETL
(Doc ID 2342512.1)
Last updated on MARCH 31, 2019
Applies to:Primavera Analytics Cloud Service - Version 18.104.22.168 and later
Information in this document applies to any platform.
UDF Mappings are not coming over into Data Warehouse through the Daily ETL load plan execution when exceeding the initial, default value amount within Unifier's Analytics node.
- Default BP Main Form String allows 60 mappings.
- Increasing this to 200 and attempting to display values from any UDF string mapped to udf_test_61 or higher properly publishes to the Unifier staging table but does not get brought into the associated fact/dimension table when running a Data Warehouse ETL.
UDF mapping values which exceed the initial, default number within the Unifier Analytics node to be added into the associated dimension / fact tables when running a Data Warehouse ETL.
The issue can be reproduced at will with the following steps:
1. Login to Unifier
2. Select Company Workspace > Analytics node.
3. Select Business Process > Open.
4. Add a BP mapping then apply.
5. On Custom fields tab, in Main Form, adjust "number of strings" = 200, then apply.
6. On Data Mapping tab, add a user defined field, and map it to a UDF text field > 61 (my test, mapped Project Name to User Defined String Field 102).
7. Select Apply and OK.
8. Run Unifier schedule.
9. Confirm the mapping is present by running following direct SQL against Unifier (done within staruser schema):
- select bp_name, udf_text_102 from sys_stg_bp@dslink02 --using example of mapping string field 102
- results show a bp_name and project name value in the text UDF
10. Execute the daily ETL against Unifier data source
- Note, no errors during execution
11. Once ETL completes, run following direct SQL against data warehouse:
- select bp_name, udf_text_102 from w_bp_d -- using the example of mapping to text field 102
- BP Exists
- Text UDF = null
The issue has the following business impact:
Due to this issue, users cannot properly report on any UDF mapped fields which exceed the default values specified.
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