Defining the Metadata Rule Details

  To define the mapping details:

1. Optional: Enter the member prefix.

   The member prefix is inserted before the source member code. Although optional, it is important to prefix the segment values with a prefix defined for the corresponding Performance Management Architect or Classic Financial Management or Planning dimension if those members do not exist in the target application.

   Note:

   When you perform the next steps to define the hierarchy region starting parent, consider that Planning, Essbase, and Financial Management do not allow members to roll up to the parent under the same root. When extracting, specify hierarchies where every node has only one parent. E-Business Suite supports instances where a segment value can roll up to two parents.

2. For E-Business Suite source systems:

   1. For Planning and Essbase applications—Account dimension mapping details: Select the Time Balance Property for Balance Sheet Accounts and Time Balance Property for Income Statement Accounts.

      The time balance property specifies how the value of summary time periods is calculated. If set to Flow, it is an aggregate of all values for a summary time period as a period total. If set to Balance, it is an ending value in a summary time period as the period total.

   2. Click Add to define the hierarchy region starting parent.

   3. Click or enter the Starting Parent.

   4. Select Base Hierarchy.

      The base hierarchy indicates the part of the hierarchy that is the base and that other parts of the hierarchy that share the same parent are shared. All nonshared members of base hierarchies have the “Store Data” property set. However, shared members cannot be set to “Store Data.”

   5. Select a prefix or suffix for the hierarchy, and then, enter a prefix/suffix value.

      The parent prefix is applied only to the parent. To enable alternate rollup hierarchies, the Prefix/Suffix value applies only to parent members. Parent members cannot be shared and must have a unique name. In addition, parent members do not store data.

3. For PeopleSoft source systems:

   1. For Planning and Essbase applications—Account dimension mapping details: Select the Time Balance Property for Balance Sheet Accounts and Time Balance Property for Income Statement Accounts.

      The time balance property specifies how the value of summary time periods is calculated. If set to Flow, it is an aggregate of all values for a summary time period as a period total. If set to Balance, it is an ending value in a summary time period as the period total.

   2. Click Add to define the hierarchy region tree.

   3. Click or enter the tree name.

   4. Click or enter the effective start date.

   5. Select Base Hierarchy.

      The base hierarchy indicates the part of the hierarchy that is the base and that other parts of the hierarchy that share the same parent are shared. All non-shared members of base hierarchies have the “Store Data” property set. However, shared members cannot be set to “Store Data.”

   6. Select a prefix or suffix for the hierarchy. Then, enter a prefix/suffix value.

      The parent prefix is applied only to the parent. To enable alternate rollup hierarchies, the Prefix/Suffix value applies only to parent members. Parent members cannot be shared and must have a unique name. In addition, parent members do not store data.

4. For Planning applications only: Select the Plan Type for Accounting and Entity dimensions.

5. For Financial Management applications only: If you are mapping an Entity dimension enter the following details for intercompany segments, depending on your source system:

   • Intercompany Segment Value

   • For Intercompany Default, select Yes or No

   In the scenario where the Intercompany segment is defined, the Intercompany transactions are identified based on the Intercompany segment. Typically, only one set of natural accounts is required for accounting the receivable and payable among the Intercompanies.

   In the scenario where there is no Intercompany segment, the Intercompany transactions should be identified based explicitly on the natural account segment. Typically, there should be all combinations of receivable and payable accounts among the transacting partner companies. Only with these natural accounts are the receivable and payable position between the Intercompanies known.

6. Click Save.