A location is the level at which a data load is executed in FDMEE. A Location is associated with one source system, but you can import data from multiple ledgers from that system. Each Location is assigned an Import Format, one or more Data Load Rules, and a Data Load Mapping. You define locations to specify where to load the data. Additionally, Locations allow you to use the same Import Format for more than one target application where the dimensionality of the target applications is the same.
The Location feature also enables you to specify free form text or a value using the integration option feature. Text or values entered for a location can be used with your FDMEE scripts.
Note: | You can create duplicate locations with the same source system and application combination. |
To create, edit, and delete import locations:
Select the Setup tab, and then under Integration Setup, select Location.
Enter or click
to select the Import Format.The source system is automatically populated based on the import format.
Optional: Enter or click
to select the Accounting Entity. (For E-Business Suite, select the ledger. For PeopleSoft, select the business unit.)If the accounting entity is selected here, then in the Data Load Rules, accounting entity populates automatically. See Defining Data Load Rule Details.
If the accounting entity is not specified here, you can specify the accounting entity in data rules. Doing so enables you to load data from multiple ledgers to business units from one location.
You can use locations with multiple import formats. For example, you can define the import format for the first location, Ledger 1. Then, define another import format for Ledger 2. In this case, you would create multiple locations with the same import format. You can also define multiple locations for target applications that are the same. In this case, you can define multiple locations for each business unit or ledger and reuse the import format.
Enter or click
to select the Target Application.Note:
When you create a location using a PeopleSoft Human Capital Management source system, the Functional Currency column displays ” Unlike PeopleSoft Enterprise Financial Management source systems, when FDMEE human resources data loads occur, there is no break out of amount by functional, entered, or translated currencies.
In Functional Currency, specify the currency of the location.
In Parent Location, enter the parent assigned to the location.
Parent mapping used to share mappings with other locations. Enter mappings at the parent location, and the related locations can use the same mappings. Multiple locations can share a parent. This feature is useful when multiple locations use one chart of accounts. Changes to a child or parent mapping table are applied to all child and parent locations.
In Data Value, specify the extra dimension that is used only for integration with multi-dimensional target systems.
This dimension is associated with a data load location. In Financial Management, the data value is the value dimension. WhenFDMEE creates the load file, the dimension value is entered for every data line that is loaded by the location. For example, the Data Value dimension is associated with the Value dimension in Financial Management. By default, when no value is entered in this field, for integration with Financial Management, the Data Value <EntityCurrency> is the default value.
When Search is selected, FDMEE connects to the Financial Management to get a list of valid data values. FDMEE takes the values from Financial Management and adds rows created by FDMEE that are a concatenation of the original value and “Adjustment Data Values”. FDMEE uses these newly created rows to manage journal loading to Financial Management.
The rows that FDMEE creates in the Data Value selection screen are:
[Contribution Adjs];[Contribution Adjs]
[Contribution Adjs];[Parent Adjs]
[Contribution Adjs];<Entity Curr Adjs>
[Contribution Adjs];<Parent Curr Adjs>
[Parent Adjs];[Contribution Adjs]
[Parent Adjs];[Parent Adjs]
[Parent Adjs];<Entity Curr Adjs>
[Parent Adjs];<Parent Curr Adjs>
<Entity Curr Adjs>;[Contribution Adjs]
<Entity Curr Adjs>;[Parent Adjs]
<Entity Curr Adjs>;<Entity Curr Adjs>
<Entity Curr Adjs>;<Parent Curr Adjs>
Optional: In Logic Account Group, specify the logic account group to assign to the location.
Logic groups contain one or more logic accounts that are generated after a source file is loaded. Logic accounts are calculated accounts that are derived from the source data.
Optional: In Check Entity Group, specify the check entity group to assign to the location.
When a check entities group is assigned to the location, the check report runs for all entities that are defined in the group. If no check entities group is assigned to the location, the check report runs for each entity that was loaded to the target system. FDMEE check reports retrieve values directly from the target system, FDMEE source data, or FDMEE converted data.
Optional: In Check Rule Group, specify the check rule group to assign to the location.
System administrators use check rules to enforce data integrity. A set of check rules is created within a check rule group, and the check rule group is assigned to a location. Then, after data is loaded to the target system, a check report is generated.
Optional: Perform these tasks:
To edit an existing location, select the location to modify, and then make changes as necessary. Then, click Save.
To delete a location, click Delete.
When a location is deleted, the location is removed from all other FDMEE screens, such as Metadata, Data Load, and Data write-back.
Tip:
To filter by the location name, ensure that the filter row is displayed above the column headers. (Use
to toggle the filter row.) Then, enter the text to filter.