Development > Utilities > Miscellaneous > Database mass update 

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 parameter entry. Described below is the function for carrying out the execution of these transactions.

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

It is therefore advisable to :


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 parameters. Once the code has been entered, the function is launched, either in test or in real mode.

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




The following fields are present on this tab :

Block number 1

  • Code (field COD)

This code identifies the system transaction to be launched.

  • field DES

Title associated to 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.


  • 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.




Batch task

This function can be executed in batch mode. The standard task AMIEXE can execute it.

Error messages

The only error messages are the generic ones.

Tables used

SEEREFERTTO Refer to documentation Implementation