Sage X3 HR & Payroll: functional pre/postrequisites for a folder migration t 

The migration of data and setups contained in the migrated folder requires two interventions: an intervention before (prerequisites) and an intervention after (postrequisites) the migration process carried out automatically when the folder migrated to Update 9 (U9) is validated for the first time.

Prerequisites to the migration process

The migration prerequisites of a folder are specified here below. Generally speaking, the first step, which is highly recommended, is to check that the data to migrate is consistent.. In actual fact, in the case of a folder associated with numerous transactions, and which may have undergone maintenance operations, some data may no longer be consistent with the others (especially in the presence of specific developments).

This operation will detect any problems concerning data that may generate errors during the migration procedure itself, which would make it necessary to restart the procedure.

Before starting the migration of the folder, it is necessary to ensure that all the temporary accounting entries generated in the temporary tables (GACCTMP, GACCTMPD, GACCTMPA) have been processed. These tables are reset to zero during the migration of the folder.

Account core model parameter (MIGGCM) (only applies to the migration of a V6 to a U9 version)

The account core model parameter (chapter TC, group MIG) must be entered in the parent folder before starting the migration. The choice of this parameter value is very important because it determines the organization of the accounting structure in the migrated folder.

The accounting data is structured in a different way if the selected account core model is a single-ledger or a multi-ledger model.

  • If the selected account core model is a multi-ledger model (for example FRA in the French reference folder, POR for Portugal), the accounting accounts are migrated to several ledgers. One of these ledgers will be an exclusively general ledger and the other ledger will be an exclusively analytical ledger. The analytical natures are migrated to analytical accounts.
  • If the selected account core model is a single-ledger model (for example FRM in the French reference folder, PO2 for Portugal), the accounting accounts are migrated to a single ledger that can be used both as a general and an analytical ledger. Caution, in this case, the analytical data is used but not the natures.

For more information concerning the accounting structure in Sage X3 HR & Payroll, see the Accounting module How to guide (How to tab in the Online help center).

When Sage X3 is used, the account core model chosen as the parameter value must be consistent with the structure used in X3.

Irrespective of the account core model chosen as parameter before the migration is started, the code of the model in the destination folder is identical to the currency code of the folder. For example, EUR for France, EUR for Portugal. It is possible to change this code after the migration of the folder, using the key change utility.

Folder localization

The migration of the folder requires the prior activation of the localization which will be used. This setting must be made in the folder record.

For example:
  • For a French folder:
    • Activate the KFR localization activity code
    • Set the FRA language
    • Set the FRA legislation
  • For a Portuguese folder:
    • Activate the KPO localization activity code
    • Set the POR language
    • Set the POR legislation
  • For a South-African folder:
    • Activate the KSA localization activity code
    • Set the ENG language
    • Set the ZAF legislation

Reports

The BULODPAY and CPTODPAY reports used in V6 should no longer be used in U9. Use the SIMBULODPAY and SIMCPTODPAY reports instead.

Postrequisites to the migration process

Accounting structure (only applies to the migration of a V6 to a U9 version)

The structure of the accounting data has been changed. The account core model, the ledgers, the charts of accounts and the analytical dimension types have been coded. This new structure is based on the elements in the reference folder and the MIGGCM parameter value entered before the migration.

It is possible to change the codes using the key change utility. For example, this allows the codes between Sage X3 HR & Payroll and Sage X3 to be aligned. The key modification is available for each level of the structure.

Business processes (only applies to the migration of a V6 to a U9 version)

The processes used in version 6 must be revalidated using the Process recoding function (ARECOPRO). This validation is necessary to make the processes consistent with U9.

The process validation must be carried out:
• after each folder validation,
• after each copy of a process from a folder to another.

For all the gadgets created in Sage X3 HR & Payroll V6, it is necessary to:
• create a menu item to select the thumbnail in the home pages,
• change all formulas which use global variables to see the data (queries, statistics etc. ).

Financials

Automatic journals

Some automatic journals for version 6 have been modified in U9 (no modification between V7 and U9).

It is therefore necessary to launch the automatic journal comparison function (CMPGAU) to compare the migrated folder with the Sage X3 folder.

Fields that indicate a file path

The new volume management method (from version 7 onwards) in U9 and the use of a web browser rather than a fat client implies that the fields that specify a file generation path now function differently. The parameter values and the fields of some functions are impacted.

Parameters that contain a path are now only used when the destination is of Server type. They must contain a path relating to the selected volume (or just a volume), expressed with the appropriate syntax.

These parameters should therefore be updated so that they contain the volumes or relative paths, in compliance with the new syntax.