Scenario: Recently, we were trying to recreate a HFM application in new environment. It was planned to create a shell HFM application first, later, each dimension will be updated by importing the .csv file each dimension at a time. Shell application was created, and dimensions was created by importing the.csv file except the Entity dimension.
Note: Entire application lift and shift (using LCM) was not recommended in this scenario due to some factors.
Issue: When Admin user was tried to load Entity dimension in "Replace" mode, there was error of "Referential Integrity Constraint". Due to this, Entity dimension was not getting updated. However, Entity dimension was getting updated in "Merge" mode.
Finding: It was found there was a "Member List", loaded into application, in which Entity dimension member were used. HFM will not allow to delete any dimension member if that member is used anywhere (like, in member list, Data form, Data Grid, Rule, IC Reports). This is why Entity dimension was not getting loaded in "Replace" mode of loading metadata. In "Merge" mode of loading metadata, it will not delete the existing member and will add additional members to existing hierarchy.
Solution: Member list was removed from HFM application and metadata was successfully loaded into application in Replace mode.
Thank you!
Created by - Mohit Jain & Megha Gupta
No comments:
Post a Comment