Intercompany Account Dimension
Return to Financial Consolidation Model Overview.
The Intercompany Account Dimension is automatically created during updating Consolidation Rules procedure. It consists of the following parallel hierarchies:
-
All Intercompany Matchings - based on D and S rules of Consolidation Rule Dimension.
-
All Consolidations - based on the rules of Consolidation Rule Dimension.
Base elements names of this dimension consist of the information about Cube, the parameter defining whether the rule is inverted, the account, the transaction type, base element of the Consolidation dimension.
The Intercompany Account can be configured through their attributes:
Attribute | Description |
AggregationType | Controls the aggregation behavior of semi-additive measures. |
Name | Readable name of the account. Localized translations can be provided. This attribute is visible in the report. There is no hard-coded behavior implemented on this name. (string) |
ID_Name | Technical element name of the article as well as the readable name. If localized translations are provided Name attribute, this attribute will also become localized. This attribute is visible in the report. There is no hard-coded behavior implemented on this name. (string, calculated) |
Description | Long text description of the account. This attribute can contain a definition of the amounts booked to the account or instructions for the planners. Localized translations can be provided. (string) |
Calculation | Calculation rule |
CalculationDependencies | Dependencies for the calculation |
TargetRestriction | Restriction of the target area the calculation applies to |
Mismatches Threshold | Threshold for intercompany differences to be reported as a mismatch. |
Transaction Currency Mismatches Threshold | Threshold for intercompany differences in transaction currency to be reported as a TC mismatch. |
PJ.Consolidation | Posting Journal Consolidation |
PJ.ConsolidationRule | Posting Journal Consolidation Rule |
PJ.Name | Short text for the journal entry header. This can be any plain text, which may optionally contain the following keywords (in all caps): LEGAL_ENTITY_ID_NAME: ID_Name attribute of the legal entity PARTNER_ENTITY_ID_NAME: ID_Name attribute of the partner entity LEGAL_ENTITY : Element name of the legal entity PARTNER_ENTITY : Element name of the partner entity NAME : Name of the consolidation rule SCOPE : Element name of the current scope HOLDING : Element name for the current scope’s holding entity |
PJ.Description | Longer text for the journal entry header. This can be any plain text, which may optionally contain the following keywords (in all caps): LEGAL_ENTITY_ID_NAME: ID_Name attribute of the legal entity PARTNER_ENTITY_ID_NAME: ID_Name attribute of the partner entity LEGAL_ENTITY : Element name of the legal entity PARTNER_ENTITY : Element name of the partner entity NAME : Name of the consolidation rule SCOPE : Element name of the current scope HOLDING : Element name for the current scope’s holding entity |
PJ.Balance Constraint | One of the following choices: Legal Entity : The journal entry is only valid if all lines of each legal entity balance (sum of all credit lines equal to the sum of all debit lines). Journal Entry : The journal entry is only valid if all lines of the entire journal entry balance (sum of all credit lines equal to the sum of all debit lines). None: The journal entry is not checked for the balance (sum of all credit lines compared to the sum of all debit lines). |
PJ.Group | Grouping of journal entry lines. Valid values are ordinals greater than zero. Entry lines of the same group are kept together and sorted by debit or credit and by amount. |
PJLine1.Description | Text for the line of the journal entry. This can be any plain text, which optionally contain the following keywords (in all caps): LEGAL_ENTITY_ID_NAME: ID_Name attribute of the legal entity PARTNER_ENTITY_ID_NAME: ID_Name attribute of the partner entity LEGAL_ENTITY : Element name of the legal entity PARTNER_ENTITY : Element name of the partner entity NAME : Name of the consolidation rule SCOPE : Element name of the current scope HOLDING : Element name for the current scope’s holding entity |
PJLine1.Legal Entity | Element of the Legal Entity dimension that figures are posted to. This can be manually typed in or one of the following keywords can be entered (in all caps): LEGAL_ENTITY : Element name of the legal entity PARTNER_ENTITY : Element name of the partner entity HOLDING : Element name for the current scope’s holding entity |
PJLine1.Partner Entity | Element of the Partner Entity dimension that figures are posted to. This can be typed in or one of the following keywords (in all caps): LEGAL_ENTITY : Element name of the legal entity PARTNER_ENTITY : Element name of the partner entity HOLDING : Element name for the current scope’s holding entity |
PJLine1.Cube | The cube to post the amount to, e.g. "Profit and Loss", "Balance Sheet", etc. |
PJLine1.Account | Element of the BS Account, PnL Account or CF Account dimension to which figures are posted. This can be typed in manually or entered as one of the following keywords (in all caps): BS_ACCOUNT : Element name of the BS Account dimension as defined by the consolidation rule line detail. PNL_ACCOUNT : Element name of the PnL Account dimension as defined by the consolidation rule line detail. ACCOUNT : Element name of the account dimension as defined by the consolidation rule line detail. CLEARING_ACCOUNT : Element name of the account dimension as defined by the Clearing Account attribute of the eliminated account. |
PJLine1.Transaction Type | Element of the Transaction Type dimension which figures are posted to (only valid for the Balance Sheet cube(s)). This can be typed in manually or the following keyword (in all caps): TRANSACTION_TYPE : Element name of the transaction type dimension. |
PJLine2.Description | Text for the line of the journal entry. This can be any plain text, which optionally contain the following keywords (in all caps): LEGAL_ENTITY_ID_NAME: ID_Name attribute of the legal entity PARTNER_ENTITY_ID_NAME: ID_Name attribute of the partner entity LEGAL_ENTITY : Element name of the legal entity PARTNER_ENTITY : Element name of the partner entity NAME : Name of the consolidation rule SCOPE : Element name of the current scope HOLDING : Element name for the current scope’s holding entity |
PJLine2.Legal Entity | Element of the Legal Entity dimension that figures are posted to. This can be manually typed in or one of the following keywords can be entered (in all caps): LEGAL_ENTITY : Element name of the legal entity PARTNER_ENTITY : Element name of the partner entity HOLDING : Element name for the current scope’s holding entity |
PJLine2.Partner Entity | Element of the Partner Entity dimension that figures are posted to. This can be typed in or one of the following keywords (in all caps): LEGAL_ENTITY : Element name of the legal entity PARTNER_ENTITY : Element name of the partner entity HOLDING: Element name for the current scope’s holding entity |
PJLine2.Cube | The cube to post the amount to, e.g. "Profit and Loss", "Balance Sheet", etc. |
PJLine2.Account | Element of the BS Account, PnL Account or CF Account dimension to which figures are posted. This can be typed in manually or entered as one of the following keywords (in all caps): BS_ACCOUNT : Element name of the BS Account dimension as defined by the consolidation rule line detail. PNL_ACCOUNT : Element name of the PnL Account dimension as defined by the consolidation rule line detail. ACCOUNT : Element name of the account dimension as defined by the consolidation rule line detail. CLEARING_ACCOUNT : Element name of the account dimension as defined by the Clearing Account attribute of the eliminated account. |
PJLine2.Transaction Type | Element of the Transaction Type dimension which figures are posted to (only valid for the Balance Sheet cube(s)). This can be typed in manually or the following keyword (in all caps): TRANSACTION_TYPE : Element name of the transaction type dimension. |
Parameter1 - 8 | Possible additional Parameters |
Updated March 19, 2024