Migrating Essbase Data between Different Hyperion Planning Versions
I need to migrate Essbase data from an Hyperion Planning 11.1.2.2 source system to an upgraded 11.1.2.4 target in Development. The source system data is considerably more recent than the target.
Ordinarily I would LCM the entire source planning application to the target before importing the data knowing that the outline in the Planning repository will then match exactly all the member combinations in the source Essbase data files.
However I understand I cannot use LCM as an interface between these two versions of Planning?
If I just try to import the source data into the older target system I will hit issues with numerous invalid member combinations.