Data Mapped Using Fully-Qualified Entity Member Names Will Not Load Into Financial Consolidation & Close Cloud Service (FCCS): "The member...does not exist..."
(Doc ID 2759167.1)
Last updated on FEBRUARY 07, 2024
Applies to:
Oracle Financial Consolidation and Close Cloud Service - Version 21.01.28 and laterInformation in this document applies to any platform.
Symptoms
An FCCS application originally had a single Entity hierarchy in FCCS to which level-0 data was loaded successfully with drill-back capability. After adding an alternate hierarchy under Entity, member names in the Data Management (DM) mappings were updated to fully-qualified nomenclature. Exporting data now fails with an error: "The member <name> does not exist for the specified cube or you do not have access to it."
When viewing the drill-through definition in FCCS, the updated fully-qualified name is not reflected. Refresh Members was performed in DM on the Target Application, and no other parameters have been modified.
Changes
Alternate hierarchy has been added to the application.
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 |
| Changes |
| Cause |
| Solution |
| References |