This function is used to copy some setup from a SAFE X3 folder to another SAFE X3 folder.

Two cases are possible:

  • If the folders are located in the same SAFE X3 solution, the copy takes place directly.
  • If the folders are located in different SAFE X3 solutions, this function generates a patch-type file only. This file will need to be subsequently reintegrated to the destination folder using the Patch integration function.

SEEINFO In case of direct copy, it is not possible to specify a file path, but only the folders of origin and destination.
These two folders will have to be located in the same solution.

SEEREFERTTO To make the setup copy easier, the notion of setup model has been introduced. The creation of a model makes it unnecessary to enter the whole setup each time a copy needs to be made.
This field is mandatory and makes it possible to pre-enter the data grid to copy. However, this grid can be modified and entered before its copy.

Screen management

The entry screen is used to define not only the required processing type (direct copy or creation of a patch file) but also a setup model code. Once this model is entered, it is possible to modify or complete the displayed lines: each line defines the lines to extract or to copy from the concerned setup tables via a data model and additional selection criteria.

Entry screen

Once the entry is validated, the copy is carried out if it was the operation requested. If the creation of a patch was requested, the patch creation function is automatically accessed and all the lines corresponding to the entry are displayed. It is then possible to complete the patch file whose creation was proposed.

Please note that the proposed patch integrates the data model lines (type=AAA) but also the patch of the setup model (type=APH), which creation is not mandatory in the patch in order to view the transferred setups.

Copy type

Copy type (field TYPTRS)

Select the copy type. Two values are available:

  • Copy : The setup is read in the folder of origin and is directly updated in the destination folder.
    The Folder of origin and the Destination folder fields need to be entered.

  • Patch: A patch is generated only once. To recover the setup in the destination folder, the patch must be integrated to this folder.
    The destination file path must be entered.

Copy

Source flr (field DOSORG)
Destination folder (field DOSDES)

Patch

Destination type (field TYPEXP)

Select the destination in the event of patch integration:

  • Client
  • Server

If you select Server, you must indicate the directory.
File name (field VOLFIL)

Setup templates

Template code (field MODPAT)

Identifies the code of the setup model.
Legislation (field CODLEG)

This field is used to select the data to process related to one single legislation.

Grid Data models

Template code (field MODDON)

The data model selected here is used to define the data that will be extracted to be entered or copied in the patch file.

SEEINFO There may be several identical data models within the same setup model.
Selection (field EXPSEL)

A selection formula is entered here, which will be applied on the main table defined in the data model.

This formula can include the variable [L]CODLEG, which is the legislation code entered when launching the copy.
Transaction validation (field TRANSAC)

When the setup data describe the entry transactions, the mere copy of setup data is not enough: It is also necessary that the corresponding transactions are revalidated (i.e.. that the code - processing, screens, windows according to the cases - must be regenerated.) It is triggered when entering here the code of the corresponding setup object.

Error messages

The only error messages are the generic ones.

Tables used

SEEREFERTTO Refer to documentation Implementation