SAP NetWeaver AS ABAP Release 752, ©Copyright 2017 SAP AG. All rights reserved.
ABAP - Keyword Documentation → ABAP - Reference → Processing External Data → Data Clusters →
DELETE FROM
Syntax
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
application server
by 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 apply
when 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
Example
In this example, two fields are written to a data cluster in an application buffer of the application server, extracted, and then deleted. Accessing the same data cluster again sets sy-subrc to 4.
DATA: id TYPE c LENGTH 4 VALUE 'TEXT',
text1 TYPE string VALUE 'Tina',
text2 TYPE string VALUE 'Ike'.
EXPORT p1 = text1
p2 = text2 TO SHARED BUFFER demo_indx_blob(XY) ID id.
IMPORT p1 = text2
p2 = text1 FROM SHARED BUFFER demo_indx_blob(XY) ID id.
ASSERT sy-subrc = 0.
DELETE FROM SHARED BUFFER demo_indx_blob(XY) ID id.
IMPORT p1 = text2
p2 = text1 FROM SHARED BUFFER demo_indx_blob(XY) ID id.
ASSERT sy-subrc = 4.
Handleable Exceptions
CX_SY_EXPIMP_DB_SQL_ERROR
Non-Handleable Exceptions