Re-ordering Of Dense Dimension Account Members after Migration
Last updated on JULY 28, 2016
Applies to:Hyperion Planning - Version 220.127.116.11.600 and later
Information in this document applies to any platform.
During the process of subsequent metadata migrations, the local application’s Account parent/member order became alphabetical, in EPMA, which of course does not match the ordinal positioning in the Shared Library.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms