SAP /SMB/CALL_TCODE Function Module for Start a new screen while calling a TCODE
/SMB/CALL_TCODE is a standard /smb/call tcode SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Start a new screen while calling a TCODE processing and below is the pattern details for this FM, 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 /smb/call tcode FM, simply by entering the name /SMB/CALL_TCODE into the relevant SAP transaction such as SE37 or SE38.
Function Group: /SMB/BBPRJ_INSTALLER
Program Name: /SMB/SAPLBBPRJ_INSTALLER
Main Program: /SMB/SAPLBBPRJ_INSTALLER
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function /SMB/CALL_TCODE 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 '/SMB/CALL_TCODE'"Start a new screen while calling a TCODE.
EXPORTING
TCODE = "Object ID
EXCEPTIONS
COMMUNICATION_FAILURE = 1 SYSTEM_FAILURE = 2
IMPORTING Parameters details for /SMB/CALL_TCODE
TCODE - Object ID
Data type: /SMB/BP_EDT12Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
COMMUNICATION_FAILURE - COMMUNICATION_FAILURE
Data type:Optional: No
Call by Reference: Yes
SYSTEM_FAILURE - SYSTEM_FAILURE
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for /SMB/CALL_TCODE 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_tcode | TYPE /SMB/BP_EDT12, " | |||
| lv_communication_failure | TYPE /SMB/BP_EDT12, " | |||
| lv_system_failure | TYPE /SMB/BP_EDT12. " |
|   CALL FUNCTION '/SMB/CALL_TCODE' "Start a new screen while calling a TCODE |
| EXPORTING | ||
| TCODE | = lv_tcode | |
| EXCEPTIONS | ||
| COMMUNICATION_FAILURE = 1 | ||
| SYSTEM_FAILURE = 2 | ||
| . " /SMB/CALL_TCODE | ||
ABAP code using 7.40 inline data declarations to call FM /SMB/CALL_TCODE
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.Search for further information about these or an SAP related objects