Setting up FDMEE Source Accounting Entity Group to extract data from multiple accounting entities in a single data load rule

An accounting entity group is a grouping of multiple accounting entities and is used to extract data from multiple source accounting entities using a single data load rule. The snapshots and content used in this post relate to Oracle EBS. The same concept would apply when using other source systems or ERP’s.

On a recent project, I came across a requirement to load multiple accounting entities. The source system was Oracle EBS and FDMEE had been integrated with Oracle EBS to pull data and facilitate drill through to Oracle EBS. Currently only one accounting entity was being extracted from Oracle EBS. Additional new ledgers had been created in Oracle EBS that needed to be extracted and loaded to Hyperion. Hence an accounting entity group was setup in FDMEE to facilitate loading of all the new entities using a single data load rule.

Ledgers in Oracle EBS show up as source accounting entities in FDMEE when the source system is initialized in FDMEE. The source accounting entities can be accessed by clicking on the ‘Source Accounting Entities’ link in the Setup tab within FDMEE. The figure below shows an example of how the source accounting entities are displayed in FDMEE. Note that they are displayed under the ‘Entities’ tab (highlighted in red)

FDMEE Source Accounting Entities

Assuming that (normally) each of the entities require a common mapping and have other things in common like chart of accounts, calendar etc. so that one import format can be used for all the entities, the next step would be to create a source accounting entity group. Click on the Entity Groups tab (highlighted in green) to add a new source accounting entity group. Click on the Add button and give a name to the source accounting entity group. Select all the source accounting entities that you want part of this group and then save this group.

FDMEE Source Accounting Entity Group

The next step would be to create an import format. Note that when you create an import format you need to provide a source accounting entity. You can select any accounting entity that you have selected as part of the accounting entity group. This assumes that all the accounting entities have a common chart of accounts thus having similar mapping requirements.

Next, create a location. When you create a location ensure that you do not select anything in the Accounting Entity box i.e. ensure you keep this blank so that when you create a data load rule for this location, you can select the source accounting entity group. (If you provide an accounting entity when creating a location and then when you create a data load rule for that location, the system prevents you from selecting a different accounting entity OR an accounting entity group)

FDMEE Location with Accounting Entity kept blank

Next, create a data load rule for the location you created in the previous step. Note that now you have the option of selecting a source accounting entity OR a source accounting entity group. Select the source accounting entity group that you created earlier. Set other options as required and save the data load rule.

FDMEE Data Load Rule with Accounting Entity Group

Update the data load mappings as required for your ledger and other dimension mappings. Execute the load rule. Assuming the load rule has executed successfully you should see that that load rule has extracted data for all accounting entities (which are part of the source accounting entity group) successfully. Given below is a snapshot from the process details.

FDMEE Process Details showing Accounting Entities

Given below are a set of constraints applying to entity groups as given in the Oracle documentation:

  • Accounting entity groups can be used only with data rules.
  • If a data rule in a location includes an accounting entity, then the rule is constrained by the accounting entity in the definition. In this case, the data rule in the location cannot use an accounting entity group.
  • If a data rule in a location has no accounting entity, then an accounting entity or an accounting entity group must be specified in the definition. The data rule execution extracts data from either a single accounting entity or from all the accounting entities in an accounting entity group.
  • Write-back rules accept only an accounting entity (and not an accounting entity group) in their definition.
  • Metadata rules accept only an accounting entity (and not an accounting entity group) in their definition.
  • FDMEE does not enforce that entities belong to the same Chart of Accounts

 

 

Leave a Comment