Some important technical details are outlined in this document, such as:
- How the transactions and balances for the corporate company and the originating company respectively are treated in different routines within the corporate company.
- Which values are transferred from the originating company to the Interface files.
- The different system stages of the consolidation process from a technical perspective.
Corporate company transactions/balances
This table displays how transactions/balances for the corporate company and the originating company respectively are treated in different routines within the corporate company. It also illustrates in what way the values are shown in some of the routines.
Routines | Include | |
---|---|---|
Own values | Values from orig. comp. 1) | |
Revaluation | YES | YES |
Copy/Elimination of G/L journals | YES | YES |
Calculation/Redistribution | YES | NO |
Inflation revaluation | YES | NO |
Year end transactions | YES | NO |
Opening balances (ANOBOB) | YES | YES |
Openings balances as transactions | YES | YES |
Account balances retrieval at financial entry option | YES | YES |
G/L transaction enquiry | YES | YES |
1) Must have been defined in Work with company hierarchy maintenance for the corporate company.
Note: All new, manually created transactions (originally pertaining to the originating company) within the corporate company will be updated with the corporate company code as originating company code in the related field.
Exceptions are:
- Update of transactions from the Interface file (SROCIB)
- Copy/Elimination of G/L journals
- Opening balances (both in ANOBOB and as transactions)
The transactions created manually when running any of the exceptions above, within the corporate company, will receive the same originating company code as the base transactions.
Transfer overview
This table displays which values are transferred from the originating company to the Interface files.
Routines | Values transferred |
---|---|
Enter financial transactions | YES |
G/L transactions from Interface file | YES |
Revaluation | YES |
Copy/Elimination of G/L journals | YES |
Calculation/Redistribution | YES |
Inflation revaluation | YES |
Year end transactions | YES |
Opening balances (ANOBOB) | NO 1) |
Openings balances as transactions | NO 1) |
1) A separate routine is available for the creation of opening balances in the corporate company at start-up.
Technical flow
This section outlines the different system stages of the consolidation process from a technical perspective.
- The image below illustrates the process of creating the interface file, retrieving transactions, and updating the corporate company.
- The image below illustrates how the originating company code is retrieved to the corporate company.
Flowchart
Flowchart
If several levels are used, the originating company code will only be transferred one level up. This means that you can only follow historic balances from one originating company one level down.
For example, in the above illustration, the originating companies’ codes BB, BC, and BD will be converted to the originating company code BA when transferring balances from company BA to company AA. You will not be able see the balances that were transferred from company BB to company BA if you are in company AA. In company AA these balances will have the originating company code BA.