
As described above, the text memory is empty after the final call of the function module COMMIT_TEXT. For a new read access, the system uses the text file. f the update task is slow, the system may read the old text contents.
However, some applications must continue processing texts with the same transaction after a COMMIT_TEXT, for example, to print a document. In this case, you can use the parameter KEEP of the function module COMMIT_TEXT to keep the texts in the text memory. The system flags them to indicate that they have been sent to the update task. If you call COMMIT_TEXT again, the flagged texts are not passed to the update task, unless they have been changed again in the meantime.