IMPORTANT |
It is extremely important that you set up and work within your own company to maintain your data integrity. If you work within any other company, your exercises will not function as intended and the data of other students might be affected. Predictable exercise results require that your data is isolated in your own company. |
Purpose: The purpose of this exercise is to set up the basic data required for running this functionality.
Before you begin the consolidation exercises, make sure that the following exist:
Two or more companies, one of which is a parent company.
Opening Balances (Period 00) in the subsidiaries that should be consolidated.
Transactions in the subsidiary companies so that there is data to consolidate. Minimum is data in Period 1.
A budget in at least one subsidiary company.
A budget version in the parent company.
Note: Depending on the data to be consolidated, it may be necessary to set up the parent company as a holding company, i.e., a company that owns subsidiaries but that has no financial transactions of its own. For example, you need to set up a holding company if fixed asset or project code parts are to be consolidated to the parent. Because these code parts have specific functions and their own sub-ledgers, data cannot be consolidated into them from a subsidiary.
Purpose: The purpose of this lesson is to familiarize you with the basic data and requirements for the Consolidation process. This process involves gathering transactions from each period from one or more subsidiary companies and transferring the balances to the parent company.
Purpose: The purpose of this exercise is to set up the basic data required for the parent company. The subsidiary company's transaction data that is transferred to the parent must clearly be separate from the parent company's transaction data. This is accomplished through the use of a code part for consolidation purposes. Only parent companies require a consolidation code part. The rest of the setup ensures that the consolidated balances are posted correctly. All the transactions in this exercise should be performed in the parent company.
Windows:
Define Code String
Code Part Values
Account Types
Voucher Type
Currency Rate Types
Currency Rates
Posting Control
Company Relationships
Internal Name Code Used Code Part Function Name your consolidation code part Yes Consolidation
Identity | Description | Valid From | Valid To |
The ID for your subsidiary company (10 characters maximum) | A description of your subsidiary company | Back date at least one year | 12/31/2049 (future period) |
Note: Back the valid-from date to the earliest date on which any consolidation activities occurred.
Note: If only a few accounts will be used for consolidation, you can update the code part demands for each account instead of at the account type level.
Note: The purpose of the following steps is to use the correct currency rates and to post differences in accounting when multiple currencies are used. The currency rounding differences are posted to the account string based on the GP6 posting type. The currency recalculation rounding differences are posted to the account string based on the GP7 posting type. If multiple currencies are not being used, skip to the next exercise.
The final steps of this exercise will show you how to connect each subsidiary company to the parent company.
Purpose: The purpose of this exercise is to show you how to connect the subsidiary's Chart of Accounts/Accounting structure to the parent company. If the parent and subsidiary use the same chart of accounts, then the setup is simple, and you need to complete only the first three steps of this exercise. If the parent and subsidiary use different charts of accounts, or if the parent requires more detailed data during consolidation, then additional setup is necessary. The transactions in this exercise should be performed for each subsidiary.
Windows:
Define Code String
Account
Account Groups
Code Part Values
Note: The level of detail required for the consolidation determines which IFS Applications window should be used. If each account in the subsidiary must be consolidated to a different account in the parent, then you should use the Account window. On the other hand, if each group of accounts in the subsidiary will be consolidated to one account in the parent, then you should use the Account Groups window. An example of this would be the consolidation of all cash and cash equivalent accounts to one cash account in the parent. A combination of accounts and account groups could be used. If the account is the only code part to be consolidated, then you do not need to use the Code Part Values window.