ASO to ASO Data Sync For FDMEE Large Dimensions Are Not Pulling in Member Names When Set to Level 0 Descendants
(Doc ID 2139551.1)
Last updated on MARCH 11, 2019
Applies to:Hyperion Financial Data Quality Management, Enterprise Edition - Version 220.127.116.11.000 and later
Information in this document applies to any platform.
Performing a refresh on members of large dimensions results in an error and the members are not pulled into FDMEE (refreshed).
The data for all members does come through in the data sync.
The members for the large dimensions do not show their associated names.
Error from Erpintegrator0.log indicates that there are unmapped dimensions:
2016-02-04 11:14:35,462 INFO [AIF]: Data Rows Marked as Invalid: 10871
2016-02-04 11:14:35,462 ERROR [AIF]: Error: Data rows with unmapped dimensions exist for Period 'Jan-2015'
2016-02-04 11:14:35,462 DEBUG [AIF]: CommData.updateWorkflow - START
2016-02-04 11:14:35,462 DEBUG [AIF]:
WHERE PARTITIONKEY=22 AND CATKEY=2 AND PERIODKEY='2015-01-31' AND RULE_ID=102
2016-02-04 11:14:35,462 DEBUG [AIF]: CommData.updateWorkflow - END
2016-02-04 11:14:35,462 INFO [AIF]: Total Data Rows available for Export to Target: 0
2016-02-04 11:14:35,462 FATAL [AIF]: Error in CommMap.validateData
Traceback (most recent call last):
File "<string>", line 2622, in validateData
RuntimeError: [u"Error: Data rows with unmapped dimensions exist for Period 'Jan-2015'"]
Data Sync is a new feature in 18.104.22.168 and for this feature to work, the dimension name & alias is required to be the same. It is the way the new feature is currently designed.
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