The Group reporting functionality provides cross company analysis, allowing corporate entities a global view of sales, etc., for each of their legal entities.
What this document contains:
- Setting up the corporate company
- Setting up the originating company
- Work with reporting conversions
- Work with data queue routines
- Error handling
- Routines supported by Group reporting
The following two companies are referred to within the Group reporting setup:
- Originating company = the company that sends the balances.
- Corporate company (also referred to as the reporting company) = the company that receives the balances.
When BIW transactions are transferred from each originating company to the corporate company, the information goes through a consolidation process (a merge) including, e.g., currency translation, period mapping, key value conversion, key mapping, key value validation, etc.
The Group reporting functionality is fully integrated with other functionality for balance analysis. This means that all balance transactions, received in the corporate company, can be analysed in, e.g., DC1 Analyser, DC1 Report Writer and the Balance enquiry.
The group reporting facility will allow you to:
- Set up a hierarchy of companies.
- Decide balance types to be sent to the corporate company.
- Convert your Chart of accounts into the format for the corporate company.
- Convert your system currency amounts, using exchange rates, into the system currency for the corporate company.
- Convert your company accounting periods into the corporate company accounting periods.
- Drill-down from On-line reports in the corporate company to the originating company.
Prerequisites
Both the originating company (sending company) and the corporate company (receiving company) must exist in the same DC1 system environment.
The originating/corporate companies cannot be a consolidation corporate company. However, the originating company can be an originating company both for group reporting and consolidation.
A Chart of account must exist in the corporate company for balance types with accounts as statistic key. In addition, an exchange rate must exist if system currency differs between companies. All other key values do not have to exist in their associated tables in the corporate company.
Drill-down from On-line reports only works one level down in the hierarchy (because conversion can be performed on each level).
Setting up the corporate company
The corporate company (receiving company) must be an existing company in DC1.
Setting up the originating company
The originating company (sending company) must be an existing company in DC1.
Program/Panel | To do |
---|---|
Work with system/custom balance types | Select the applicable menu item (System balance types and/or Custom balance types). The following fields apply:
|
Work with company hierarchy | This program is accessed from the Work with company hierarchy menu item when you are in the originating company. Define the corporate (reporting) company information for the originating company. |
Company hierarchy maintenance | Enter the following information:
Click OK. |
Account/summary id part relationship | Enter the following information:
Click OK. |
Currency translation settings | Enter the following information:
Click OK. |
Accounting period relationship | On this panel you convert the accounting periods of the originating company to the accounting periods of the corporate company. Note: Period conversion is always carried out within one fiscal year. This means that both companies, originating and reporting, must have the same set-up of the fiscal year, either calendar fiscal year or non-calendar fiscal year.
Enter the following information:
Click OK. |
Budget number selection and relationship | On this panel you decide which budgets to copy from the originating company to the corporate company. Enter the following information:
Click OK. |
Balance type selection | On this panel you decide which balance types to send from the originating company to the corporate company. Mark each selected balance type. Click OK. Click OK again to verify selection. |
Work with reporting conversions
Program/Panel | To do |
---|---|
Account/Sum id part conversions maint, header | This panel can only be accessed if you are working in an originating company. Only account parts which have been set up for conversion in the relationship file can be selected. This panel displays the relationship between the account parts in the corporate company and the account parts or summary id parts in the originating company that have been set up in your system.
Select the account parts. |
Account/Sum id part conversions maint, detail | The first detail panel displays the relationship between the account part numbers/summary part ID’s in the originating company and the account part numbers in the corporate company.
Select the record you want to maintain. |
Account/Sum id part conversions maint, detail | On the second detail panel you establish the relationship between the account part numbers/summary part id’s in the originating company and the account part numbers in the corporate company. Caution: As you can also convert balance accounts into trade accounts, and vice versa, you must be careful when creating the entries in this table, so that you do not become confused with the account types.
Note: Two field names can be valid for the following fields. They are either From account part or From summary id part.
Tip: You can also enter a mask. For example, __4_ means that only the accounts which have a 4 in the third position should be converted to the number below. You must complete the positions that you do not use with underscore characters. If there are several masks that match an account number, the system chooses the mask with the smallest number of underscore characters. If there are more than one with this number, the system chooses the one with a character (not underscore) in the position furthest to the left.
Tip: You can also enter an account mask. |
Work with data queue routines
For the balances to be updated the following routine must exist:
Routine | Description |
---|---|
BIWSND | Updates balances and sends them to the next company in the hierarchy. |
Error handling
The following error scenarios and the corresponding solutions are described:
- Scenario 1: Balances not updated in originating company
- Scenario 2: Balances not received in corporate company
- Scenario 3: Balances in error log file
- Scenario 4: Balances not updated in corporate company
Scenario 1: Balances not updated in originating company
If balances are not updated in the originating company, then check the following:
- That data queue routine BIWSND is active (see Work with data queue routines). If not, start the routine. If only the administration job is active then a rebuild is on-going and you have to wait until it is finished.
- That the balance types are active in the originating company (see Work with system/custom balance types), if not you must activate the balance type(s) and also select them to be sent to the corporate company. You have to rebuild balances from transactions in the originating company to update both the originating company and the corporate company.
Scenario 2: Balances not received in corporate company
If balances are not received in the corporate company, then check the following:
- That data queue routine BIWRCV is active (see Work with data queue routines). If not start the routine. If only the administration job is active, then a rebuild is on-going and you have to wait until it is finished.
- That the balance types are active in the corporate company (see Work with system/custom balance types). If not, then you must activate the balance type(s). You have to rebuild balances from transactions in the originating company to update the corporate company.
- That the balance types are selected to be sent to this company (see Work with company hierarchy). If not, then you must select the balance types and rebuild balances from transactions in the originating company.
Scenario 3: Balances in error log file
If balances are received, but not updated in the group corporate company, then check the error log file (Work with BIW transactions in error). If there are errors they can be corrected by either:
- Entering/changing entries in the associated tables in the corporate company.
- Changing conversion rule in the originating company. Caution: Since this solution will only affect the current and future transactions you should also perform a rebuild.
or
After the errors have been solved you have to delete the errors in the error log file to re-start the update of the balances. Note: Errors of type Warning are always updated. They are just information messages.
Scenario 4: Balances not updated in corporate company
If balances are still not updated in the corporate company, then check the following:
- That data queue routine BIWSND is active (see Work with data queue routines). If not, start the routine. If only the administration job is active, then a rebuild is on-going and you have to wait until it is finished.
- That no errors exist in the error log file (Work with BIW transactions in error).
Routines supported by Group reporting
The following routines are supported:
Routine | Description |
---|---|
Build historic balances/budgets | In this program you can move old balances from an originating company into a newly created corporate company. Click OK to start updating. Caution: You should only run this once for each originating company. |
Update break level texts | Break level texts are used in the corporate company to display description and validate key values that do not exist in their associated tables. When a key value does not exist a warning message is displayed in the error log file and a record is created in the break level text table with the key value.
In this program you can update break level texts (descriptions) for those break level text key values that do not have a text (description). Click OK to start updating. |
Rebuild balances from transactions | This routine is fully integrated with the Group reporting routine, e.g., a rebuild in an originating company also rebuilds balances for that company in the corporate company. |
Clear balances/budgets manually | This routine is fully integrated with the Group reporting routine, e.g., a clearance in an originating company also clears balances for that company in the corporate company. |
Rebuild summary identities | This routine is not integrated with the Group reporting routine, e.g., a rebuild in an originating company will only rebuild that company’s summary identities. A rebuild in a corporate company will rebuild ALL companies’ summary identities in the corporate company. This is because the corporate company can have a different setup of summary identity. This means that the original summary identity is not used and that it will always complement summary identities in the corporate company except for budgets entered on a specific summary identity. |
Budgets | All budget routines are fully integrated with the Group reporting routine, except historic budgets, e.g., budgets already entered in the originating company when starting the Group reporting routine. |