SAP IUMD TARGET ABAP Statements



Get Example source ABAP code based on a different SAP table
  



INSERT, UPDATE, MODIFY, DELETE, target

ABAP_SYNTAX
... dbtab
BEGIN_SECTION VERSION 5 OUT $|view$|(target_syntax)
END_SECTION VERSION 5 OUT $[client_handling$] ...

ABAP_ALTERNATIVES:
1 ... dbtab$|view
BEGIN_SECTION VERSION 5 OUT
2 ... (target_syntax)
END_SECTION VERSION 5 OUT

What does it do?
In the modifying AB-SQL statements INSERT , UPDATE, MODIFY , and DELETE, these elements specify statically or dynamically which DDIC database table
BEGIN_SECTION VERSION 5 OUT or DDIC view
END_SECTION VERSION 5 OUT is accessed. Optional additions client_handling control client handling.
BEGIN_SECTION VERSION 5 OUT Only views whose key fields are located together at the beginning of the view can be accessed.
END_SECTION VERSION 5 OUT



Latest notes:
NON_V5_HINTS
Write access to DDIC database tables or DDIC table views with replacement objects is still performed on the DDIC database table or the DDIC view and produce a syntax warning.
ABAP_HINT_END

ABAP Alternative 1 ... dbtab$|view

What does it do?
dbtab can be a DDIC database table defined in the ABAP Dictionary
BEGIN_SECTION VERSION 5 OUT and view can be a DDIC table view
END_SECTION VERSION 5 OUT
BEGIN_SECTION VERSION 5 OUT .
Only DDIC table views that refer to a single DDIC database table and whose status in the ABAP Dictionary allows changes can be specified. No DDIC external views or CDS entities can be specified.
END_SECTION VERSION 5 OUT



Latest notes: