US Eliminations Setup 
US eliminations functionality addresses the posting of Intercompany US eliminations in scenarios where a full legal consolidation application is not required, such as within a standard financial application.
The following are required to perform Intercompany eliminations within an application:
The application must include a dimension of type I, Intercompany.
The Intercompany dimension must include the property ENTITY, whose values are entity names.
The account dimension must include the property ELIMACC, whose values are account names.
The entity dimension must include the property ELIM, whose values are Y or blank.
The appropriate business rule table must be set up.
A DTS package executing the Intercompany logic must be available. This configuration not only allows Intercompany details to be entered for any account, but it also supports an automatic elimination-by-level for all desired accounts.
When reporting the financial results of a group of entities, you may want to see the results for the group net all Intercompany activity within the group. Therefore, the system identifies Intercompany activities and balances and posts entries so these activities and balances are fully eliminated when looking at the overall results for the group. US eliminations functionality addresses the posting of Intercompany eliminations in scenarios where a full legal consolidation application is not required such as within a standard financial application. When utilizing a legal consolidation application, Intercompany eliminations are normally handled as part of an automatic adjustments function.
Intercompany elimination entries should be reflected only in groups in which both the entity and the partner entity are part of the group. To address this, US eliminations uses a concept known as posting at first common parent.
US eliminations are normally used in financial applications, as opposed to legal consolidation applications.
The business rules table for US eliminations defines the data sources to eliminate. For each of these data sources you then define the corresponding destination data source under which the system should post the elimination postings.
The values entered in the following properties determine default elimination logic:
Dimension |
Property |
Length in Characters |
Content |
|---|---|---|---|
Account |
ELIMACC |
20 |
A valid account against which the actual Intercompany account to be eliminated should be offset |
Entity |
ELIM |
1 |
Y or blank |
Intercompany |
ENTITY |
20 |
The entity ID corresponding to this Intercompany member |
Currency |
REPORTING |
1 |
Y or blank |
The default elimination logic does the following:
Scans all base level non-elimination entities (entities having the property ELIM <> Y).
In case the application has a currency dimension, restricts its action to all reporting currencies only (currencies having the property REPORTING=Y). Data in local currency cannot be eliminated because it is in different currencies.
Eliminates all values of the accounts to be eliminated (accounts having property ELIMACC<>blank) into the desired plug account (the account specified by the ELIMACC property itself).
The elimination is posted to the elimination entity immediately below the first common parent. The common parent is derived as follows:
For a particular record the system identifies the two entities for which a common parent must be found. The first entity is the current entity member and the second entity is the entity corresponding to the current Intercompany member. This entity is obtained reading the content of the property ENTITY of the current Intercompany member.
The system searches in a selected entity hierarchy for the first member that has both entities as descendants. This is the common parent.
Then the system searches in the immediate descendants of the common parent for a valid elimination entity (an entity having the property ELIM=Y). This is the entity where the results of the elimination are stored.
The default elimination logic does its searches in the first organizational structure (hierarchy) of the entity dimension. This can be modified to have the elimination performed in all hierarchies existing in the entity dimension. If no common parent is found, no elimination occurs. If no elimination entity is found below the first common parent, the next common parent is searched.