Hyperion Financial Data Quality Management (FDM/FDMEE) (MOSC)

MOSC Banner

Issue in EBS-FDMEE Mapping for planning application

edited Mar 9, 2016 8:22PM in Hyperion Financial Data Quality Management (FDM/FDMEE) (MOSC) 6 commentsAnswered ✓

We are implementing Hyperion Planning 11.1.2.4 and using Hyperion FDMEE … In our client scenario we have to bring EBS Actuals data into Hyperion. We defined the mapping between EBS Company to Entity dim, EBS Dept to Dept dim, Account to Account Dim and Product to Product dim. However FDMEE is forcing us to map Version dimension in Hyperion to EBS. Why version is asking for Mandatory mapping from source while defining Import Format? Please, can someone explain on this?

Regards

Santhosh

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

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