This content has been marked as final. Show 4 replies
Metadata rules refresh the code combination ID to member name relationship (from eBS). You must refresh the metadata rule (in ERPi only) before running a data rule to ensure that you get all records.
Please take moment to flag any responses that you find useful or correct.
Thanks for your response Tony.
If I understood your answer, you are saying that I must run a Metadata extract in order to get all the latest code combination updates. Correct? What would you suggest to someone that absolutely cannot run the Metadata extract because it would overwrite the hierarchies in Essbase that have been so meticulously maintained offline thus far ? Is there a back end solution to update these new code combinations ? By the way, where are these code combinations maintained ? In the Planning repository tables ? if so, which schemas ? (Not that I would try to manually manipulate them). Thanks Tony.
You can modify the process to not load to Planning when you run the metadata rule. The code combination IDs are refreshed in ERPi and then pushed over to EPMA (or Planning if using classic). By modifying the process to not load past erpi, you get the update IDs and thereby the full data set.
I love your idea. I'm going to test it. Thanks Tony.