Get Example source ABAP code based on a different SAP table
ARTICLE
Syntax Revisions in Program Calls ABAP Code Snippet ARTICLE
Incorrect Transaction Call The additions USING and AND SKIP FIRST SCREEN for the statement CALL TRANSACTION are mutually exclusive.
In ABAP Objects and, as of release 7.0, outside of classes, the following statement causes an error message:
CALL TRANSACTION ... USING itab AND SKIP FIRST SCREEN.
Correct syntax:
CALL TRANSACTION ... USING itab.
Reason:
The content of the batch input table specified in the addition USING controls the entire transaction flow including the display of screens. The addition AND SKIP FIRST SCREEN is to be used only in connection with filling the mandatory input fields via SPA/GPA parameters. ABAP Code Snippet ABAP Code Snippet ARTICLE
No Implicit Field Names When Calling Dialog Modules To call dialog modules, the names of the fields from or to which data is transferred must be specified explicitly in ABAP Objects.
In ABAP Objects, the following syntax causes an error message:
CALL DIALOG ... EXPORTING f1 ... fn IMPORTING f1 ... fn.
Correct syntax:
CALL DIALOG ... EXPORTING f1 FROM f1 ... fn FROM fn IMPORTING f1 TO f1 ... fn TO fn.
Reason:
The use of implicit names can cause errors. With the implicit method, the system tries to find global data objects in the called program whose names are literally the same as the names specified after FROM or TO. If offset/length specifications or preceding selectors are used in the names, data objects with identical names cannot exist in the called program. ABAP Code Snippet
