Oracle Hyperion Data Relationship Management (DRM), Fusion Edition functions as a master data management solution where reporting structures are maintained, analyzed, and validated before moving throughout the enterprise. Data Relationship Management does the following:
Manages business entities, hierarchies, attributes, and mappings across multiple systems.
Validates data relationships and calculates attribute values using business rules.
Enforces referential integrity across all subscribing systems and hierarchies.
Enables you to create and manage alternate views.
Merges independent data sets from different sources and combines them into a master set.
Maintains historical versions for comparative reporting and analysis.
Tracks all hierarchy and attribute changes with a full-featured audit log.
Can serve as the main point-of-entry to update subscribing systems or be used subsequently for reconciliation and analysis.
You can use Data Relationship Management to manage charts of accounts segment values and hierarchies for Oracle General Ledger. You can create new segment values, edit their properties, and maintain hierarchies using DRM. This information can be synchronized to one or more general ledger instances using a concurrent request program in the Oracle E-Business Suite.
For more information on how to use Data Relationship Management, see the Oracle Hyperion Data Relationship Management, Fusion Edition, Oracle General Ledger Integration Guide.
You must complete configuration setups in Oracle Hyperion DRM in order to integrate with the Oracle Fusion General Ledger and the Oracle E-Business Suite (EBS) General Ledger. These setups are typically completed by an administrative user.
Create a DRM user.
Load metadata by uploading the application template.
Update the external connections to the Oracle E-Business Suite and Oracle Fusion General Ledger instances.
For more information refer to the Oracle Hyperion Data Relationship Management, Fusion Edition, Oracle General Ledger Integration Guide and the Hyperion Data Management Integration with the Oracle Fusion and E-Business Suite General Ledgers White Paper, Note 1315694.1 on My Oracle Support.
You must perform the following configuration steps in each Oracle General Ledger instance with which you are integrating Data Relationship Management.
You must set several system profile options. The following table provides details about each option.
| Profile Option | Description |
| GL: DRM Username | Set this site-level profile option to the user name for the Data Relationship Management user created during the configuration. This profile option applies only to E-Business Suite. |
| GL: DRM Property for Value Set Name | Set this profile option to be equal to the property that was created in Data Relationship Management to hold the value of the alternate value set for the instance which is being updated. This profile option stores the name of the version-level property in Data Relationship Management, which supplies the value set name for an instance. For example, suppose ACME Corporation creates a Data Relationship Management property entitled, UK Value Sets to link its United Kingdom general ledger value sets to Data Relationship Management versions. In this case, the profile option is UK Value Sets.
Note: This step is required only if you need to store alternate names for value sets with Data Relationship Management versions |
| GL: DRM Property to Allow Version Export | This profile option indicates whether to export values to an instance. If you are exporting to only one general ledger, the default values for this property are correct and do not need to be changed. If you are exporting to multiple general ledgers, then copy the exports provided by Oracle General Ledger as describedConfiguring Data Relationship Management Metadata for Oracle General Ledger chapter of theOracle Hyperion Data Relationship Management, Fusion Edition, Oracle General Ledger Integration Guide. Use the names for the respective exports that you created for the value set and hierarchy exports. |
| GL: DRM Property to Allow Hierarchy Export | This profile option indicates whether to export a hierarchy to an instance. If you are exporting to only one general ledger, the default values for this property are correct and do not need to be changed. If you are exporting to multiple general ledgers, then copy the exports provided by Oracle General Ledger as described in the Configuring Data Relationship Management Metadata for Oracle General Ledger chapter of theOracle Hyperion Data Relationship Management, Fusion Edition, Oracle General Ledger Integration Guide. Use the names for the respective exports that you created for the value set and hierarchy exports. |
| GL: DRM API Adapter URL | Set this profile option to the URL of the Data Relationship Management API Adapter. The Data Relationship Management instance exposes its Web Service operations through this URL. |
| GL: DRM WSDL URL | Set this profile for the DRM WSDL for use by the E-Business Suite Services Invocation Framework (SIF) in accessing the DRM web service. SIF validates the SOAP requests against this WSDL and also derives the endpoint URL (the web service URL). |
| GL: DRM Template for Hierarchy Export | Set this profile to specify which DRM export to use for hierarchy export. If you are exporting to multiple EBS general ledgers, then you should have copied the hierarchy export provided by Oracle (the process for this is described in the Hyperion DRM configuration section of the Hyperion Data Management Integration with the Oracle Fusion and E-Business Suite General Ledgers White Paper, Note 1315694.1 on My Oracle Support). Your company has two EBS instances, North America and the United Kingdom and you want to integrate with DRM. You can use the default hierarchy export provided by Oracle for one of the instances, such as the North America instance. For this instance you will leave the default value for the profile option GL: DRM Template for Hierarchy Export. You must both create and name a new export in DRM for the United Kingdom instance, since exports are connected to specific databases. You then update the value for the profile option GL: DRM Template for Hierarchy Export to use the name of the export that you created. |
| GL: DRM Template for Version Export | Set this profile to specify which DRM export to use for version export. If you are exporting to multiple EBS general ledgers, then you should have copied the value set export provided by Oracle (the process for this is described in the Hyperion DRM configuration section of the Hyperion Data Management Integration with the Oracle Fusion and E-Business Suite General Ledgers White Paper, Note 1315694.1 on My Oracle Support). If your company has two EBS instances, North America, and the United Kingdom and you want to integrate with DRM. You can use the default value set export provided by Oracle for one of the instances, such as the North America instance. For this instance, you leave the default value for the profile option GL: DRM Template. However, you must create and name a new export in DRM for the United Kingdom instance, since exports are connected to specific databases. You then update the value for the profile option GL: DRM Template for Version Export to use the name of the export that you created. |
The Data Relationship Management password must be stored in Oracle E-Business Suite to enable access to Data Relationship Management when loading values and hierarchies. You populate the Data Relationship Management password in E-Business Suite by running a script. This script is stored in FND_VAULT.
The script is run as:
sqlplus apps/apps@db @$FND_TOP/sql/afvltput.sql SQLGL <KEY> <VALUE>
The table below describes the two parameters used in the script:
| Parameter | Value |
| Key | The name of the DRM user stored in the profile option: GL: DRM Username |
| Value | The DRM password for the user identified in the profile option: GL: DRM Username |
Oracle E-Business Suite provides an initialization program that is run from Oracle General Ledger.
Note: This step is only required if you would like to start using DRM with EBS value set values and hierarchies (parent-child relationships).
The Initialize Segment Values and Hierarchies program is run from each general ledger instance to output data for loading into DRM. Each request can extract one value set of segment values and hierarchies. When you select the Initialize Segment Values and Hierarchies program from the Submit Request window, you will then be prompted to select a value from the Value Set Name field within the Parameters window. Request sets can be created to run the request for multiple value sets.
The Oracle General Ledger application template includes an import profile to load the import file produced by the E-Business Suite initialization program. The following Data Relationship Management import profile is included in the application template:
EBSValueSetImport: Loads data created by the Initialize Segment Values and Hierarchies concurrent request program in E-Business Suite
Using DRM as a master data management solution may require data cleansing to transition from disparate sources of information for charts of accounts to a single, unified application. The data cleansing is completed in DRM.
For more information refer to the Oracle Hyperion Data Relationship Management, Fusion Edition, Oracle General Ledger Integration Guide and the Hyperion Data Management Integration with the Oracle Fusion and E-Business Suite General Ledgers White Paper, Note 1315694.1 on My Oracle Support.
Chart of accounts segment values and hierarchies are loaded from Data Relationship Management into Oracle General Ledger using a concurrent request program. The Load Segment Values and Hierarchies request is run from each general ledger instance to retrieve data from Data Relationship Management. Each request can load one value set of segment values and hierarchies. When you select the Load Segment Values and Hierarchies program from the Submit Request window, you will then be prompted to select a value from the Value Set Name field within the Parameters window. Request sets can be created to run the request for multiple value sets.
The Load Segment Values and Hierarchies request will only create or update segment values and hierarchies for the chart of accounts accessible through your general ledger data access setting. The request also requires that only one Data Relationship Management version is defined as the master for each value set using the Value Set Master property.
An accompanying report for the Load Segment Values and Hierarchies request indicates whether the load into Oracle General Ledger is successful and provides summary information about the information imported from Oracle Hyperion Data Relationship Management, Fusion Edition.
Data Relationship Management node types are automatically enabled for hierarchies that are imported from Oracle General Ledger. New hierarchies that are created directly in Data Relationship Management will not have Oracle General Ledger node types enabled without additional configuration.
You must perform one of the following actions to enable node types for new hierarchies to be exported to Oracle General Ledger:
Assign OracleGL.NodeType as the default value of the Hierarchy Node Type property definition in the Core namespace. This configuration will enable node types for all hierarchies using the Node Type property in the OracleGL namespace. This task can be performed by an application administrator only.
Select the Node Type property from the OracleGL namespace for the value of the Hierarchy Node Type property in the System category for each new hierarchy created.
For more information refer to the Oracle Hyperion Data Relationship Management, Fusion Edition, Oracle General Ledger Integration Guide.
The Data Relationship Management data model is significantly different from that of the Oracle E-Business Suite. Data Relationship Management groups multiple hierarchies consisting of multiple nodes into one or more versions, whereas Oracle E-Business Suite has multiple chart of accounts value sets (segments), each with segment values (nodes). For an example comparing the Oracle General Ledger and Data Relationship Management data models refer to the Managing Segment Values and Hierarchies for Oracle General Ledger chapter in the Oracle Hyperion Data Relationship Management, Fusion Edition, Oracle General Ledger Integration Guide.