The Company consolidation routine is to be preferred if:
- You need better currency translation for G/L balances (there are more possibilities to get an exact exchange rate).
- You want better control of what is transferred and when to do it.
- A “living” corporate company is requested with possibilities to revalue, change summary identities, rebuild, etc.
The Group reporting routine is to be preferred:
- When you want to work with other balance groups than G/L (GLBAL).
- When you want to follow up on a daily operating basis.
The following outlines the differences between the Company consolidation routine and the Group reporting routine.
| Area | Company consolidation | Group reporting | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Applications | Application FIN must be active. Company consolidation only uses G/L balances. The balance type used for amounts is 301, if activated, otherwise type 302. For quantities, the balance type 305 is used. | Can use all active balance types for all applications. | ||||||||||
| Consolidation type | The originating company decides the consolidation type which indicates, e.g., the exchange rate’s time, level code and period. The following consolidation types exist:
For balances:
For budgets: The budget exchange rate is handled separately. Budget values are retrieved according to the specified parameters. Note: It is mandatory to define a consolidation type on main account level for all accounts which are to be transferred. Otherwise, balances and budget values will not be retrieved. |
The reporting company decides the consolidation type which indicates, e.g., the exchange rate’s time, level code and period. The following consolidation types are supported by group reporting:
For balances:
For budgets: Same as for Company consolidation. Note: It is optional to define a consolidation type. Balances and budgets are always transferred. However, for balances, if a consolidation is not defined on main account level, the type from Work with system balance types is defaulted. |
||||||||||
| Error handling | Generates printouts of consolidation conversions (report, errors, etc.). Update can be done even if errors exist in consolidation, but will end up in journal in error. | Uses program Work with BIW transactions in error and the alert functionality to track errors. Update can only be done if errors have been corrected. | ||||||||||
| Updates | Updates balances and budgets for the selected period(s) at request.
Balances are transferred and updated as G/L transactions. |
Can update each transaction immediately, (both in the originating company and the reporting company), if update jobs are active, making it a true on-line system.
Balances are not updated at transaction level. |
||||||||||
| Originating company code | The originating company is always used as originating company code at transfer to the corporate company. | The original originating company code is always transferred to the reporting company. |