Defining Locations

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 enabling 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 Oracle Hyperion Financial Data Quality Management, Enterprise Edition scripts.

Note:

You can create duplicate locations with the same source system and application combination.

To create, edit, and delete import locations:

1. On the Setup tab, under Integration Setup, select Location.

2. In Location, click Add.

3. From Location Details, in Name, enter the location name.

4. From Import Format, enter the import format.

   The import format describes the source file structure, and it is executed during the source file import step. FDMEE supports file-based imports for those users who do not have direct connections to their source data but do have source data residing in a text file. A corresponding import format must exist before it can be used with a location.

   Additionally:

   • The source system is automatically populated based on the import format.
   • The Source field displays the source application based on the import format.

   You can also click and select an import format.

5. In Accounting Entity, specify the source system accounting entities (business units or ledgers) to use for the location.

   For an E-Business Suite source system, the Accounting Entity is the ledger. For PeopleSoft source systems, the Accounting Entity is the business unit.

   If the accounting entity is selected here, then in the Data Load Rules, the accounting entity populates automatically.

   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.

6. In Target Application, specify the target application associated with this location.

   You can also click to search for a target application.

7. Optional: Enter or click to select the Accounting Entity. (For E-Business Suite, select the ledger. For PeopleSoft, select the business unit.)

8. In Functional Currency, specify the currency of the location.

   Note:

   For Financial Consolidation and Close and Tax Reporting customers: To load data to actual currency rather than entity currency when the currency is fixed, set the currency in the Functional Currency field in the Location option. You can also add a Currency row in the import format and map it. See Defining the Import Format.

   Financial Consolidation and Close can also specify Parent Input, Contribution Input, and Translated Currency Input in this field to create and post journals to different currencies other than the entity currency.

9. In Parent Location, enter the parent assigned to the location.

   Parent mappings are 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 apply to all child and parent locations.

10. In Data Value, specify the extra dimension that is used only for integration with multiple dimension target systems.

    This dimension is associated with a data load location. In Oracle Hyperion Financial Management, the data value is the value dimension. When FDMEE 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, if no value is entered in this field when integrating 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>

11. Optional: In Logic Account Group, specify the logic account group to assign to the location.

    A logic group contains 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.

    The list of values for a logic group is automatically filtered based on the Target Application under which it was created.

12. 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.

    The list of values for a check entity group is automatically filtered based on the Target Application under which it was created.

13. 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.

    The list of values for a check rule group is automatically filtered based on the Target Application under which it was created.

14. Click Save.

15. 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, and Data Load.

    Tip:

    To filter by the location name, ensure that the filter row is displayed above the column headers. (Click to toggle the filter row.) Then, enter the text to filter.

To specify free form text or values for use with scripts:

1. On the Setup tab, under Integration Setup, select Location.

2. In the Location Detail, click the Integration Option tab.

3. From Integration Option, in Integration Option 1-4, specify the free form text or value, and then click OK.

   The information is accessible from the Integration Option fields in the Location table.