Hyperion Planning (MOSC)

MOSC Banner

EPMA Merge As Moved Clarification

edited Aug 27, 2015 7:38AM in Hyperion Planning (MOSC) 1 commentAnswered ✓

Hello Community,

I'm looking for some clarification on the meaning of Merge As Move when importing EPMA interface tables into Planning.  I have gone through documentation and message boards and just can't seem to grasp the full meaning of this.  I had thought that when using this option on import profiles that it deals only with existing members (not new ones) between the source and destination.

As an example lets say that in the source interface table a member called child 1 belongs to parent 2.  Prior to the import, child 1 belongs to parent 1.  After the import profile has been executed, with the Merge As Move option, child 1 will belong to parent 2 in the app.  Now let's say we have a new member child2 that exists in the source interface table belonging to parent 1 that does not currently exist in the app.  Does executing the import profile with Merge As Move as the process option insert this new member under parent

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

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center