Refer to documentation Implementation
The screen is presented in the form of a grid with several lines: each line corresponds to a key change definition.
If the key is made up of two parts, the two key parts are entered, but the key part to recode is indicated first. For instance, if the user decides to modify the key of a miscellaneous table, the table number is the second entered, and the code in the table, which will be recoded, is entered first.
Fields
The following fields are present on this tab :
Block number 1
| Code identifying the current record. |
| [object Object] |
| Select this check box to activate the current record. Disabled records keep their content and setup but cannot be used (by recalling their code) on other records (documents, settings ...), or for mass processes. The authorizations to a given function can prohibit the creation of an active record. In this case, the check box is disabled by default. It can only be modified by an authorized user or through a signature Workflow. |
| Object code concerned by the recoding. |
| If the key of the object has a single part, this field is empty. Otherwise, the value of the second part of the object key is the element to be modified. |
| This is the key value of the object to be modified |
| Enter the description of the relevant record. This long description is used as a title in screens and reports. |
| This is the new value of the key which must replace the former value 'Identifier 1'. |
Close
Action icon
This function is used to load in the grid all the other keys of the table corresponding to the current line. For instance, to recode all the codes of a miscellaneous table, enter the first code, then return to the line in "entry" mode and, with a right click, request the loading: all the other lines of the miscellaneous table in question will then be loaded, and the last step will be to define the new codes displayed next to them.
This function is used to pre-load a list of the lines to rename by indicating the corresponding object and a filter criterion.
Close
In some cases, codes are used in the form of a constant in calculation formulas. Automatic journals are the most frequent example. In order to enable the recoding utility to recognize keys written in the form of constants in formulas, a particular technique can be used. Instead of entering the key associated with an object (for example JOU) in the form of a constant (for example "FRVEN"), the following formula will be used in the automatic journal:
Func ACHANGE.C("FRVEN","JOU")
The ACHANGE.C function systematically returns the value of the first parameter ("FRVEN" in this example); typing this formula is thus equivalent to entering the "FRVEN" constant. However such formulas are detected by the recoding function. That is why, if a line exists for the JOU object, which associates to the FRVEN code a new VEN code, the recoding function will replace the formula with
Func ACHANGE.C("VEN","JOU")
Note that, in the case of a two-part table, the formula should be entered in the following form: "CLE1~CLE2". For instance, in order to rename the FRCHQ code into CHQ in miscellaneous table number 306, the following formula must be used:
Func ACHANGE.C("306~FRCHQ","ADI")
The following fields are included on the window opened through this button : Block number 1
Block number 2
Close This button is used to copy the record definition from or to another folder. |