TABLE OF CONTENTS

Oracle Data Relationship Management - Oracle General Ledger Integration Guide
Documentation Accessibility

Documentation Feedback

Copyright Page

Using Data Relationship Management with Oracle General Ledger

Configuring Data Relationship Management for Oracle General Ledger

- Locating the Application Template

- Loading the Application Template

- Creating Properties for Multiple General Ledger Instances

- Exporting Segment Values and Hierarchies from Data Relationship Management

- Exporting Data

- Export Profiles

- Copying Exports for Multiple General Ledger Instances

- Connecting to Oracle General Ledger Instances

- System Preferences

- Deploying the Data Relationship Management Web Service

- Setting up Data Relationship Management Users

Initializing Data Relationship Management with Oracle General Ledger Data

- Import Profiles

- Importing Data

- Assigning Validations

- Enabling Node Types

Managing Segment Values and Hierarchies for Oracle General Ledger

- Managing Oracle General Ledger Value Sets

- Managing Chart of Accounts Segment Values

- Managing Hierarchies of Segment Values

- Validating Segment Values and Hierarchies

- Loading Segment Values and Hierarchies into Oracle General Ledger

Documentation Accessibility

For information about Oracles commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc .

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Documentation Feedback

Send feedback on this documentation to: epmdoc_ww@oracle.com

Follow EPM Information Development on these social media sites:

LinkedIn - http://www.linkedin.com/groups?gid=3127051&goback=.gmp_3127051

Twitter - http://twitter.com/hyperionepminfo

Facebook - http://www.facebook.com/pages/Hyperion-EPM-Info/102682103112642

Google+ - https://plus.google.com/106915048672979407731/#106915048672979407731/posts

YouTube - http://www.youtube.com/user/OracleEPMWebcasts

Oracle® Data Relationship Management

Release 11.1.2.4

Oracle General Ledger Integration Guide

Copyright © 2013, 2015, Oracle and/or its affiliates. All rights reserved.

Updated: August 2015

Authors: EPM Information Development Team

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS:

Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

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

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. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Using Data Relationship Management with Oracle General Ledger

You can use Oracle Data Relationship Management to manage charts of accounts segment values and hierarchies for independent value sets by the Accounting Flexfield in Oracle General Ledger. Users create new segment values, edit their properties, and maintain hierarchies using the Data Relationship Management web client. This information can be synchronized to general ledger instances using a concurrent request program in Oracle General Ledger.

This integration between Data Relationship Management and Oracle General Ledger is available for:

- Oracle E-Business Suite Release 12.1 and 12.2.x

- Oracle Fusion Accounting Hub Release 11g

For more information about Oracle General Ledger concepts, see the Oracle General Ledger Implementation Guide and the Oracle Applications Flexfields Guide.

For more information about Oracle Fusion Accounting Hub concepts, see the Oracle Fusion Accounting Hub Implementation Guide, the Oracle Fusion Applications Financials Implementation Guide, and the Oracle Fusion Applications Common Implementation Guide.

Configuring Data Relationship Management for Oracle General Ledger

In This Section:

Locating the Application Template

Loading the Application Template

Creating Properties for Multiple General Ledger Instances

Exporting Segment Values and Hierarchies from Data Relationship Management

Setting up Data Relationship Management Users

An application template is used to configure a Data Relationship Management application for Oracle General Ledger. The application template contains predefined Data Relationship Management metadata such as properties, categories, validations, node types, and exports. You use the Data Relationship Management Migration Utility to load the application template. After the template is loaded, you can modify the metadata from the template to support custom requirements of the organization.

Note:

You must be an application administrator to configure Data Relationship Management for Oracle General Ledger.

Locating the Application Template

An Oracle General Ledger application template is installed as part of the Oracle General Ledger installation. You use the application template to configure the Data Relationship Management metadata to enable integration with Oracle General Ledger.

To confirm that the application template is installed correctly on an E-Business Suite instance:

1. On the computer where Oracle General Ledger is installed, navigate to the $JAVA_TOP/oracle/apps/gl/drm directory on the E-Business Suite instance.

2. A file named OracleGL_DRM_AppTemplate.xml should be in this directory. This file is the application template.

To confirm that the application template is installed correctly on an Oracle Fusion Accounting Hub instance:

1. On the computer where Oracle Fusion Accounting Hub is installed, navigate to either the $APPL_TOP/fin/gl/drm directory on the Oracle Fusion Accounting Hub instance.

2. A file named OracleGL_DRM_AppTemplate.xml should be in this directory. This file is the application template.

Loading the Application Template

You use the Data Relationship Management Migration Utility to load the application template. See the Oracle Hyperion Data Relationship Management Administrators Guide topic " Loading Metadata " for details on how to use the Migration Utility to load the application template.

After you load the application template, you can complete the configuration of the Data Relationship Management application for Oracle General Ledger. Property definitions and validations that are created during the load of the Oracle General Ledger application template are assigned to the OracleGL namespace. This namespace is reserved for Oracle General Ledger. These objects can be modified or deleted from the application by an administrator, but new custom objects cannot be assigned to the namespace.

Note:

Oracle E-Business Suite and Oracle Fusion Accounting Hub use the same OracleGL application template. If your Data Relationship Management application is supporting both Oracle E-Business Suite and Oracle Fusion Accounting Hub in a co-existence scenario, the OracleGL template only needs to be loaded from one source.

Creating Properties for Multiple General Ledger Instances

Data Relationship Management properties are used to control which segment value sets and hierarchies are exported to an Oracle General Ledger instance.

The following properties are included with the Oracle General Ledger application template:

- Allow Export—Version-level flag to enable a version to be exported

- Allow Hierarchy Export—Hierarchy-level flag to enable a hierarchy to be exported

To export different value sets or hierarchies to different general ledger instances, you create custom properties in Data Relationship Management for each instance.

Exporting Segment Values and Hierarchies from Data Relationship Management

After you load the application template, you can export segment values and hierarchies from Data Relationship Management.

Exporting Data

When you run the integration program, the Data Relationship Management data is exported to the Oracle General Ledger interface tables. From these tables, the data is loaded into Oracle General Ledger.

Export Profiles

The application template includes export profiles to enable export of segment values and hierarchies from Data Relationship Management to Oracle General Ledger. The integration program calls these exports using the Data Relationship Management Web Service.

The following exports are included in the application template:

- EBSValueSetExport (Version Export)—Outputs a global list of E-Business Suite segment values from a Data Relationship Management version

- EBSHierarchyExport (Hierarchy Export)—Outputs the nodes and relationships for E-Business Suite hierarchies from a Data Relationship Management version

- FusionValueSetExport (Version Export)—Outputs a global list of Fusion Accounting Hub segment values from a Data Relationship Management version

- FusionHierarchyExport (Hierarchy Export)—Outputs the nodes and relationships for Fusion Accounting Hub hierarchies from a Data Relationship Management version

Copying Exports for Multiple General Ledger Instances

If you are integrating Data Relationship Management to more than one Oracle General Ledger instance, you must create copies of the exports for each instance. See " Running, Copying, and Deleting Exports " in the Oracle Hyperion Data Relationship Management Users Guide.

Connecting to Oracle General Ledger Instances

After loading and configuring the application template, use Data Relationship Management to create external connections to the Oracle General Ledger instances with which you are integrating. If you copied Data Relationship Management exports to synchronize charts of accounts to multiple general ledger instances, you must create and configure separate connections for each instance. See " Defining External Connections " in the " Working with External Connections " chapter of the Oracle Hyperion Data Relationship Management Administrators Guide.

Connecting to E-Business Suite Instances

When connecting to E-Business Suite instances, the connection must point to the database for the E-Business Suite instance and must log in using the APPS schema. The staging tables are under the GL schema, with synonyms in the APPS schema. The staging table names are GL_DRM_SEGVALUES_INTERFACE and GL_DRM_HIERARCHY_INTERFACE.

Connecting to Oracle Fusion Accounting Hub Instances

When connecting to Oracle Fusion Accounting Hub instances, the connection must point to the database for the Oracle Fusion Accounting Hub instance and must log in using the FUSION_RUNTIME schema. The staging tables are under the FUSION schema, with synonyms in the FUSION_RUNTIME schema. The staging table names are GL_DRM_SEGVALUES_INTERFACE and GL_DRM_HIERARCHY_INTERFACE.

System Preferences

The following Data Relationship Management system preferences are used to ensure the integrity of values exported to Oracle General Ledger. These system preferences should be modified only to accommodate newly created data that must be modified before being exported.

- AuthMethod—Set to CSS or Mixed to enable integration using the Data Relationship Management web service

- InvDescr—Restricts the use of single and double quote characters in node descriptions

- InvName—A list of invalid characters will be set to restrict their use in names of nodes

- LeafEdit—Set to Data Creator and Data Manager to limit the edit ability of the Leaf property

- RenameLeaf—Set to blank to prohibit leaf nodes from being renamed

- RenameLimb—Set to blank to prohibit limb nodes from being renamed

See the chapter entitled " Working with System Preferences " in the Oracle Hyperion Data Relationship Management Administrators Guide for information on how to set system preferences.

Deploying the Data Relationship Management Web Service

The Data Relationship Management Web Service is used to synchronize segment values and hierarchies to Oracle General Ledger. See the " Deploying and Configuring the Data Relationship Management Web Service API " chapter of the Oracle Hyperion Data Relationship Management Installation Guide for instructions and considerations for enabling the web service for use with this integration.

Setting up Data Relationship Management Users

Data Relationship Management users must be created separately for use with Oracle General Ledger. E-Business Suite and Fusion Accounting Hub require different user configurations in Data Relationship Management.

Perform the following setup tasks for integration with E-Business Suite General Ledger:

- Assign the Data Creator or Data Manager roles to users who need to create value sets or hierarchies.

- Create a separate Data Relationship Management user for use by the Oracle General Ledger integration program.

- Set the Authentication option to CSS (External) for the users that will run the Oracle General Ledger integration program. Oracle Hyperion Shared Services must be used to authenticate users in an external user directory.

Perform the following setup tasks for integration with Fusion Accounting Hub:

- Assign the Data Creator or Data Manager roles to users who need to create value sets or hierarchies.

- Assign the Application Administrator roles to users that will run the Oracle General Ledger integration program.

- Set the Authentication option to CSS (External) for the user that will run the Oracle General Ledger integration program. Oracle Hyperion Shared Services must be used to authenticate users in an external user directory.

For more information, see the topic entitled " Creating Users "in the " Managing Users " chapter of the Oracle Hyperion Data Relationship Management Administrators Guide.

Initializing Data Relationship Management with Oracle General Ledger Data

In This Section:

Import Profiles

Importing Data

Assigning Validations

Enabling Node Types

Chart of accounts segment values and hierarchies can be extracted from E-Business Suite and output to a Data Relationship Management import file using a concurrent request program. The Initialize Segment Values and Hierarchies request is run from each general ledger instance to output data for loading into Data Relationship Management. Each request can extract one value set of segment values and hierarchies. Request sets can be created to run the request for multiple value sets.

Import Profiles

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

Importing Data

The import process will perform the following tasks:

- Creates a Data Relationship Management version. The version name will be the same as the value set name in E-Business Suite.

- Assigns values to version and hierarchy properties defined in the application template for the E-Business Suite value set being loaded.

- Creates a node for each value in the value set and loads E-Business Suite segment property values into global node properties defined in the application template.

- Creates a separate hierarchy for each top node (hierarchy) in E-Business Suite. The name of each hierarchy will correspond to the description of the parent value of the top node from the parent-child relationship.

- Creates orphan nodes for segment values that do not have any parent-child relationships in E-Business Suite.

- Checks for invalid characters to enforce alphanumeric node names.

Assigning Validations

Data Relationship Management validations are not automatically assigned to the version of data created by the import process. Enable the validations included in the Oracle General Ledger application template to ensure that nodes are in accordance with the value set configuration in E-Business Suite. Assign validations at the version level according to the table below.

Validation

Assignment Value

Account Type Required

Batch

Max Description Length

Both

Natural Account Required Fields

If the version represents a natural account: Batch; otherwise: None

Parent Posting

Batch

Required Fields

If the version represents a natural account: None; otherwise: Both

Segment Value Max Length

Based upon the definition of the related value set

Segment Value Uppercase

Based upon the definition of the related value set

Start Date Before End Date

Both

See " Validating Segment Values and Hierarchies " for more information on these validations.

Enabling Node Types

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 some additional configuration. 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.

Managing Segment Values and Hierarchies for Oracle General Ledger

In This Section:

Managing Oracle General Ledger Value Sets

Managing Chart of Accounts Segment Values

Managing Hierarchies of Segment Values

Validating Segment Values and Hierarchies

Loading Segment Values and Hierarchies into Oracle General Ledger

The Data Relationship Management data model is significantly different from that of Oracle E-Business Suite and Oracle Fusion Accounting Hub. Data Relationship Management groups multiple hierarchies consisting of multiple nodes into one or more versions, whereas the Oracle General Ledger systems have multiple chart of accounts value sets (segments), each with segment values (nodes), and in the case of Oracle Fusion Accounting Hub, trees (hierarchies) and tree versions. The following examples compares the Data Relationship Management andOracle General Ledger data models:

Data Relationship Management

Oracle E-Business Suite General Ledger

Oracle Fusion Accounting Hub

Version

Hierarchy

Top Node

Value Set

Parent

Value Set

Tree

Version

Account 2011

Balance Sheet

BalSheet

Account

BalSheet

Account

Balance Sheet

2011

Account 2011

Income Statement

NetIncome

Account

NetIncome

Account

Income Statement

2011

Entity 2010

Function

Total Function

Entity

Total Function

Entity

Total Function

2010

Entity 2011

Function

Total Function

Entity

Total Function

Entity

Total Function

2011

Managing Oracle General Ledger Value Sets

Oracle General Ledger value sets are managed using Data Relationship Management versions. Each version corresponds to a single chart of accounts value set by default.

Caution!

All hierarchies for a value set in Oracle Fusion General Ledger will be replaced with those in Data Relationship Management when the E-Business Suite integration runs. Make sure all hierarchies for the value set exist in Data Relationship Management before running the Import Segment Values and Hierarchies process in E-Business Suite.

Data Creator and Data Manager users create versions in Data Relationship Management for each value set. Version-level properties are used to associate versions to Oracle General Ledger value sets.

Version-level Property

Description

Allow Export

Enables export of the version to Oracle General Ledger

Natural Account

Identifies whether the Oracle General Ledger value set is for Natural Accounts

Value Name Max Length

Identifies the maximum length for the value name in the value set

Value Set

Identifies the name of the Oracle General Ledger value set for the nodes and hierarchies managed in the Data Relationship Management version

Value Set Master

Identifies whether the Data Relationship Management version is the primary source of Oracle General Ledger segment values for a given value set

For more information on versions and version properties, see the Oracle Hyperion Data Relationship Management Users Guide.

Managing Chart of Accounts Segment Values

Data Relationship Management nodes are used to create and maintain Oracle General Ledger segment values. Each Data Relationship Management node corresponds to a single Oracle General Ledger segment value. In Data Relationship Management, nodes are managed in hierarchies. Data Creator or Data Manager users must create at least one hierarchy in each version to manage the nodes that represent the segment values for a given value set. Multiple hierarchies can be used to organize different groups of segment values.

Node-level properties in Data Relationship Management are used to manage the Oracle General Ledger properties for segment values.

Node-level Property

Description

Account Type

Indicates the account type

Allow Budgeting

Indicates whether budgeting is allowed for the segment value

Note:

This option is only valid for the Oracle E-Business Suite General Ledger.

Allow Posting

Indicates whether it should be possible to post to the segment value

Enabled

Indicates whether the account is enabled

End Date

Indicates the effective end date for the node

Note:

This date should be later than the start date

Financial Category

Indicates the financial category for the account

Level

Describes a values relative level in its hierarchy structure

Node Type

Indicates the type of node

Parent

Indicates whether the segment value is a parent

Reconcile

Indicates whether the account is a reconciling account

Rollup Group

Identifies a group of parents for reporting or other application purposes

Start Date

Indicates the effective start date for the node

Third-Party Control Account

Indicates whether the account is a third-party control account

Value Set Order

Indicates the value set order

The properties displayed for nodes for an Oracle General Ledger value set are managed by Data Relationship Management node types. The Natural Account property for versions controls whether the properties for Natural Accounts are displayed for nodes in the version or properties for a standard value set are displayed.

The following table lists the properties that are available for each node type:

Property

Natural Account

None

Account Type

X

Allow Budgeting

X

X

Allow Posting

X

X

Enabled

X

X

End Date

X

X

Financial Category

X

Level

X

X

Parent

X

X

Reconcile

X

Rollup Group

X

X

Start Date

X

X

Third-Party Control Account

X

Value Set Order

X

X

The following additional node-level properties are available to manage alternate descriptions for Oracle General Ledger segment values in different xml:lang uages. These properties are pre-configured in the application template to be hidden from display or modification by users. To enable support for one or more alternate descriptions, disable the Hidden parameter for the property definitions for those descriptions.

- Description: Arabic

- Description: BR Portuguese

- Description: CAD French

- Description: Croatian

- Description: Czech

- Description: Danish

- Description: Dutch

- Description: Finnish

- Description: French

- Description: German

- Description: Greek

- Description: Hebrew

- Description: Hungarian

- Description: Icelandic

- Description: Italian

- Description: Japanese

- Description: Korean

- Description: LA Spanish

- Description: Lithuanian

- Description: Norwegian

- Description: Polish

- Description: Portuguese

- Description: Romanian

- Description: Russian

- Description: Simplified Chinese

- Description: Slovak

- Description: Slovenian

- Description: Spanish

- Description: Swedish

- Description: Thai

- Description: Traditional Chinese

- Description: Turkish

For more information on nodes and node properties, see the Oracle Hyperion Data Relationship Management Users Guide.

Managing Hierarchies of Segment Values

Data Relationship Management hierarchies are used to create and maintain hierarchical relationships for Oracle General Ledger segment values. Each Data Relationship Management hierarchy within a version corresponds to a hierarchy of segment values for an Oracle E-Business Suite value set and a tree version for an Oracle Fusion Accounting Hub value set.

Data Creator and Data Manager users create hierarchies in Data Relationship Management for each version.

The following hierarchy-level properties are used to control the creation or update of hierarchies and trees in Oracle Fusion General Ledger:

Property

Description

Allow Hierarchy Export

Enables the export of the hierarchy to Oracle General Ledger

Tree Name

Indicates the name of the tree in Oracle General Ledger (applies to Oracle Fusion Accounting Hub only)

If the Tree Name property is not defined, the hierarchy name in Data Relationship Management is used for the tree name in Fusion Accounting Hub.

If the value of the Tree Version Name property does not match an existing version of a tree in Fusion, a new tree version with that name is created.

If the value of the Tree Version Name property matches an existing tree version in Fusion, the existing tree version is updated.

The following version-level properties are used to control the creation or update of tree versions in Fusion Accounting Hub.

Property

Description

Effective Start Date

Indicates the effective start date for the version (applies to Oracle Fusion Accounting Hub only)

Effective End Date

Indicates the effective end date for the version (applies to Oracle Fusion Accounting Hub only)

Tree Version Name

Indicates the name of the tree version in Oracle General Ledger (applies to Oracle Fusion Accounting Hub only)

If the Tree Version Name property is specified in Data Relationship Management and matches an existing Tree Version Name in Fusion Accounting Hub, the Fusion tree version is updated.

If the Tree Version Name property is specified in Data Relationship Management but does not match an existing Tree Version Name in Fusion Accounting Hub, a new Fusion tree version is created.

If the Tree Version Name property is not specified in Data Relationship Management, a new Fusion tree version is created using the name of the version from Data Relationship Management.

Note the conditions in the following table.

Condition

Fusion Response to Condition and Follow-up Task

New Tree Version Name with Tree Version Effective Start/End Date overlaps with an existing version in Fusion

This condition fails audit in Fusion.

Update the date in Data Relationship Management and then re-import.

Existing Tree Version Name with different Tree Version Effective Start/End Date in Data Relationship Management than in Fusion

Dates are updated in Fusion but require the user to manually update the status from draft to active. During this process, Fusion checks to make sure there are no date overlaps.

Existing Tree Version Name with different Tree Version Effective Start/End Date in Data Relationship Management that overlaps with a different existing version in Fusion

This condition fails audit in Fusion.

Update the dates in Data Relationship Management and then re-import.

Validating Segment Values and Hierarchies

Oracle General Ledger segment values and hierarchies are validated to ensure data integrity in the following ways:

- Real-time validations run in Data Relationship Management as users perform changes and prevent invalid changes from being saved

- Batch validations are run explicitly by users in Data Relationship Management after changes are made and can check an entire hierarchy or version

- Validations are run during the load of segment values and hierarchies into Oracle General Ledger

The following validations are enforced along with their applicable node types:

Validation

Description

Natural Account

None

Account Type Required

The Account Type property must be defined for a Natural Account value set value.

X

Max Description Length

The description of an Oracle General Ledger value set value must not exceed 240 characters.

X

X

Natural Account Required Fields

The following properties must be defined for a Natural Account value set value: Enabled; Allow Posting; Third-Party Control Account; Allow Budgeting; Reconcile.

X

Parent Posting

The Allow Posting property cannot be set to True for a parent node.

X

X

Required Fields

The following properties must be defined for a value set value: Enabled; Allow Posting; Allow Budgeting.

X

Segment Value Max Length

The segment value name length must be less than or equal to the maximum for the value set.

X

X

Segment Value Uppercase

The segment value must be all uppercase.

X

X

Start Date Before End Date

The Start Date must be before End Date.

X

X

Validations must be assigned to versions in Data Relationship Management based on the specified Oracle General Ledger value set defined for each version. For more information on assigning validations, see the Data Relationship Management Administrators Guide.

Loading Segment Values and Hierarchies into Oracle General Ledger

Chart of accounts segment values and hierarchies are loaded from Data Relationship Management into Oracle General Ledger using a concurrent request program. The program is available as a concurrent request in Oracle E-Business Suite or as an Enterprise Scheduler Service request in Oracle Fusion Accounting Hub. These requests are run from each Oracle E-Business Suite or Oracle Fusion Accounting Hub instance to retrieve data from a Data Relationship Management application.

The following requests are used for running the concurrent request program:

- Load Segment Values and Hierarchies - imports chart of accounts data into Oracle E-Business Suite

- Load Accounts and Hierarchies - imports chart of accounts data into Oracle Fusion Accounting Hub

Each request can load one value set of segment values and hierarchies. The request will only create or update segment values and hierarchies for the chart of accounts accessible through the users 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 E-Business Suite is successful and provide summary information about the information imported from Oracle Data Relationship Management.