Sage X3 Fixed Assets

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

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

This document does not involve the migration process of the Fixed Assets X3 V5 module to the Sage X3 V7, which belongs to the global migration process of a folder to V7. Refer to the documentation on Sage X3:Functional prerequisites and post-requisites for the migration of a folder to V7
 
 

The migration of the Sage X3 Fixed Assets V5 product to Sage X3 V7 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 Fixed Assets V5 folder but to insert the Fixed Assets and their various parameters into a folder containing other modules, especially the Financials module which has some common parameters with the Fixed Assets.

The aim of this process is to read the tables of the V5 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.5 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.

Prerequisite

Refer to documentation Implementation

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. 5/v. 7.
(2) If the activity code CCN - Concessions is to Yes.
(3) If the activity code KPO - Portuguese localization is to Yes.
(4) Only in update:
(5) If the activity code PHY - Physical elements is to Yes.
(6) If the activity code LEA - Financial lease contract is to Yes.
(7) If the activity code GRT - Grant is to Yes.
(8) Event tables described in the miscellaneous table 952 of the Fixed Assets V5 folder.

Correspondence of v.5/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.5 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 Fixed Assets V5 accounting code, the migration processing will create an X3 V7 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 Fixed Assets V5 accounting code, the migration processing will create an X3 V7 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 Fixed Assets V5 flows, the migration processing will create an ERP V7 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.

A/P - A/R Accounting

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

Product

• If an item already exists in the ERP V7, the FLGFAS "Fixed Asset" is updated with the value of this field in Fixed Assets V5.
• 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 V7 grants no longer mention the various accounts but an accounting code. When migrating the grants, the processing searches in the ERP V7 for an accounting code linked to the various accounts of the V5 grant. If such an accounting code is found, it is assigned to the V7 grant. Otherwise, an accounting code is created with the accounts of the V5 grant and it is assigned to the V7 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 journals; the reference automatic journals having been modified between Sage X3 Fixed Assets V5 and the V7 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 Sage X3 Fixed Assets 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

• Make sure that the migrated elements are compliant with the reference elements; the reference entry types having been modified between Sage X3 Fixed Assets and the V7 Fixed Assets module. 
  In Sage X3 Fixed Assets V5, the provisional posting parameters could be managed at the level of the parameters values (chapter AAS - Fixed Assets, group CPT - Financials); in V7, this information is set up at the level of the Entry type (fields Document type and Journal).
  

Posting of the entry types

Development/Utilities/Dictionary/Transaction generation

• It is imperative to launch the validation of the TPE transaction Accounting entry types in the migrated folders.
  This transaction is available after setting the Fixed Assets module to Yes in this screen.
   

Journal entry transaction

Parameters/General parameters/Parameter values
Parameters/Financials/Journal entry transaction

• Upon generation of the accounting entries, the journal entry transaction code used by default is provided by the SCHSTDC - 'Column entry transaction' parameter value (chapter CPT - Financials, group DEF - Default values). STDCO code is the one used in the reference folder.
  This code can also be specified in the header in the automatic journals. This code is not entered by default in the journals of the reference folder.
  
  Check that there is a journal entry transaction that bears the STDCO code.
  In the absence of a transaction code, an error of type "Non-existent structure" is triggered upon entry generation.
  

Trace level calculation

Parameters/General parameters/Parameter values

• Make sure that the CALTRACE - Calculation log level (chapter AAS - Fixed Assets, group CLC - Calculation) is set to 0.
  A log level that is too high can generate a System error during the depreciation calculation processing.

Error messages

The only error messages are the generic ones.