Hyperion Planning (MOSC)

MOSC Banner

Migrating Essbase Data between Different Hyperion Planning Versions

edited Aug 15, 2016 6:43AM in Hyperion Planning (MOSC) 6 commentsAnswered ✓

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.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center