Single segment or chartfield mappings define a simple one-to-one mapping between source and target dimension members. When you create single segment or chartfield mappings, you can optionally define:
A member prefix or suffix type and value
Segment hierarchies to extract from the source system
Orphan member handling
Statistical Account handling
To define the mapping details:
In Prefix/Suffix Value, enter the member prefix or suffix.
Member prefixes are inserted before the source member code. Although optional, it is important to prefix the segment values with a prefix defined for the corresponding dimension when those members do not exist in the target application.
Member suffixes are inserted after the source member code.
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 one parent. Fusion and E-Business Suite support instances where a segment value can roll up to two parents.
Select Concat Name to Alias to concatenate the Name and Alias.
From EPMA Option, select the EPMA metadata load option.
Metadata load options:
Merge as Primary—Merge as Primary processes all sections and adds new dimensions, members, relationships, properties and associations that exist in the source, but do not exist in the Shared Library or target application. No dimensions, members, relationships, properties, or associations are removed. If a dimension, relationship, member, or property specified in the source exists in the Shared Library or target application it is overwritten with the value specified in the source. (Members are not moved, but overwritten.) Properties not included in the source are unchanged in the Shared Library or target application.
Note:
If a member has multiple instances in a dimension, the IsPrimary column specifies which instance is primary and which instances are shared. The IsPrimary parameter is optional; however, Oracle strongly recommend that you use it. If left undefined, it defaults to “True”, which assumes that the member is primary. If you do not define the IsPrimary parameter or when there are duplicate members defined as primary, a warning is displayed in the Import Results file.
Merge as Move—This mode processes only members with IsPrimary set to true, and ignores any others. During processing, the first line specifying a primary location for a member is executed, any subsequent lines specifying a different primary location are ignored, and a warning message is displayed.
Replace—All new elements are added and all property updates are made. Then, any members or member relationships that are not specified in the source are deleted from the Shared Library or target application. You can also use replace mode to reorder members under a parent. Properties not included in the source are unchanged in the Shared Library or target application.
This mode does not create Shared members unless they are defined in the import file (IsPrimary=false). This mode can detect a primary member under a new parent and process it as a move.
Note:
The Replace option does not display the Reorder Type and Reorder Existing Members options.
For Fusion and E-Business Suite source systems:
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 the time balance property is set to “Balance,” it is considered an ending value in a summary time period for the period total.
From the Hierarchy Region tab, click Add to define the hierarchy region.
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.”
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.
For PeopleSoft source systems:
From the Hierarchy Region tab, click Add to define the hierarchy region tree.
In a base hierarchy, other parts of the hierarchy that share a parent are shared. They cannot be set to "Store Data." Unshared members; however, have the "Store Data" property set. All nonshared members of base hierarchies have the “Store Data” property set. However, shared members cannot be set to “Store Data.”
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.
From Select how to process source orphan members, select the method for handling orphan members:
Ignore—No orphan members from the source are extracted.
Create as Root Member—Root members are created, and orphan members are not. All members are created at the top level of the hierarchy.
Create as Children of—Orphan members are placed as children of the member specified in the entry field to the right “Create as Children of field.”
Planning only: Select the Plan Type for the Accounting and Entity dimensions.
Financial Management 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, 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, all combinations of receivable and payable accounts exist among the transacting partner companies. Only with these natural accounts are the receivable and payable position between the Intercompanies known.
or enter the Starting Parent.