Abel Enterprise recovery - Implementation

Prerequisites

Activity codes

The following activity codes (sorted by type) may have an impact on the way the function operates :

 PHY : Physical assets

Miscellaneous prerequisites

Before launching the import of data extracted from Abel Enterprise, some verifications, actions or setup of parameter values must be done in Sage X3.

This includes:

• creating the mandatory ledger: company, financial and geographic sites, contexts and plans,
• setting up the values of certain parameters,
• verifying that the parameters are equivalent between Abel Enterprise and Sage X3.

Verifications

• Verify the format of the ADI data type.
   
  In the case where non-alphanumeric characters (-, /, ...) are present in the imported data, the data type format must be set to: 20X and not 20B for these characters to be validated.
   
• From the Recovery screen, launch the Audit of the miscellaneous tables which can be subject to an update during the recovery process in order to check their length. The list of the tables concerned and their length is displayed in a log file. The user can thus compare these lengths to those of the tables extracted from Abel Enterprise (Volumetric control, Ledger chapter - ER01 code).
   The length of the miscellaneous table 537 - Category must always be from 1 to 12.
   
  The update of a table length is carried out in the Miscellaneous table definition function (Development / Data dictionary menu). Once the modification is carried out, Save and Validate.
   
• Lease contracts and concession contracts cannot be imported. When they are managed, they MUST have been created in Sage X3 before the recovery.
  It is then necessary to perform, in the FASAE template, a manual load of: 
   
  Lease contracts
   
  --> line 82 Lease contract reference Funding, with the field: LEAREF
  --> line 83 - Original lease contract, with the field: LEAREFORI
   
  Concession contracts
  
  --> line 84 - Concession contract, with the field: CCNREF

Parameter values

The values of the following parameters are to be checked:

AAS Chapter - FAS Group

• PRVSITUPD - Modification of the previous situation
   
  This parameter must be set to: Yes, in order to authorize the recovery of totals and accounting allocation dates prior to the fiscal year.

AAS Chapter - IMP Group

• REPDPRCUM - Depreciation total recovery
   
  This parameter must be set to: Yes, in order to authorize the recovery of depreciation totals. These amounts will be forced and not re-calculated by Sage X3.
   
• REPENDDPE - FY depreciation charge recovery
    
  This parameter must be set to: No, in order not to import fiscal year depreciation charges.
   
• AEPLNL1 to AEPLNL8 - Free plan 1 to 8 (Abel Enterprise)
     
  These parameters are used to match up the plan codes of Abel Enterprise and those of Sage X3.
  
• AEAXE1 to AEAXE4 - Dimension type 1 to 4 (Abel Enterprise)
   
  These parameters are used to match up the analytical dimension type codes of Abel Enterprise and those of Sage X3.
  
• AESCT1 and AESCT2 - Sector 1 and 2 (Abel Enterprise)
   
  These parameters are used to match up the IAS geographic/activity dimension type codes of Abel Enterprise and those of Sage X3.
   
• DISAFAS - Import of "inactive" assets
   
  The value of this parameter is to be checked.

Ledger and organizational information

The following ledger must always be created before import:

• Company
• Financial and geographic sites
• Contexts and plans
   
   The dates of the current period must be the same in Abel Enterprise and Sage X3.

Organizational Information

The fields of the Abel Enterprise column here above are defined by default to load the fields of the Sage X3 column.

In order to modify this setup (e.g. if the Abel Enterprise Site section must load the Financial Site section of Sage X3), it is recommended to:
 
- either modify the export template by changing the names of the sections to export (see below),
- or modify the import template by changing the names of the sections to load,
- or else create a transcoding table (see below).

 In Sage X3:
- A financial site is always a geographic site.
- A site can only be a geographic site, therefore, it must be attached to a financial site.

Here are some example of setup combinations (the Financial Site section of Abel Enterprise being optional or managed in another section):

Heading: Company

Heading: Site / Financial site

Heading: Site / Geographic site

Specificities linked to the book vs. tax depreciation

Data structure variance between Abel Enterprise and Sage X3 as far as book vs. tax depreciation is concerned:

• Abel Enterprise:
  The book vs. tax depreciation is stored in the BCO table header, except for the 4 recurring total sections (book vs. tax provision, re-integration provision, book vs. tax recovery, re-integration recovery) which are stored in the Fiscal plan of the AMT table.

In order to properly migrate theses data, the output file of Abel Enterprise considers and respects the Sage X3 data structure, which is:

• the book vs. tax depreciation is stored in the Accounting plan of the DEPREC table,
• the fiscal re-integration is stored in the Fiscal plan of the DEPREC table.

Matching setup between Abel Enterprise and Sage X3.

Transcoding tables

Generally, the External code corresponds to the data of Abel Enterprise and the Local code corresponds to those of Sage X3.
For the sections for which a transcoding process is written in the import processing (all internal tables for instance table I08 - Issue type), it is also possible to define a transcoding table; in this case, Local and External codes are Enterprise data.

Example

In Abel Enterprise, the user has defined an issue type: S - "Export Sales".
In order to recover the issued assets having the issue type: S - Export Sales, one must:

• Create a transcoding table (example: Table 96 - Abel issue type) and enter local and external codes:
  Local code: 1 (Sales)
  External code: S (New issue type "Export Sales")
   
• Modify the FASAE template and assign to the field *81 - Issue type, the table created for this purpose (table 96), in the column: Table number.
  During the import, the External code: S becomes the External code: 1 which will be recoded into the Local code: 1 - Sales.
  
  

Automatic recoding of local menus

Tables used

No table is used by this function.