SAP ABAP4_CALL_TRANSACTION Function Module for
ABAP4_CALL_TRANSACTION is a standard abap4 call transaction SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for abap4 call transaction FM, simply by entering the name ABAP4_CALL_TRANSACTION into the relevant SAP transaction such as SE37 or SE38.
Function Group: SBDC
Program Name: SAPLSBDC
Main Program: SAPLSBDC
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function ABAP4_CALL_TRANSACTION pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'ABAP4_CALL_TRANSACTION'".
EXPORTING
TCODE = "Transaction Code
* SKIP_SCREEN = ' ' "
* MODE_VAL = 'A' "
* UPDATE_VAL = 'A' "
IMPORTING
SUBRC = "
TABLES
* USING_TAB = "
* SPAGPA_TAB = "
* MESS_TAB = "
EXCEPTIONS
CALL_TRANSACTION_DENIED = 1 TCODE_INVALID = 2
IMPORTING Parameters details for ABAP4_CALL_TRANSACTION
TCODE - Transaction Code
Data type: SY-TCODEOptional: No
Call by Reference: No ( called with pass by value option)
SKIP_SCREEN -
Data type: SY-FTYPEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
MODE_VAL -
Data type: SY-FTYPEDefault: 'A'
Optional: Yes
Call by Reference: No ( called with pass by value option)
UPDATE_VAL -
Data type: SY-FTYPEDefault: 'A'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ABAP4_CALL_TRANSACTION
SUBRC -
Data type: SY-SUBRCOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ABAP4_CALL_TRANSACTION
USING_TAB -
Data type: BDCDATAOptional: Yes
Call by Reference: No ( called with pass by value option)
SPAGPA_TAB -
Data type: RFC_SPAGPAOptional: Yes
Call by Reference: No ( called with pass by value option)
MESS_TAB -
Data type: BDCMSGCOLLOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
CALL_TRANSACTION_DENIED - No Authorization
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TCODE_INVALID -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ABAP4_CALL_TRANSACTION Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.DATA: | ||||
lv_subrc | TYPE SY-SUBRC, " | |||
lv_tcode | TYPE SY-TCODE, " | |||
lt_using_tab | TYPE STANDARD TABLE OF BDCDATA, " | |||
lv_call_transaction_denied | TYPE BDCDATA, " | |||
lt_spagpa_tab | TYPE STANDARD TABLE OF RFC_SPAGPA, " | |||
lv_skip_screen | TYPE SY-FTYPE, " SPACE | |||
lv_tcode_invalid | TYPE SY, " | |||
lt_mess_tab | TYPE STANDARD TABLE OF BDCMSGCOLL, " | |||
lv_mode_val | TYPE SY-FTYPE, " 'A' | |||
lv_update_val | TYPE SY-FTYPE. " 'A' |
  CALL FUNCTION 'ABAP4_CALL_TRANSACTION' " |
EXPORTING | ||
TCODE | = lv_tcode | |
SKIP_SCREEN | = lv_skip_screen | |
MODE_VAL | = lv_mode_val | |
UPDATE_VAL | = lv_update_val | |
IMPORTING | ||
SUBRC | = lv_subrc | |
TABLES | ||
USING_TAB | = lt_using_tab | |
SPAGPA_TAB | = lt_spagpa_tab | |
MESS_TAB | = lt_mess_tab | |
EXCEPTIONS | ||
CALL_TRANSACTION_DENIED = 1 | ||
TCODE_INVALID = 2 | ||
. " ABAP4_CALL_TRANSACTION |
ABAP code using 7.40 inline data declarations to call FM ABAP4_CALL_TRANSACTION
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8."SELECT single SUBRC FROM SY INTO @DATA(ld_subrc). | ||||
"SELECT single TCODE FROM SY INTO @DATA(ld_tcode). | ||||
"SELECT single FTYPE FROM SY INTO @DATA(ld_skip_screen). | ||||
DATA(ld_skip_screen) | = ' '. | |||
"SELECT single FTYPE FROM SY INTO @DATA(ld_mode_val). | ||||
DATA(ld_mode_val) | = 'A'. | |||
"SELECT single FTYPE FROM SY INTO @DATA(ld_update_val). | ||||
DATA(ld_update_val) | = 'A'. | |||
Search for further information about these or an SAP related objects