SAP SUBST_SET_COMMANDFILE_NAME Function Module for Set the names of the export commandfiles









SUBST_SET_COMMANDFILE_NAME is a standard subst set commandfile name SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Set the names of the export commandfiles 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 subst set commandfile name FM, simply by entering the name SUBST_SET_COMMANDFILE_NAME into the relevant SAP transaction such as SE37 or SE38.

Function Group: SUG7
Program Name: SAPLSUG7
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function SUBST_SET_COMMANDFILE_NAME 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 'SUBST_SET_COMMANDFILE_NAME'"Set the names of the export commandfiles
EXPORTING
* IV_SAPVERS = ' ' "SAP R/3 Release

IMPORTING
EV_CUSTA = "Request/Task
EV_REPTA = "Request/Task
EV_GENTA = "Request/Task
EV_DDVTA = "Request/Task
EV_ADDTA = "Request/Task
EV_TSTTA = "Request/Task
EV_DOCTA = "Request/Task
EV_PCKTA = "Request/Task
EV_LANTA = "Request/Task
.



IMPORTING Parameters details for SUBST_SET_COMMANDFILE_NAME

IV_SAPVERS - SAP R/3 Release

Data type: PUTTB-SAPRELEASE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for SUBST_SET_COMMANDFILE_NAME

EV_CUSTA - Request/Task

Data type: E070-TRKORR
Optional: No
Call by Reference: No ( called with pass by value option)

EV_REPTA - Request/Task

Data type: E070-TRKORR
Optional: No
Call by Reference: No ( called with pass by value option)

EV_GENTA - Request/Task

Data type: E070-TRKORR
Optional: No
Call by Reference: No ( called with pass by value option)

EV_DDVTA - Request/Task

Data type: E070-TRKORR
Optional: No
Call by Reference: No ( called with pass by value option)

EV_ADDTA - Request/Task

Data type: E070-TRKORR
Optional: No
Call by Reference: No ( called with pass by value option)

EV_TSTTA - Request/Task

Data type: E070-TRKORR
Optional: No
Call by Reference: No ( called with pass by value option)

EV_DOCTA - Request/Task

Data type: E070-TRKORR
Optional: No
Call by Reference: No ( called with pass by value option)

EV_PCKTA - Request/Task

Data type: E070-TRKORR
Optional: No
Call by Reference: No ( called with pass by value option)

EV_LANTA - Request/Task

Data type: E070-TRKORR
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for SUBST_SET_COMMANDFILE_NAME 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_ev_custa  TYPE E070-TRKORR, "   
lv_iv_sapvers  TYPE PUTTB-SAPRELEASE, "   SPACE
lv_ev_repta  TYPE E070-TRKORR, "   
lv_ev_genta  TYPE E070-TRKORR, "   
lv_ev_ddvta  TYPE E070-TRKORR, "   
lv_ev_addta  TYPE E070-TRKORR, "   
lv_ev_tstta  TYPE E070-TRKORR, "   
lv_ev_docta  TYPE E070-TRKORR, "   
lv_ev_pckta  TYPE E070-TRKORR, "   
lv_ev_lanta  TYPE E070-TRKORR. "   

  CALL FUNCTION 'SUBST_SET_COMMANDFILE_NAME'  "Set the names of the export commandfiles
    EXPORTING
         IV_SAPVERS = lv_iv_sapvers
    IMPORTING
         EV_CUSTA = lv_ev_custa
         EV_REPTA = lv_ev_repta
         EV_GENTA = lv_ev_genta
         EV_DDVTA = lv_ev_ddvta
         EV_ADDTA = lv_ev_addta
         EV_TSTTA = lv_ev_tstta
         EV_DOCTA = lv_ev_docta
         EV_PCKTA = lv_ev_pckta
         EV_LANTA = lv_ev_lanta
. " SUBST_SET_COMMANDFILE_NAME




ABAP code using 7.40 inline data declarations to call FM SUBST_SET_COMMANDFILE_NAME

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 TRKORR FROM E070 INTO @DATA(ld_ev_custa).
 
"SELECT single SAPRELEASE FROM PUTTB INTO @DATA(ld_iv_sapvers).
DATA(ld_iv_sapvers) = ' '.
 
"SELECT single TRKORR FROM E070 INTO @DATA(ld_ev_repta).
 
"SELECT single TRKORR FROM E070 INTO @DATA(ld_ev_genta).
 
"SELECT single TRKORR FROM E070 INTO @DATA(ld_ev_ddvta).
 
"SELECT single TRKORR FROM E070 INTO @DATA(ld_ev_addta).
 
"SELECT single TRKORR FROM E070 INTO @DATA(ld_ev_tstta).
 
"SELECT single TRKORR FROM E070 INTO @DATA(ld_ev_docta).
 
"SELECT single TRKORR FROM E070 INTO @DATA(ld_ev_pckta).
 
"SELECT single TRKORR FROM E070 INTO @DATA(ld_ev_lanta).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!