ABAP Keyword Documentation → ABAP − Reference → Processing External Data → ABAP Database Access → ABAP SQL
ABAP SQL - Write Accesses
Write accesses include inserting, modifying, and deleting content in database tables. All write accesses can be made as individual accesses or as mass access. If multiple rows of a database table are to be changed, mass access using internal tables generally gives better performance than individual accesses.
Other versions: 7.31 | 7.40 | 7.54
Notes
- In the case of writes, attention must always be paid to data consistency. The LUW concept is designed for this purpose. In application programs of an AS ABAP, the implicit database LUWs are normally not sufficient for consistent data storage. Instead, explicit SAP LUWs need to be programmed, which normally contain multiple database LUWs.
- When making writes to a database table for which a database cursor is open in a
SELECTloop or opened by using OPEN CURSOR, the results set is database-specific and undefined. Avoid this kind of parallel access if possible.
- Write access to tables or classic views with replacement objects is still performed on the database table or the classic view and lead to a syntax warning.
- Once a global temporary table is filled using ABAP SQL, this table must be emptied again explicitly before the next implicit
database commit using
the ABAP SQL statement
DELETE FROMwithoutWHEREor using an explicit database commit or database rollback. If not, the runtime error COMMIT_GTT_ERROR is produced.
Continue
INSERT, UPDATE, MODIFY, DELETE - target
INSERT, UPDATE, MODIFY dbtab - LOB Handles