Execution: Instead of database changes for texts in other languages
This event occurs when the function 'Save' runs. A different logic from in the standard can now run, for example to also change hidden maintained tables in the database.
The standard routine VIM_TEXTTAB_DB_UPDATE can be a template for the realization of the individual routine.
The following global data are available:
Internal Table <VIM_TEXTTAB> : The text data must be handled differently in the individual routine, depending on the constant value of the processing flag
ORIGINAL : No action required
NEUER_EINTRAG : Put the entry in the database and set the processing flag to ORIGINAL.
NEUER_GELOESCHT : Delete the entry from the internal table. No database operation is required as the new entry does not yet exist there.
GELOESCHT : Delete the entry from the internal table. It was already deleted from the database in the entity save routine, so no user database operation is required.
AENDERN : The entry must be changed in the database. The processing flag is set to ORIGINAL.
UPDATE_GELOESCHT : Delete the entry from the internal table. It was already deleted from the database in the entity save routine, so no user database operation is required.
If the internal table <VIM_TEXTTAB> has been changed, the following statement must be at the end of the routine: MODIFY VIM_TEXTTAB_CONTAINER INDEX VIM_TEXTTAB_CONTAINER_INDEX .