This month, we have had the opportunity to assess the Oracle Hyperion Data Relationship Manager (DRM) template Oracle is creating for the E-Business Suite General Ledger (EBS-GL).
PLEASE NOTE: the first production release of this product will be available with Oracle E-Business Suite Release 12.2 and could be very different from the beta version we have seen.
For those who don’t know much about EBS-GL, a GL account code is made up of a combination of flexfields, each of which defines a key business concept. For example, a flexfield could hold company codes, natural accounts, or products. Each of these flexfields then uses a defined value set, which represents the list of valid codes for that flexfield and any associated hierarchies.
The Oracle Hyperion DRM template focuses specifically on the governance of EBS-GL value sets and their hierarchies. It allows users to extract masterdata from EBS-GL into DRM, control the value sets and hierarchies in DRM and then publish changes directly into EBS. In essence it moves the management of EBS-GL masterdata into DRM. Their approach has been to separate each value set into separate versions.
What we liked – The template comes with the complete integration between EBS and Oracle Hyperion DRM. EBS users can “pull” the valid values from Oracle Hyperion DRM into EBS. They simply have to execute an E-Business Suite Request called “Load Segment Values and Hierarchies” and specify the Value Set they wish to see updated. A workflow then triggers the required DRM exports and processes the master data into Oracle Hyperion DRM using the API.
What we struggled with –The power of Oracle Hyperion DRM rests with its ability to manage the relationships between the masterdata from different systems. For instance it could be used to align and map important masterdata between an ERP and EPM layer. In Oracle Hyperion DRM these relationships should be enforced using business rules (or validations). This calls into question the decision to separate the different flexfields into separate versions as validations are not capable of performing checks between versions.
Our final observation is that the template cannot yet manage the valid combinations of flexfields. We would hope to see this in the final release.
For those who wish to read more detail about the integration, Oracle released this Oracle General Ledger Integration Guide. Alternatively, if you have questions about governing E-Business Suite using Oracle Hyperion DRM then please get in contact.