drm white paper

An Oracle White Paper

November 2012

Hyperion Data Management Integration with the Oracle Fusion and E-Business Suite General Ledgers

Introduction ....................................................................................... 2

Background Concepts ....................................................................... 3

DRM Administrative Configurations ................................................... 4

Initial Load of Values from EBS ......................................................... 8

Hyperion DRM Configuration Prerequisite ..................................... 9

Initialization Steps ........................................................................ 10

Orphan Nodes ............................................................................. 13

Initialization with Multiple EBS Instances ..................................... 14

Optional Administrative DRM Configurations ................................... 14

EBS and Oracle Fusion Administrative Configurations .................... 19

Optional Steps ............................................................................. 20

Business User Configurations ......................................................... 23

Ongoing Business Processes .......................................................... 29

Integration of Translated Values ...................................................... 32

2 Hyperion Data Management Integration with the Oracle Fusion and E-Business Suite General Ledgers

Introduction

Integration between Oracle Fusion Accounting Hub and Hyperion Data Relationship

Management, Fusion Edition (DRM) provides the ability to synchronize chart of

accounts values and hierarchies. Customers can maintain charts of accounts values

and hierarchies centrally in a single application, Hyperion DRM, and then propagate

updates to multiple E-Business Suite (EBS) and/or Fusion instances.

Figure 1 DRM with EBS and Oracle Fusion

There are several advantages to this process.

Expanded functionality: DRM is a best-in-breed solution for master data management for charts of accounts and hierarchies.

Maximize efficiency: no duplication in data entry.

Increased accuracy: DRM serves as a single source of truth for all charts of accounts and hierarchies.

This functionality is especially useful for customers who are using Applications

Unlimited co-existence architecture. Applications Unlimited co-existence refers to an

architecture that combines use of selected E-Business Suite and Oracle Fusion

applications. In this case, Applications Unlimited co-existence is when a customer

continues to use the E-Business Suite General Ledger for processing and the Oracle

Fusion Accounting Hub for financial reporting and analytics.

An Applications Unlimited co-existence configuration allows customers to take

advantage of significant new Oracle Fusion features such as the ability to quickly


execute online inquiries with step-by-step drilling and pivoting across all dimensions

and hierarchies such as the chart of accounts and organizational structures.

Because Oracle provides Hyperion DRM to E-Business Suite and Oracle Fusion

integration, Applications Unlimited co-existence is possible without dual maintenance

of charts of accounts and hierarchies.

You must license Hyperion DRM, Fusion Edition to take advantage of this integration.

Background Concepts

Hyperion DRM provides a user interface for creating versions, hierarchies, and nodes.

This is used to maintain charts of accounts values and hierarchies.

Both Oracle Fusion and the E-Business Suite general ledgers use value sets to maintain

values for their charts of accounts. This continues to be true when customers use

Hyperion DRM for chart of accounts and hierarchy maintenance.

The DRM application is used to make updates and changes to DRM versions and

hierarchies. The results of these changes are exported to the Oracle Fusion and E-

Business Suite General Ledgers value sets, EBS hierarchies (parent-child

relationships), and Oracle Fusion Trees.

Each DRM Version which is to be exported to Oracle Fusion and/or EBS must contain

the name of the value set for the exported segment values. You can synchronize

multiple instances using the same Hyperion Version.

Oracle has provided DRM properties to store segment value attributes, such as account

type and start/end dates; providing the ability to enter such values in DRM and

integrate them to Oracle Fusion and/or EBS.

There are standardized EBS Standard Request Submission (SRS) / Fusion Enterprise

Schedule Service (ESS) requests that can be submitted from both the E-Business Suite

and the Oracle Fusion General Ledgers to import values from DRM. The requests

must be submitted from each general ledger that uses DRM as its source for charts of

accounts values/hierarchies. Only independent value sets are eligible for integration.

When DRM is used as a source of truth for chart of accounts and hierarchies,

customers should not make chart of accounts and/or hierarchy or parent-child

relationship updates directly in either Oracle Fusion or EBS. Such changes will not be

integrated to DRM.


DRM Administrative Configurations

This section includes configuration steps that are completed in Hyperion DRM to

integrate with the Oracle Fusion and EBS General Ledgers. These steps are typically

completed by an administrative user.

These configurations assume a new implementation of Hyperion DRM. These steps

also assume that you have installed and configured the Hyperion DRM web service, as

per the standard installation and configuration guide for DRM. DRM documentation is located at:

Oracle Hyperion Data Relationship Management, Fusion Edition Installation Guide:

http://download.oracle.com/docs/cd/E17236_01/epm.1112/drm_install_111

21.pdf

Oracle Hyperion Data Relationship Management, Fusion Edition Administrator's

Guide:

http://download.oracle.com/docs/cd/E17236_01/epm.1112/drm_admin.pdf

If you are already using DRM, some of these steps may be optional.

1. Create a DRM user. Navigation: Administer New (from toolbar) User Figure 2. Create User


Follow standard DRM procedures for creating users, with the following additional

guidelines.

For Oracle Fusion, identity propagation is used to leverage the same user

credentials for both the Fusion and DRM user. The username has to be the same as

the username who will be used in Oracle Fusion to launch the request to load

segment (account) values and hierarchies. The Oracle Fusion username is

propagated to DRM after users submit the request in Oracle Fusion to synchronize

with DRM. For this to work correctly, the DRM administrator needs to use

the same Oracle Fusion user name on the DRM system.

Hyperion DRM must be authenticating users with the same user directory used by

Fusion. To do this, the authentication mode should be set to CSS (External), central shared services, and an instance of Hyperion Shared Services needs to be

configured in the DRM Console to point to the user directory.

This restriction does not apply to E-Business Suite, where the DRM username and

the EBS username may be different. Since you have to separately configure the

username/password for the DRM user, you could use Internal authentication for the EBS user if you desire. The configuration of the username/password for EBS

will be covered in detail later in this white paper.

Assign the Data Creator and Data Manager roles to the user to be able to

successfully export chart of accounts values and hierarchies to the E-Business Suite

and Oracle Fusion.

To run the DRM exports for EBS and Fusion, the user must have the Application

Administrator role and at least read access to the Oracle General Ledger property category.

2. Using the Hyperion DRM Migration Utility, Load Metadata functionality, upload the application template. For convenience, Oracle has placed the

application template in two different locations (one for EBS, one for Oracle

Fusion). This is the same file in two locations. It only needs to be uploaded once.

The template file is an FND file that is located either at:

Instance Location

EBS $GL_TOP/java/drm/OracleGL_DRM_AppTemplate.xml

Oracle

Fusion

[FUSIONAPPS]$APPL_TOP/fin/gl/drm/OracleGL_DRM_AppTemplate.xml


Your database administrator should locate and download this file to a directory

accessible to the DRM user completing the import.

This template provides the options that are completed by business users to integrate

DRM information with the E-Business Suite and Oracle Fusion General Ledgers.

For example, it will load DRM properties that can be used to indicate whether a

hierarchy is for accounts, or the account type, or posting eligible for posting for a

particular node.

3. Update the external connections to the E-Business Suite and Oracle Fusion General Ledger instances. Navigate: Administer New External Connection

Two default connections are available with the application template, one for EBS

and one for Oracle Fusion. Use these connections when there is a single EBS

and/or single Oracle Fusion instance.

This is a task for a database administrator or systems administrator, specifically the

DRM Application Administrator role. You must update the external connections with the Connection String, User ID, and Password for each Oracle Fusion and E-

Business Suite instance that you would are integrate with DRM.

Figure 3. Update External Connection for EBS

Figure 4. Update External Connection for Fusion

The remaining fields should be completed as follows:


Field Value

Name This field is already completed.

EBSDBConnection for EBS

FusionDBConnection for Fusion

Description Description of your EBS or Oracle Fusion

instance.

Object Access System

Connection Type Database Table

Data Access Provider Oracle

Connection String Include the database host, port, and SID

(System Identifier)

User ID This must be the name of a database user

who has access to the appropriate tables

in EBS or Oracle Fusion:

GL_DRM_SEGVALUES_INTERFACE

and

GL_DRM_HIERARCHY_INTERFACE

Password This is the password for the user selected

under USER ID. It set by your Oracle Fusion or EBS database administrator.

For Oracle Fusion, its the password

to the Oracle Fusion runtime schema,

such as FUSION_RUNTIME

For the E-Business Suite, its the

password to the apps schema.

Once you enter the password, click the refresh button and DRM will connect to the

Oracle Fusion or EBS instance and will display all the tables that the user can

access. From the list of tables, select the tables:

o GL_DRM_SEGVALUES_INTERFACE

o GL_DRM_HIERARCHY_INTERFACE


4. Update the default for the hierarchy node type to Node Type. Navigate: Administer Property Definitions Core HierarchyNodeType

Figure 5. Update Hierarchy Node Property

The default node type controls behavior of the Oracle General Ledger properties in

DRM based upon whether a hierarchy is for an account segment. For example, it

determines that properties such as Third Party Control Account are relevant only if a segment is for an account.

Typically, the value OracleGL.NodeType is appropriate for DRM. However, this step should be completed only if there is not a conflicting (and more frequent) use for

the default node type. For example, if DRM is used for other purposes, such as to

maintain location or organizational hierarchies, and there is a need to alter behavior

based upon classifications of such hierarchies, you may not want to make the default

specific to General Ledger integration. In such cases, you will need to update the

hierarchy node type to Node Type for each new version for charts of accounts that you create.

Initial Load of Values from EBS

This section contains the details required to initialize the EBS segment values and

hierarchies in DRM. EBS provides an initialization program that is run from the

general ledger, which will take the current segment values and associated hierarchies

for a value set and import them to DRM.

This step is only required if you would like to start using DRM with EBS value set

values and hierarchies (parent-child relationships).


This program will import the current EBS configuration, without any editing, to DRM.

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.

Once DRM becomes the source of truth for all hierarchies, existing parent-child

relationships in EBS will be overridden by the Load Segment Values and Hierarchies

concurrent program.

Additional data cleansing can be completed in DRM.

Hyperion DRM Configuration Prerequisite

You must have a DRM user with access to the Application Administrator role to run the import from DRM. You can reuse the same user from your initial DRM

configuration provided you add this role. In contrast, exporting from DRM to EBS

and/or Oracle Fusion does not require the Application Administrator role.


Initialization Steps

1. Using EBS, run the initialization program. This is completed from a general ledger responsibility. Navigate: Other Requests Run

This program creates a file that will be used to complete the DRM import. Data

access sets are used to determine which value sets a user may initialize. Each

value set must be separately initialized to DRM.

Figure 6 Initialization Program in EBS

Once the program completes, an output file is generated. Open and save this file

to your client (e.g. PC). It should default to .txt format. This output file will be used for the import into DRM.


2. Using DRM, import the EBS file into DRM. Navigate: Home Import Select EBSValueSetExport

Figure7 Import to DRM

Select the file that you saved from the EBS. In this example, the file is

Initialize_Segment_Values_and_310311.txt.

Select the execute button. This will submit the import request.

The import request will complete several actions:

Creates a DRM Version. The version name will be the same as the value set name.

Creates a node for each value in the value set, including segment properties such as:

o Allow Budgeting o Allow Posting o Reconcile o Third Party Control Account

Creates a separate hierarchy for each to top node (hierarchy) in EBS. The name of each hierarchy will correspond to the description of the parent

value of the top node from the parent-child relationship.

Checks for invalid characters (not permitted by DRM). If you are using characters not permitted by DRM, fix the value set information in EBS and

then resubmit the import.

Figure 2


If there are exceptions, they will appear on the import user interface (lower pane).

They should be examined and resolved. If you need to make updates in EBS, delete

the version and then resubmit the import after they are complete.

The figures below provide an example of an EBS parent-child relationship,

Application Sales Rollup, and the corresponding hierarchy that is created in DRM via the initialization process.

Figure 8 EBS Parent-Child Relationship Example

Figure 9 Corresponding DRM hierarchy (post initialization)

3. Enable validations for the nodes in the version. DRM provides the ability to determine which validations should be enforced for the nodes in a given version.


Enable the validations to ensure that nodes are in accordance with the value set

configuration. Select the values according to the figure below.

Validation Suggested Value

Account Type Required Batch

Max Description Length Both

Natural Account Required Fields If the version represents a natural

account: Batch

Otherwise: None

Required Fields If the version represents a natural

account: None

Otherwise: Both

Start Date Before End Date Both

Value Name Maximum Length Based upon the definition of the related

value set.

Value Name Uppercase Based upon the definition of the related

value set.

4. Review the version and update the Oracle General Ledger properties. Navigate: Home Browse Select the Version.

The imported version is now ready for review. Once you have determined that it

accurate. You must update the Oracle General Ledger property to True to indicate that it is available for export to EBS and/or Oracle Fusion on a regular

basis. You must also update the status from Working to Saved by right clicking the version and selecting Save.

Orphan Nodes

DRM categorizes any node that does not belong to at least one hierarchy in the version

as an orphan. Orphan nodes may not be updated in DRM.

Consider updating your EBS-Parent child relationships prior to submitting the

initialization program to ensure that all segment values belong to a parent-child

relationship (which is synonymous with hierarchy in DRM). Otherwise, you will have

to assign orphan nodes to hierarchies in DRM to make them eligible for update.

To avoid creating one node hierarchies, parent segment values that do not have any

associated children will be categorized in DRM as orphans when they are initialized

from EBS.


Initialization with Multiple EBS Instances

You may have multiple EBS instances, each with their own value sets, which should

be stored and updated as a single Hyperion DRM version and hierarchy. Only one of

the value sets can be initialized per DRM version. This DRM Version will serve as the

source of truth, regardless of how many value sets will ultimately map to this version, and should be used as a starting point for data cleansing.

For example, ACME Corporation has two EBS instances, ACME North America, and

ACME Mexico. Each of these instances has a value set for accounts. These value sets

are intended to represent a corporate-wide list of accounts. However, over time, the

ACME Mexico instance hasnt been accurately updated. Consequently, there are disparities between the two value sets.

Moving forward, ACME would like a single, consolidated corporate account structure

across all of its instances. To do this, a single DRM version must be used. This single

DRM version can be exported to both ACME North America and ACME Mexico.

ACME should initialize DRM using the value set from the North America instance,

since it is more accurate. Once this is complete, ACME should use DRM to complete

any required updates, including changes to reflect accounts from ACME Mexico that

should also be in the corporate-wide account list.

The results are later exported to both ACME North America, and ACME Mexico;

ensuring that both instances are accurate.

Optional Administrative DRM Configurations

The default configuration assumes a single EBS plus a single Oracle Fusion instance.

The following configuration steps are only required under certain conditions, such as if

you have multiple EBS and/or multiple Oracle Fusion instances.

There must be at least one version and hierarchy in DRM before these optional steps

can be completed. This can be accomplished with the initialization of EBS (which will

automatically create DRM versions and hierarchies) or by manually creating a new

DRM version and hierarchy.

1. Create new connections. Navigate: Home New (from the menu pull down list) External Connections

You must create a new connection for each additional Oracle Fusion and E-Business

Suite instance that you would are integrate with DRM. See the step entitled Update


the external connections to the E-Business Suite and Oracle Fusion General Ledger

instances, for a description of how to complete these fields.

Figure 10 Create a new connection

2. Create/copy exports. Navigate: Export [Select appropriate export] Export (from toolbar pull down list] Select the Copy option.

Create copies of both the hierarchy and value sets exports. Create one copy of each,

for each additional instance.

For example, if you have three E-Business Suite instances, you will have a total of six

E-Business Suite exports (three value set exports, and three hierarchy exports).

However, because one value set and one hierarchy export are provided by Oracle, you

only need to create two new value set exports and two new hierarchy exports.

You can use the same values for all of the fields from the seeded exports except for the

name (which must be unique), and the connection string, which must be specific to the

EBS or Oracle Fusion instance that is to receive the exported values.

To update the connection string, select the level two tab entitled Target. From this screen, update the connection string to the appropriate instance, as defined in the

external connections configuration step.

3. Create custom properties for value sets. Navigation: Administer New (from toolbar) Property Definition

This step is only required if you are integrating to multiple E-Business Suite or

multiple Oracle Fusion General Ledgers, and these general ledgers use different value

set names to represent the respective chart of accounts segments.


Example: ACME Corporation has two E-Business Suite instances, North America and United Kingdom. ACME wants to use standardized chart of accounts values for the account segment of its charts of accounts.

The value set name for the account segment in the North America instance is ACME Accounts. The value set name for the account segment in the United Kingdom is Account Segment.

Because the names of the value sets are different, store an alternate value set name

with each DRM version that is to be exported to both North America and the United

Kingdom. This links both value sets to the same DRM hierarchy so that the values

may be exported to both general ledgers correctly.

For each alternate value set name that must be used, an additional property must be

created in DRM to store the alternate name. Later, the alternate value set name(s) must

be stored with the appropriate versions.


Figure 11 Create a new connection

The fields should be completed as follows:

Property Value

Name Name of the field.

Label Name of the field that you would like to

appear when users enter a value for the

value set as they create DRM versions.

For the ACME Corporation example, a

reasonable value would be United Kingdom Value Set or North America Set so that users understand what value should be entered.

Description Description of the field. For example,

Property to hold North America value sets.

Data Type String

Property Type Defined

Default Value Leave blank

Minimum Length Optional. You can put in a minimum

length based upon

Property Level Version

Column Width 20

Maximum Length Leave blank.


4. Create custom properties for version and hierarchy exports. Navigation: Administer New (from toolbar) Property Definition

Oracle provides a property to indicate whether a particular version or hierarchy in

DRM should be exported to the EBS and Oracle Fusion General Ledgers. This

step is used only in cases where customers have divergent master data

management requirements by instance.

Customers may decide that they would like to export certain versions and/or

hierarchies only to specific EBS or Oracle Fusion instances. This step is for such

cases. Create a custom property that is used to determine whether a particular

version or hierarchy should be exported to a specific instance.

Example (Version): ACME Corporation has a version for a hierarchy that is used

only in Oracle Fusion for pro forma financial analysis. This version should only be

exported to Oracle Fusion. In this case, an additional property should be created to

indicate that an EBS instance should not import this hierarchy.

Example (Hierarchy): ACME Corporation uses DRM to maintain its cost center

values for its corporate, Oracle Fusion General Ledger. However, the E-Business

Suite general ledger for the United Kingdom does not share these or use these cost

centers. For such a case, create a custom property, such as UK Value Sets, for United Kingdom Hierarchy Export, to indicate that an Oracle Fusion based cost

center hierarchy should not be exported to the United Kingdom general ledger.

These custom properties are integrated with the Oracle Fusion and EBS General

Ledgers through the use of profile options, GL: DRM Property to Allow Version

Export and GL: DRM Property to Allow Hierarchy Export. Configuration of these

profile options is covered later in this white paper.


EBS and Oracle Fusion Administrative Configurations

This section describes integration configurations for the EBS and Oracle Fusion

General Ledgers. Unless specifically noted, the configuration steps should be

completed in each Oracle Fusion and EBS instance that is integrated to DRM.

In general, Oracle provides default values for profile options that may not require

update unless otherwise noted.

This section assumes that you have already created the value sets necessary to hold

the segment values loaded from DRM.

1. Update the profile option: GL: DRM Username (EBS only). This profile option should have the username for the DRM user created during the configuration that

has access to the DRM data creator / manager role.

2. For E-Business Suite (only), run the script that populates the DRM password in E-Business Suite. This DRM password must be stored in the E-Business Suite

database to enable access to DRM when loading values and hierarchies.

This script is stored in FND_VAULT. The script is run as:

sqlplus apps/@db @$FND_TOP/sql/afvltput.sql SQLGL

Parameter Value

The password to the apps schema

The name of the DRM user stored in the

profile option: GL: DRM Username

The DRM password for the user identified

in the profile option: GL: DRM Username

Note: the following profile options are all at the site-level.

3. Register DRM Adapter URL. This only applies if you are using a release earlier than Fusion Release 3 (11.3.0.0). Otherwise, skip directly complete the topology

configuration as described in the next step.

Update the profile option: GL: DRM API Adapter URL.


This is the URL of the DRM API Adapter. This points to the DRM Adapter URL

(e.g. http://adcdae09.us.oracle.com:5243/Oracle/Drm/APIAdapter) It is passed as

one of the parameters to the DRM Web Service. This is a task for a system

administrator.

4. Complete Topology Manager configuration. This applies only if you are using Fusion Release 3 (11.3.0.0) or a later release. Otherwise, proceed to the next step.

1) Click on the option 'Register Applications' under the Topology Registration Task list on the left side of the Setup and Maintenance page.

2) Add a new application by clicking on the green plus sign.

3) Enter/select the following values:

Enterprise Environment: oracle

Enterprise Application: GlDrmApp (select it from the dropdown list)

Name: GlDrmApp (manually enter this name)

Server Protocol : http

External Server Host: enter the host that is in the value of the profile

option GL_DRM_API_ADAPTER_URL.

External Server Port: enter the port that is in the value of the profile

option GL_DRM_API_ADAPTER_URL.

5. Update the Profile Option: GL: DRM WSDL URL (EBS only)

The DRM WSDL is used by the EBS Services Invocation Framework (SIF) to access

the DRM web service. SIF validates the SOAP requests against this WSDL and also

derives the endpoint URL (the web service URL).

Optional Steps

These steps are only completed if you have multiple EBS instances or multiple Oracle

Fusion instances, AND you need to alter the behavior of the DRM synchronization by

instance. For example, there are value sets that should only be synchronized to certain

instances.

In this case, you may need to vary the values for these profile options by instance.

1. Update the profile options that tell DRM whether to export a value set or hierarchy to the EBS or Oracle Fusion instance. This allows you to selectively export

versions and hierarchies to specific instances.

GL: DRM Property to Allow Version Export


This is the name of the version-level property in DRM which indicates whether to

export values (in DRM terminology, nodes) to an instance.

GL: DRM Property to Allow Hierarchy Export

This is the name of the hierarchy-level property in DRM which indicates whether

to export hierarchy relationships to an instance.

2. Update the profile options that hold the value set name. This allows you to link multiple value sets which use different names, to the same DRM version.

GL: DRM Property for Value Set Name

This profile option stores the name of the version-level property in DRM that

specifies the value set name for an instance. As discussed earlier in this white

paper, you must create additional properties in DRM to hold the alternate value set

names. Here, you are specifying the name of the property that you created to hold

the value set name used by this particular instance.

This step is required only if the customer needs to store alternate names for value

sets with DRM versions.

The value should be the same name as the property name that was created in DRM

to hold the value of the alternate value set for the instance which is being updated.

Example: ACME Corporation created a DRM property entitled, UK Value Sets to link its United Kingdom general ledger value sets to DRM versions. In this

case, the profile option value should be UK Value Sets.

3. Update the profile options that specify which DRM export to use.

These profile options are: GL: DRM Template for Version Export and GL: DRM Template for Hierarchy Export

If you are exporting to multiple EBS general ledgers, then you should have copied

the exports provided by Oracle (the process for this is described in the Hyperion

DRM configuration section of this white paper). Use the names for the respective

exports that you created for the value set and hierarchy exports.

Example: ACME Corporation has two EBS instances, North America, and the

United Kingdom; it wants to integrate with DRM.


It can use the default exports provided by Oracle for one of the instances, such as

the North America instance. For this instance, it will leave the default values for

the profile options GL: DRM Template, and GL: DRM Template for Hierarchy

Export.

ACME must both create and name new exports in DRM for the United Kingdom

instance, since exports are connected to specific databases. It must then update the

values for the profile options GL: DRM Template for Version Export, and GL:

DRM Template for Hierarchy Export to use the names of the exports it created.


Business User Configurations

This section contains the configurations that a business user would complete to

integrate Hyperion DRM with the Oracle Fusion General Ledger. Before creating

DRM versions and hierarchies, the chart of accounts structures and associated value

sets should be created in both Oracle Fusion and EBS.

Business users can complete maintenance of DRM versions and hierarchies and export

the results to the Oracle Fusion and EBS General Ledgers.

1. Create a separate DRM version for each value set. Navigation: Select New from the Versions menu.

Current EBS GL customers may bypass this step by running the initialization

program for all of their value sets that are to be maintained in DRM.

The same version can be used to export results to multiple Oracle Fusion and EBS

instances. This is a primary advantage of DRM: define all the valid values (as

nodes) in a single version and export it to multiple instances that use the same

values in their chart of accounts.

For Oracle Fusion, multiple hierarchies, from different versions may be exported

for planning / financial reporting requirements. For EBS, only one DRM version

may be exported per value set.

EBS customers can choose to version DRM as often as is needed for their business

requirements. Since EBS does not create versions (like Oracle Fusion), the

existing EBS account hierarchies will be overwritten. The versions are maintained

only in DRM.

If a Version is deleted in DRM, it will not delete the related Oracle Fusion trees

since those trees may be used in general ledger processes such as allocations.

2. Using DRM, set Oracle General Ledger Properties for each version. Navigation: From Version Right click Select Properties Select Oracle General Ledger from choice list.


Figure 12 Oracle General Ledger Properties

Property Value

Allow Export Set this value to Yes to enable export of the version to Oracle Fusion and/or EBS.

This would likely be set to No if the version is no longer used (i.e. a new

version has been created to reflect

changes in hierarchies), the version is not

ready for export, or if DRM is used for

non-Oracle general ledger purposes and

the version is for non-general ledger use.

Tree Version Name Name of the Oracle Fusion tree that

should receive the hierarchy values.

Each DRM version is equivalent to an

Oracle Fusion tree version name.

This option does not apply to EBS.

Effective Start Date Effective start date for the version.

Make sure that the date range (between


the effective start date and the effective

end date) does not overlap with other

versions that reference the same Oracle

Fusion tree. Otherwise, an exception will

be created when integrating with the

Oracle Fusion General Ledger.

Effective End Date Effective end date for the version.

Make sure that the date range (between

the effective start date and the effective

end date) does not overlap with other

versions that reference the same Oracle

Fusion tree. Otherwise, an exception will

be created when integrating with the

Fusion general ledger.

Value Set The value set code that will receive the

exported results. This is case sensitive.

If value sets have different codes in the

various general ledgers, create additional

DRM properties to store the alternate

value set names, and update the GL:

DRM Property for Value Set Name to

point to the custom property.

Value Set Master Set the Value Set Master option to Yes for the version which is to be exported to both EBS and Oracle Fusion.

All of the nodes in this version will be

exported to EBS and Oracle Fusion. The

values for the nodes, including node

descriptions, in this version are the source

of truth for value sets, regardless of their

values and configurations in alternate

DRM versions.

If the value set master option is set to

No then no new values will be added to EBS. Values will still be added to Oracle

Fusion.

If you chose to create new versions (for

example, to reflect chart of accounts

hierarchies at the beginning of a new


accounting period or year), you can

update the value set master option to

No for the old version and set it to Yes for the new version.

You may create non-value set master

versions for integrating hierarchies to

Oracle Fusion for what-if analysis and/or

planning.

Natural Account Set this value to True for versions that are used to hold natural account values.

Otherwise, it should be set to False.

Segment Value Max Length This determines the total permissible for

segment values. Enter a value consistent

with the value set configuration in EBS

and/or Fusion.

3. Create hierarchies for the version. Navigation: Version (Select appropriate version) Hierarchies (lower region) Create Icon

DRM hierarchies can be used to maintain both Oracle Fusion trees, and EBS

hierarchies. All nodes must be managed in DRM in hierarchies. This means that

you will need at least one hierarchy per DRM version to manage segment values

for that version. Best practice is to provide this with a primary hierarchy structure.

However, that hierarchy could be as simple as a flat list of segment values.

Because the Oracle Fusion General Ledger contains hierarchy enhancements

known as trees, it is possible to export multiple versions for the same value set for

Oracle Fusion. In contrast, the EBS General Ledger may only have a single

version imported from DRM.

4. Update the system property Hierarchy Node Type to Node Type.

This step is only required if the default value for Hierarchy Node Type is not set

and the hierarchy is not imported from EBS.


In EBS, the top node of parent-child relationships is used to create a hierarchy. In

the following example, there are multiple parent-child relationships for the value

set Operations Department, each with its own parent-child relationships.

Figure 13 Multiple hierarchies

Each DRM Hierarchy name is equivalent to an Oracle Fusion tree name. If you

chose to have multiple hierarchies associated with the same version, each hierarchy

must contain all of the same descendants. Otherwise, create separate versions for

the different hierarchies.

For the purposes of exporting EBS hierarchies, it should be noted that DRM does

not support ranges. Therefore, when DRM hierarchies are exported to EBS,

existing ranges will be replaced by individual values. The enforcement of the

hierarchies, however, remains the same.

Each time a hierarchy is loaded from DRM, the EBS hierarchy relationships are

replaced with the current DRM hierarchy relationships.

In contrast, if you delete a node in DRM, it will remain in EBS and Oracle Fusion.

4. Complete hierarchy properties. Navigation: Hierarchy (Select appropriate hierarchy) Category (Oracle General Ledger) from choice list


Figure 14 Hierarchy properties

Property Value

Allow Hierarchy Export Set

Tree Name This is the name of the Oracle Fusion tree

corresponding to the tree version

specified in the version Oracle General

Ledger properties.


Ongoing Business Processes

This section contains the ongoing processes that business users complete to integrate

Hyperion DRM with the Oracle Fusion General Ledger. Charts of accounts

maintenance is completed via DRM.

DRM is used for maintenance, and the results are exported back to EBS and/or Oracle

Fusion. Manual updates to charts of accounts and hierarchies should no longer be

completed in EBS.

Business users submit the export process to synchronize EBS and Oracle Fusion with

DRM master data. Accordingly, run the export processes (SRS and ESS requests) at

regular intervals, based upon how often DRM is updated. The requests should be run

at least prior to financial reporting to modify any financial report charts of accounts /

hierarchies values as needed.

At regular intervals, synchronize DRM and EBS / Oracle Fusion using EBS SRS and

Oracle Fusion ESS requests.

Steps:

1. Using DRM, set Oracle General Ledger Properties for each node in the hierarchy. Navigation: Version (Select appropriate version) Hierarchies (Select appropriate hierarchy) Open Hierarchy Create node (New from toolbar, or right click from an existing node and select New)

For each node that is integrated to Oracle Fusion and/or EBS, there are a set of

Oracle General Ledger properties which should be completed. The default values

are provided below.

Figure 15 Node properties


2. EBS: Run the Load Segment Values and Hierarchies request. Oracle Fusion: Run the Load Accounts and Hierarchies ESS request.

This must be completed for each EBS and Oracle Fusion instance that you are

integrating with Hyperion DRM. The request is run for each value set with

associated values and hierarchies. Request sets can be created to run the request

for multiple value sets.

Data access set security is used to determine which value sets a user can

synchronize from DRM to EBS and/or Oracle Fusion.

The Load Segment Values and Hierarchies request will only create or update

segment values and account hierarchies for the chart of accounts accessible via the

users general ledger data access setting.

The Load Segment Values and Hierarchies request will complete successfully only

if it can find exactly one value set marked as Master, in the Oracle General Ledger version properties of DRM. Otherwise, it will create an error report,

prompting for an update of the value set master option.

The Load Segment Values and Hierarchies will enforce segment validations in the

EBS and Oracle Fusion General Ledgers such as:

The segment value length cannot exceed the maximum as defined for the value set.

The segment value must be not include special characters ~!@#$%^&*()+=|\}]{["?/>.


There is an EBS report which will indicate whether the export is successful and

provide summary information about the information imported from DRM.

Figure 16 Load Segment Values and Hierarchies Report

2. Review the results in the Oracle Fusion and/or EBS General Ledger. The picture below shows how the hierarchy from DRM has been exported as an account

hierarchy in the EBS General Ledger.

Figure 17 Load Segment Values and Hierarchies Report

You can query the results in Oracle Fusion using the Appl Core user interface. You can view the results in the EBS GL by querying the value set values.


Integration of Translated Values

This section contains instructions to configure DRM for holding translated description

values for value set values. If you are not using multiple languages for one or more

value sets, this step is not required.

For example, ACME Corporation may have a Mexican subsidiary, with its own EBS

instance, that uses the corporate ACME Accounts value set. This value set is also used by the ACME Corporation, USA Instance. Since the value set is shared, account

descriptions must be maintained both in English and Spanish.

When the values for ACME Accounts are exported from DRM to the ACME Mexico EBS instance, the account descriptions should be in Spanish. To do this, the

alternate language (Spanish) account descriptions are maintained in DRM and exported

to the Mexico instance.

Steps for configuration of alternate language descriptions:

1. For each additional language that you would like to use update the property that holds the alternate language description by deselecting the Hidden option. Navigation: Administer Property Definitions OracleGL Select property that holds the appropriate language

2. Once the property is visible, you may enter values in the alternate language when creating or editing nodes.

The export program(s) will populate the alternate language nodes in the appropriate

language. Based upon the installed language and configuration of the EBS and/or

Fusion instance, the alternate language will be displayed for any node that has an

entered description in that language for the appropriate property.

Example: ACME Corporation deselects the Hidden option for the LA (Latin American) Spanish Description property. When nodes are created or edited, the

user can enter a description in English in the Description property, and a description in Spanish in the Description: LA Spanish property.

The load segment values and hierarchies program will populate both the English

and Spanish language descriptions. If the instance has Spanish installed and it is

the language used, then the descriptions will appear in Spanish.


About Oracle Fusion Applications

Oracle Fusion Applications leverage industry standards and technologies to transform organizations

into next-generation enterprises. Oracle Fusion Applications are service-enabled, enterprise

applications that can be easily integrated into a service-oriented architecture and made available as

software as a service.

For more information about Oracles Fusion Accounting Hub, please contact us today at 800-273-

9913. To learn more about Oracle Fusion applications, please visit oracle.com/fusion

Hyperion Data Manaagement Integration with

Oracle Fusion and E-Business Suite General

Ledgers

Author: Matthew Skurdahl

Oracle Corporation

World Headquarters

500 Oracle Parkway

Redwood Shores, CA 94065

U.S.A.

Worldwide Inquiries:

Phone: +1.650.506.7000

Fax: +1.650.506.7200

oracle.com

Copyright 2011, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only and the

contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other

warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or

fitness for a particular purpose. We specifically disclaim any liability with respect to this document and no contractual obligations are

formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any

means, electronic or mechanical, for any purpose, without our prior written permission.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license

and are trademarks or registered trademarks of SPARC International, Inc. UNIX is a registered trademark licensed through X/Open

Company, Ltd. 1010

drm white paper

Documents