It is possible to create, using the system transactions management, a transaction code that is used to carry out a mass update (modification, deletion of information in the database), after an optional phase of associated setup entry. Described below is the function for carrying out the execution of these transactions.

Legal notice

This type of function is a development function whose use is probibitted in a standard use framework.

Any legal consequences arising from the use of development tools on databases containing data which it is prohibitted by law to modify will be under the full responsibility of the customer. For further information, refer to the corresponding annex.

Indeed, the setup function of system transactions enables a mass update of the data of any table. The coherence rules linked with the application are not controlled; it is a maintenance tool.

It is therefore advisable to:

  • be extremely cautious when creating such transactions
  • only give access to this function to certain users.
  • use access codes to protect each system transaction to correctly filter those that could be accessible to certain users.
  • In addition, if the ASIGMNTsetup if set to Yes, a validation screen will be displayed and active after a second entry of the user's password and a reason code.

Prerequisite

SEEREFERTTO Refer to documentation Implementation

Screen management

Entry screen

The opening screen is used to enter the code of the system transaction, along with the linked setups. Once the code has been entered, the function is launched, either in test or in real mode.

A trace is displayed when the execution of the function is completed: it gives the list of the modified lines.

Block number 1

Code (field COD)

This code identifies the system transaction to be launched.

field DES

Title associated with the previous code.

Block number 2

Test mode (field TEST)

If this box is checked, the transaction is carried out without any table being updated, and the trace mentions which data would be updated if the process were launched in real mode.

It is possible to set a maximum number of transactions to be processed.
Number of transactions (field NOMBRE)

In test mode, this field limits the number of processed table lines.

Grid

Variable (field VARDES)

Name of each variable which can be entered as system transaction parameter.

Value (field VALEUR)

It defines the values associated with the transaction parameters when said transaction is being carried out.

Entry screen

Batch task

This function can be run in batch mode. The standard task AMIEXE is provided for that purpose.

Error messages

The only error messages are the generic ones.

Tables used

SEEREFERTTO Refer to documentation Implementation