Consolidation export to Sage
From the consolidation data already extracted in BALCONSO (see documentation Extraction for conso), this function is used to generate a pre-consolidated balance export file destined for the Sage consolidation software, in the corresponding ASCII format.
Prerequisites
Refer to documentation Implementation
Screen management
Entry screen
Fields
The following fields are present on this tab :
Header
| Enter the company group code whose consolidated extraction data must be exported to the consolidation software. |
| This field is used to define the type of pre-consolidated ledger (local menu 2644) whose extraction data must be exported to the consolidation software. |
| No help linked to this field. |
| If this box is checked, the processing is carried out for the analytical accounting. |
File generation
| No help linked to this field. |
|
|
Close
Structure of the pre-consolidated balance file
The file expected to be entered into Sage Concept Consolidation is an ASCII file with the | as field separator and the . as decimal separator.
This file has a header/line structure: the header recording characterizes the extracted consolidated balance and the line recordings represent the balance totals.
Sage FRP Consolidation & Reporting fields |
| Sage X3 fields | ||
Delivery | Field description | Field comments | Mandatory? | Comments |
HEADER | __________ | __________ | __________ | __________ |
1 | CATP | Constant systematically entered | YES | "CATP" systematically mentioned |
2 | Category_Entry period_Allocation period | By default, the category must be CONSO | YES | The category is systematically CONSO. |
LINES | __________ | __________ | __________ | __________ |
3 | DONN | Constant systematically entered | YES | "DONN" systematically mentioned |
4 | Rank | Field not used | NO | Empty by default |
5 | Category_period | The header information is enough. | NO | Empty by default |
6 | Flag | On a maximum of 12 positions, of alphanumerical type | YES | Use of the ACCGRU of BALCONSO that contains either the consolidation code of the general account or the general account code itself. |
7 | Flows | On 12 positions maximum, of alphanumeric type. | NO | Loaded with F990 for the real accounts, and with F900 for the profit and loss accounts. |
8 | Evaluation method |
| YES | By default to CLOCAL, in other words, the pre-consolidated balance will have been extracted in company currency. (1) |
9 | Currency |
| NO | Loaded with the extraction currency, in order to allow comparison with the currency set up in the consolidation software. (cf. (1)) |
10 | Source entity | On a maximum of 12 positions, of alphanumerical type | YES | Use of CPYGRU of BALCONSO that contains either the consolidation code of the company or the company code itself. |
11 | Partner intra-group entity |
| NO | Use of BPRGRU of BALCONSO that contains either the consolidation code of the BP or the BP code itself. |
12 | Title intra-group entity |
| NO | Empty - Not used by the software |
13 | Group |
| NO | Empty - Not used by the software |
14 | Entry nature |
| NO | Empty - Not used by the software |
15 | Entry type |
| NO | Empty - Not used by the software |
16 | Amount |
| NO | Must contain the balance of the account(s). |
17 | Analytical dimensions |
| NO | |
18 | Standard |
| NO | "COMMON" systematically mentioned |
(1) When a file is transferred to the Sage consolidation software, the latter controls the file content (CLOCAL in position 8 and currency code in position 9) with its own setup data. In this way, if the currency entered in the file in position 9 is different from the currency declared in the consolidation software, the file is rejected.
(2) In Sage X3, data are currently stored in 2 fields: one providing the balance in absolute value (BLC of BALCONSO) and the other providing the balance sense (SNSBLC of BALCONSO with 1 for debtor et -1 for creditor).
Batch task
This function can be run in batch mode, but no dedicated standard task is delivered to run it.
Workflow Rules
The execution of the pre-consolidated balance export to the consolidation software can come along with the sending of an information e-mail if the EXPCONSO workflow rule has been activated (event code CSL).
This message stipulates the generation directory and the name of the generated file, as well as the code of the user who has launched the function.
The generation log file is included as an attachment.
Specific Buttons
This button is used to save the launch setups, exactly as it is done with the management of memo objects function, namely with the notion of standard memo. |
This button is used to recall the launch setups, exactly as it is done with the management of memo objects function, namely with the notion of standard memo. |
This button is used to delete the launch setups, exactly as it is done with the management of memo objects function, namely with the notion of standard memo. |
Error messages
In addition to the generic error messages, the following messages can appear during the entry :
"No conso to be exported on this scope"
For the selected group of companies, there are no recordings in BALCONSO, therefore there are no consolidation data to be extracted.
"No conso to be exported for this scope and this type of ledger"
For the selected group of companies AND the selected type of ledger, there are no recordings in BALCONSO, therefore there are no consolidation data to be extracted.