4 Using Data Relationship Management with FDMEE

Oracle Data Relationship Management may be used to manage financial master data entities which include chart of account values and hierarchies used for general ledgers in ERP systems such as E-Business Suite (EBS), Peoplesoft (PS), and Fusion Financials(FS). Data Relationship Management is also used to manage dimension members and hierarchies for EPM applications such as Financial Management, Planning, and Essbase, which often source transactional data from these same ERP systems. Oracle Hyperion Financial Data Quality Management, Enterprise Edition is used to load transactional data from these ERP systems to Oracle EPM applications.

In some cases, the dimensionality and granularity of the target EPM application does not match the source system and mappings must be defined between the source and target in order to appropriately transfer and load the transactional data from the ERP system to the EPM application. FDMEE provides the ability to natively manage mappings between source ERP segment values and target EPM dimension members explicitly or using rules (range, wildcard, script). When Data Relationship Management is used as a master for dimension members of the EPM applications, Data Relationship Management may also be used to manage mappings of ERP segment values to those dimension members and synchronize those changes to FDMEE for use by transactional data loading processes.

The main advantage of maintaining explicit mappings in Data Relationship Management is to be able to validate integrity and record auditing information for each mapping at the time of making the change. This is not easily accomplished with rule-based mappings in FDMEE. You can use ancestor relationships from Data Relationship Management hierarchies to map multiple values at the same time or you can use queries/compares with multi-select to map multiple values at the same time.

For each FDMEE location, the user gets to decide whether to use explicit mappings or rule based mappings. If rule-based mappings are preferable, then use FDMEE for those mappings. If you want to use Data Relationship Management to manage the mappings along with the GL segment values and/or EPM dimension members being managed in Data Relationship Management, then you would use explicit mappings in Data Relationship Management and load those mappings into FDMEE.