Functional prerequisites and postrequisites for the upgrade of a folder

The upgrade of a folder (data and settings) requires two interventions:

Prerequisites to the upgrade process

Before starting the upgrade of a folder:

  1. Make sure the data to upgrade is consistent, especially for folders that had many movements (including specific developments) and that went through maintenance operations.
    The Consistency Verification function (Development > Utilities > Verifications > Data > Consistencies) helps detect data that can generate errors during the upgrade procedure itself to avoid having to restart the procedure.
  2. Make sure all the temporary accounting entries generated in the temporary tables (GACCTMP, GACCTMPD, GACCTMPA) have been processed.
    These tables are reset to zero during the upgrade of the folder.

Account core model parameter (MIGGCM)

Only applies to the upgrade from V6 to U9.

Enter the account core model parameter (chapter TC, group MIG) in the parent folder before starting the upgrade. The value of this parameter determines the organization of the accounting structure in the upgraded folder.

Refer to the Accounting module how-to guide in the How to tab of the online help center for more information regarding the accounting structure in Sage X3.

Caution: If you also use Sage X3, make sure you select an account core model that is consistent with the structure used in Sage X3.

Note: The code of the model in the destination folder is identical to the currency code of the folder, regardless of the account core model chosen before the upgrade. For example, it is "EUR" for France and Portugal. You can change this code after the upgrade of the folder using the key change utility.

Folder localization

Before the upgrade of a folder, you must first activate the localization that will be used. This is done directly from the folder record (Setup > Organizational structure > Folders).

For example:

  1. For a French folder:
    1. Activate the "KFR" localization activity code.
    2. Set the "FRA" language.
    3. Set the "FRA" legislation.

  2. For a Portuguese folder:

    1. Activate the "KPO" localization activity code.
    2. Set the "POR" language.
    3. Set the "POR" legislation.

  3. For a South-African folder:

    1. Activate the "KSA" localization activity code.
    2. Set the "ENG" language.
    3. 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 upgrade process

Accounting structure

Only applies to the upgrade from V6 to U9.

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 on the value of the MIGGCM parameter that was entered before the upgrade.

You can change the codes using the key change utility, for example to ensure that the codes are aligned in Sage X3 and in Sage X3. You can edit the key for each level of the structure.

Business processes

Only applies to the upgrade from V6 to U9.

The processes used in V6 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:

For all the gadgets created in Sage X3 V6, you have to:

Financials

Automatic journals

Some of the V6 automatic journals have been modified in U9. It is therefore necessary to launch the automatic journal comparison function (CMPGAU) to compare the upgraded folder with the Sage X3 folder.

Fields that indicate a file path

Because of the new volume management method in U9, as well as the use of a web browser rather than a fat client, the fields that specify a file generation path now function differently. The parameter values and the fields of some functions are impacted.

Parameters containing a path are now only used with the Server type destination. 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.