In that case, refer to the technical procedure described in the Easy upgrade guide documentation (documentation only available in English).
In case of migration of a folder from one major release to another, the following stages must be complied with:
The rest of the documentation describes all the steps.
Pre-migration stages are launched in the source environment and they can be spread over a period of time, before the actual migration. In fact, they do not require the operation of Sage X3 HR & Payroll to be stopped.
The stages are the following:
This stage corresponds to the beginning of the transfer to the next version. At this stage, the operation of the solution must be stopped: it will resume when the migration is completed.
This stage is sub-divided into 4 phases:
1. Extraction of the data from the folder to be migrated:
2. Copy of the files of the folder to be migrated to the U9 solution,
3. Creation of a copy folder of the folder tree structure in the new environment of version 6 or 7, and import of the exported data into the new environment,
4. Creation of the folder record in the U9 environment. If the import is carried out via the console, the folder record is created automatically. On the other hand, if the import has been carried out via database tools, the folder record will have to be created manually after the import is completed.
These various stages can be combined into a single one. For that purpose, use theremote import wizard available in the SAFE X3 configuration console.
If the procedure must be relaunched from the import of the data into the migration folder, you must launch the TRTMIGDEL processing to clear the tables storing the migration status.
If the console import function is used, the procedure is as follows:
Before revalidating the folders, the activity code value must be adjusted in the folder record. Setups are thus in conformity with the license. For example, to implement new functionalities controlled by new activity codes. The modification of the folder record, or its creation, will be carried out by logging to the Supervisor folder. The folder revalidation cannot be triggered without this update. This is reminded by an error message when launching the validation.
Revalidating the folder transforms the structure of the Sage X3 HR & Payroll dictionary, then of the setup tables, then the data tables, of the previous version in order to bring the structure up to the Update 9 level while transferring the data. To revalidate the folder, click the Validation button from folder management or launch the VALDOS task in query management. This performs the supervisor and functional migration of the folder, by running a comparison between the dictionary of the new version and the dictionary of the version to migrate.
If a first migration test is performed on a folder including specific developments and if this migration is likely to stop on an error, setting up by default the dimension of the GTRALIG global variable to 200 (for optimization reasons) does not provide with all the last operations performed just before the migration is stopped.
You must temporarily modify the dimension formula of the GTRALIG global variable with the the value 1. The value 200 must be re-entered following the migration.
Remember to log out and then log on again in order for the value to be taken into account.
The folder revalidation triggers the following stages in the folder to migrate:
This functional migration can be lengthy when the folder is very large. Moreover, some updated tables are potentially independent and, therefore, could be migrated in parallel, thus benefiting from multi-processor architectures to accelerate this phase.
To allow this migration to be scheduled in the best way, it is possible to define a customized migration plan before launching the data validation. This migration plan is described in the Migration procedure function (called from the Supervisor folder). This function is used to define the stages, phases and procedures of the functional and supervisor migration. A migration plan corresponds to the definition of specific migration parameters (impacted folder, number of procedures that can be run in parallel, task sequencing policy, running status). A migration plan is created by recopying all the active elements of the migration procedure. This complete set of procedures is provided as a standard. It allows all the processings carried out by the standard software during the migration phase to be run exhaustively. A short description of these procedures is provided in a dedicated documentation.
It is possible, at this stage, to define specific procedures by writing complementary processings in conformity with the methodology defined in the following annex. These specific procedures will be inserted in a relevant way between the standard procedures.
Once a migration plan has been defined, it is possible to launch it, interrupt it momentarily, resume its execution, and view its progress status.
When a folder is not too large and its migration does not require any particular planning, it is not necessary to create a migration plan. In fact, when there is no migration plan, the folder validation operation will automatically create a migration plan. The code of this migration plan will be the folder code, except if this code already corresponds to a migration plan that does not have the Pending status. If this is the case, the plan is created with a predefined code under the form MIGmmddM##. mmandddare the numbers representing the month and the day of the launching, ## is a sequential number.
However, to customize the migration sequencing options, it is possible to create a migration plan with a code that must correspond to the folder name. This creation will take place in the supervisor folder before launching the folder validation. If there is such a migration plan with the status Pending,it will be used for the functional migration of the folder.
A plan created with a name that is different from the folder to migrate will never be used by the automatic folder validation functions. Such a plan is restricted to a manual launching.
A migration plan is characterized by a folder code and 4 parameters:
If the migration plan is created by default upon folder revalidation, it is created with the following values:
The user can at all times modify these values from the migration plan control function.
The ordered list of the plan procedures is displayed on the screen associated with the migration plan. The plan execution can be globally controlled via specific buttons:
Each plan line materializes a step in the execution, characterized by:
The functional migration can be split through the migration steps. If a procedure linked to a given phase is not completed, the following phases cannot be launched. The phases are linked to the following steps:
One step includes unitary procedures that are organized in phases and ranks.
This phase is manual. It is triggered by the execution of the TRTMIGDEL processing from the processing execution function. Running this phase will delete all the tables with the MIG activity code.
This phase cannot be reversed.Please ensure that the migration processings have been carried out successfully.
Keeping the temporary tables in the folder is compatible with the resumption of normal operations. It is therefore possible to keep these tables on-line for a few weeks of operation. Should any problem occur in the weeks following the migration, it will be possible to have the original data available for comparison or analysis purposes.
As soon as the folder is revalidated, it can be accessed without use restriction (there can be some level of restriction if some postmigration operations have been postponed).
The only remaining task is to check and adapt some functional setups. This aspect is described in the documentation on the functional postrequisites.