Get Example source ABAP code based on a different SAP table
VERSION 5 IN
AB_SQL - Write Access Write accesses include inserting, modifying, and deleting content in DDIC database tables. All write accesses can be made as individual accesses or as bulk access. If multiple rows of a DDIC database table are to be changed, bulk access using internal tables generally gives better performance than individual accesses.
INSERT
UPDATE
MODIFY
DELETE
Latest notes:
In the case of writes, data consistency must always be ensured. 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 must be programmed, which normally contain multiple database LUWs.
Once a global temporary table is filled using AB_SQL , this table must be emptied again explicitly before the next implicit database commit using the AB-SQL statement DELETE FROM without WHERE or using an explicit database commit or database rollback, otherwise the runtime error COMMIT_GTT_ERROR is produced.
When making writes to a DDIC database table for which a database cursor is opened in a SELECT loop, the result set is database-dependent and undefined. This kind of parallel access should therefore be avoided. NON_V5_HINTS
