Ansicht
Dokumentation
ABAPDELETE_CLUSTER - DELETE CLUSTER
General Data in Customer Master General Data in Customer MasterThis documentation is copyright by SAP AG.
DELETE FROM
DELETE FROM ${ ${MEMORY ID id$}
$| ${DATABASE dbtab(ar) $[CLIENT cl$] ID id$}
$| ${SHARED MEMORY dbtab(ar) $[CLIENT cl$] ID id$}
$| ${SHARED BUFFER dbtab(ar) $[CLIENT cl$] ID id$} $}.
Effect
This statement deletes a data cluster stored in the
ABAP memory, in a database table, or in a
cross-transaction application buffer of the current
using the statement
EXPORT. The data cluster is
identified by its ID id and, except in the case of the ABAP memory, by the name of a database
table dbtab, a range ar, and an optional client cl. The same rules apply to dbtab,
ar, cl, and id as to accessing the appropriate repository with the IMPORT statement.
System Fields
| sy-subrc | Meaning |
| 0 | The specified data cluster was found and deleted. |
| 4 | The specified data cluster was not found. |
Notes
- See also Classes for Data Clusters.
- Since each client represents a self-contained unit, the addition CLIENT should not be used in application programs.
Example
In this example, two fields are written to a data cluster in an application buffer of the current , extracted, and then deleted. Accessing the same data cluster again sets sy-subrc to 4.
Exceptions
Catchable Exceptions
- Cause: SQL error in deletion from the database.
Runtime Error: DBIF_...
Non-Catchable Exceptions
- Cause: Error when deleting in cross-transaction application buffer
Runtime Error: DELETE_BUFFER_FAILED
Runtime Error: DELETE_BUFFER_EXTERNAL_ERROR
Runtime Error: DELETE_BUFFER_INTERNAL_ERROR
Runtime Error: DELETE_BUFFER_KEY_NOT_FOUND
SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up ABAP Short Reference
This documentation is copyright by SAP AG.
Length: 4235 Date: 20240423 Time: 233820 sap01-206 ( 46 ms )
