Migration Abel X3 v.140

This function is common to the migration to Sage X3 V7: 

• of the product Sage X3 Fixed Assets V5, described in an appendix document: Migration Sage X3 Fixed Assets   
   
• of the product AbelX3 V140, described in this documentation:

The migration of the Sage X3 Fixed Assets product to the ERP v.7 is carried out by means of a specific processing that is different from the one used when migrating an X3 product (where the folder is imported via the console, then validated in the new solution). The purpose is not to migrate the whole Abel X3 v.140 folder but to insert the Fixed Assets and their various parameters into a folder containing other modules, especially the Financials module having some common parameters with the Fixed Assets.

The aim of this processing is to read the tables of the v.140 folder described here below by means of a link, and to create and update the corresponding tables in the V7 destination folder. It is activated in the V7 destination folder by means of this function, used to choose the V.140 folder and the various execution parameters: choice of the companies, allocation of the analytical dimension types, etc.

  For performance reasons, the reading is conducted without a lock being applied. It is therefore imperative that no user work during the migration.

Prerequisites

Activity codes

The following activity codes (sorted by type) influence the behavior of the function:

• ANA: Nb of analytical dimension types

Miscellaneous prerequisites

Abel X3 v.140 folder:

• It must belong to patch list 21 at a minimum.
• It must be an application folder.

In this application folder, the following conditions must be met:

• No actual calculation must have been carried out in the current periods (or on the current fiscal year if the fiscal year is not subdivided in periods) of the contexts of the company.
• The free context for the grant depreciation must have the same currency, the same subdivisions and the same current period as the fiscal and accounting context. During the migration, the free context used for this depreciation will be automatically moved in the fiscal and accounting context.
• The events must all be posted.
• During the migration, it is possible to request in the fiscal and accounting context, that a plan belonging to a context other than the accounting and tax context be moved. It is for this reason necessary that the FY/period breakdown of the current period and the currency be identical in the two contexts.
• If, in v.140, the UPs are managed using several plans in different contexts, it must be taken into account that these plans move to the Accounting and fiscal context during the migration. Indeed, in v.7., only one context can manage UPs.

X3 V7 folder:

• It must not be a root folder.

In this application folder, it is necessary to:

• Have a "miscellaneous" link defined to the v.140 application folder.
   Refer to the documentation on the setup of Folders.
• Have the Fixed Assets module activated, and to have validated this folder.
• Have defined the receiving company and its sites. The Account Core Model of this company will have to be compatible with the contexts of the company of origin. In other words, an IAS ledger needs to exist in the Account Core Model of the receiving company, whenever at least one context of the company of origin contains at least an IAS/IFRS plan.
• No context should be defined for the processed companies. In other words, a company can only be migrated once.This control is carried out upon execution of the processing.
• The Fixed Assets activity codes (excluding the sizing activity codes) must have the same values as those of the folder of origin. This control is carried out upon processing execution.

Journal postings 

If the migration of journal postings is required, it is advised to define a specific journal type that will be recovered in the v.7 folder. This type of entry will be used to:
- easily find the entries originating from the migration,
- avoid duplicates, especially when the numbering of document type in the v.7 folder is prior to the v.140 folder numbering.

Dimension types

Before performing the migration processing, the correspondence between the dimension types of the v.140 (numbered from 1 to 9) and those of the ledgers of the Account Core Models for the v.7 needs to be set up for each migrated company.

Activity sectors

The SCT1 and SCT2 economic and geographic activity sectors become dimension types in V7. When submitting the processing, it is therefore necessary to specify the dimension types onto which this information should be copied, for each migrated company.

Screen management

Entry screen

Description of the table migration

Principles

The basic principle for each table to process is simple: through the link, the processing opens the source table, as well as the destination table in the local folder. Then it loops onto the records (by company or not , depending on the cases) of the source table. Finally it creates or updates the records in the destination table.

The translatable texts (ATEXTRA table) are copied for each table in all the languages available in the destination folder.

List of the concerned tables

The grid below lists all the tables concerned by the migration.

• When no link between the Sage X3 Fixed Assets folder and a Sage X3 accounting folder has been noticed, all the tables listed are migrated (checkbox "Reuse of the ledger common to X3" activated by default).
   
• When no link has been noticed, only the tables including a X in the grid are migrated. The others, related to the objects shared with X3, are not recovered by the migration processing (the checkbox "Reuse of the ledger common to X3" is automatically de-activated).
   
• The following columns are used to find the tables that can be subjected to a common setup to all the companies and those which setup can be specified by company.
  The choice to copy or not the common setup is carried out on the launch screen by activating the checkbox "Copy of the common setup".

(1) See below the correspondence of miscellaneous tables v. 140/v7.
(2) Only in update:
(3) If the activity code CCN - Concessions is to Yes.
(4) If the activity code PHY - Physical elements is to Yes.
(5) If the activity code LEA - Financial lease contract is to Yes.
(6) If the activity code GRT - Grant is to Yes.
(7) Event tables described in the miscellaneous table 952 of the Abel X3 v. 140 folder.

Correspondence of v.140/v.7 miscellaneous tables

Particular cases - Reprocessing information

it is necessary to reprocess some tables, in addition to the mere copy.

Dimension types, activity sectors

• For the business objects managing this information, the migration processing assigns the values of the v.140 dimension types and the activity sectors SCT1 and SCT2 to the v.7 dimension types, according to the setup carried out by the user on the submission screen of the migration process.

Accounts

• For each Abel X3 v.140 accounting code, the migration processing will create a Sage X3 v.7 account for the Chart of Accounts of the main Social ledger of the company account code model and for the Chart of Accounts of the main IAS ledger if the latter is defined for the company account core model.
• If the account is classified 2, fields FLGABL (account tracked in Fixed Assets) and FLGEXPCRE (expense creation) are initialized to Yes. Otherwise, these fields are initialized to No.
• If the account does exist, it is not modified.

Accounting codes

• For each Abel X3 v.140 accounting code, the migration processing will create an ERP v.7 accounting code for the Chart of Accounts of the main social ledger of the company account code model and for the Chart of Accounts of the main IAS ledger if the latter is defined for the company account core model.
• If the accounting code exists, it is modified.
• The correspondence between account lines occurs as follows:

Social ledger

IAS ledger

Setup of the flows

• For each setup of the v.140 flows, the migration processing will create an ERP V.7 flow setup for the Chart of Accounts of the main social ledger of the company account code model and for the Chart of Accounts of the main IAS ledger if the latter is defined for the company account core model.

BP

• If a BP already exists in the ERP V7, it is not modified.

Product

• If an item already exists in the ERP V.7, the FLGFAS "Fixed Asset" is updated with the value of this field in Abel X3 v.140.
• In creation and update modes, the group code is assigned for the ERP V7 legislation.

Sites

• The sites are updated with the information: Inventory (IVYFLG) andInventory Site (IVYFCY).

Subsidies

• The V.7 grants no longer mention the various accounts but an accounting code. When migrating the grants, the processing searches in the ERP V.7 for an accounting code linked to the various accounts of the v.140 grant. If such an accounting code is found, it is assigned to the V.7 grant. Otherwise, an accounting code is created with the accounts of the v.140 grant and it is assigned to the V.7 grant.

Posting types

• The document and journal types are fed from the automatic journal if these fields are not formulas.
  The formulas concerning the CCE and DIE fields are transformed by the migration tool to adapt to the V7 account core model.
  CCE field: funcGENEVE.GET_CCE_DAT([F:CPT]PERENDDAT,"[F:OBJ]","","",<PLAN>,[F:TCD]DIE(<NUM AXE>))
  DIE field: func GENEVE.GET_DIE_BY_PLN([F:OBJ]CPY,<PLAN>,<NUM AXE>)

Post-requisites

 Following the migration, it is imperative to perform the following controls:

Posting the Fixed Assets Transactions

Development/Utilities/Dictionary/Transaction generation

• After copy of the common setup: launch, in the migrated folder, the transaction validation: FIX - Fixed assets transactions, in order to make operational the entry transactions migrated from the source folder.
  This transaction is available after setting the Fixed Assets module to Yes in this screen.

Account Core Model, Ledger and Contexts

Setup/Organizational structure/Account core models
Setup/Fixed assets/Depreciation contexts

• Check the consistency between the various contexts (and depreciation plans) and the account core model.

Automatic journals

Parameters/Financials/Accounting Interface/Automatic Journals

• Make sure that the migrated automatic journals are compliant with the reference documents; the reference automatic journals having been modified between Abel X3 v.140 and the V.7 Fixed Assets module.
   
  Fixed Assets Module

Financial module

Journal types

Parameters/Financials/Document types

• Ensure the compliance of the migrated elements with the reference elements to be found in the root folder:
  - Actual document types: IMR12, IMR2 and IMR3
  - Simulation document types: IMS12 and IMS3
  
  Since the document types used have been modified between Abel X3 and the V7 Fixed Assets module, it is important to make sure that they are going to be used for the right ledgers (propagation rules of the ledgers). 

Fixed Assets entry types

Parameters/Fixed Assets/Accounting entry types

• Since the types of reference entries have been completely modified between the Abel X3 v. 140 version and Sage X3, they are only mentioned as extra information and cannot work as they are.
  During the migration, they are renamed as follows: V14 + company code + plan no. + entry type. 
  
  The user can check or even adapt the entry types delivered as standard in Sage X3.

Error messages

All error messages are generic error messages.