Kontakt

Ansicht
Dokumentation

ABENMESH_DELETE - MESH DELETE

ABENMESH_DELETE - MESH DELETE

Addresses (Business Address Services)   BAL Application Log Documentation  
This documentation is copyright by SAP AG.
SAP E-Book

DELETE mesh_path

DELETE ${ TABLE mesh_path table_key $}
     $| ${ mesh_path $}.

Variants:

1. DELETE TABLE mesh_path table_key.

2. DELETE mesh_path.

Effect

Deletes one or more lines from the last path node of a mesh path mesh_path.

Note

It should be noted that the addition TABLE is highly significant for directly specified internal tables, as in DELETE, and distinguishes different variants of statements from each other.

Variant 1

DELETE TABLE mesh_path table_key.


Effect

Deletes exactly one line from the follow-on node of an initial mesh association. In this variant, no path extensions can be specified, and the square brackets of the initial mesh association cannot contain any additional conditions. The line to be modified is determined using the table key:

  • If the ON condition of the mesh association used covers all key fields of the table key it uses, the line to be deleted is determined using the result of the mesh path. Here, only those fields of the ON condition are respected that are also key fields.
  • If the ON condition of the mesh association used does not cover the key fields of the table key it uses, the missing key fields must be specified in the addition table_key and these are combined with the result of the mesh path. The same can be specified for table_key as in the statement DELETE TABLE itab with a directly specified internal table:
  • WITH TABLE KEY must be used to specify all key fields not covered by the ON condition. No key fields can be specified that are already covered by the ON condition. Furthermore, all fields of the follow-on node used in the ON condition must exist in the table key used by the mesh association.

  • Only those components are taken from a work area specified using FROM wa that match the non-covered key fields. All other components are ignored. The work area wa must be compatible with the line type of the last path node.

If a table key is specified in table_key using keyname COMPONENTS or USING keyname, this key overrides any USING KEY additions specified in the definition of the mesh association. The line is deleted with respect to this table key and its key fields must be completely covered.

The line is deleted in accordance with the rules of DELETE. If the follow-on node contains multiple lines that match the specified key, the first line found is deleted. If the line to be deleted is not found, nothing is deleted.

The return code sy-subrc is set in the same way as in the corresponding statement DELETE itab.

Notes

  • If the ON condition covers all key fields, the addition WITH TABLE KEY cannot be specified. The addition FROM wa can be specified, but is ignored.
  • If no explicit table key is specified in the definition of the ON condition and in the statement DELETE TABLE mesh_path, the line is deleted with respect to the primary table key.
  • Columns of the follow-on node that are listed in the ON condition but are not part of the table key used are either forbidden or ignored in this variant. This means that the line to be deleted cannot be determined beyond the bounds of the table key.

Deleting Single Lines in Mesh Paths

Variant 2

DELETE mesh_path.


Effect

Deletes multiple lines from the last path node of a mesh path mesh_path. All lines from the last path node described by the result of the mesh path are deleted. An additional condition can be specified in the square brackets [ ... ] of each mesh association of the mesh path using the additions USING KEY and WHERE log_exp.

Deleting Multiple Lines in Mesh Paths






SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 6945 Date: 20240418 Time: 041148     sap01-206 ( 103 ms )