The accounting data are structured differently if the selected account core model is a single-ledger or a multi-ledger model.
For more information concerning the accounting structure in HRM V7, see the How to guide entitled "Accounting module" ("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 equal 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.
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.
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. This allows for example the codes between Sage X3 People and Sage X3 to be aligned. The key modification is available for each level of the structure.
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 version 7.
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 People 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. ).
Some automatic journals of version 6 have been modified in version 7.
It is therefore necessary to launch the automatic journal comparison function (CMPGAU) to compare the migrated folder with the Sage X3 folder.
The new volume management method in version 7 and the use of a web browser rather than a fat client implies that the fields that specify a file generation path now follow different rules. 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.