Questions About Deleting Dimension Members Using fn_drmDataLoader Batch Dimension Loader
(Doc ID 2422967.1)
Last updated on MARCH 22, 2023
Applies to:
Oracle Financial Services Analytical Applications Infrastructure - Version 8.0.2 to 8.0.7.4.0 [Release 8]Information in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
Oracle Financial Services Analytical Applications Infrastructure (OFSAAI)
Oracle Financial Services Profitability Management (PFT)
Oracle Financial Services Funds Transfer Pricing (FTP)
Oracle Financial Services Asset Liability Management (ALM)
Data Relationship Management (DRM)
Goal
Question 1: On OFSAA 8.0.5 when using the batch framework, ran a new months dimension data with sync flag = Y. However, the following error is returned:: Error. Cannot delete a member which is used in a hierarchy. Expected that when setting the sync flag to Y, the hierarchy validation would not occur and any records in the DIM table not present in the STG tables would be deleted.
Question 2: On OFSAA 8.0.5: Also, for another dim have set sync flag = N because of the need to maintain custom nodes in a hierarchy created in the UI and that do not exist within DRM. However, when load this process, ORA-0001 unique constraint violation occurs. What is the proper way of maintaining those custom items?
Solution
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
| Goal |
| Solution |
| References |