SUBST_SET_COMMANDFILE_NAME SAP Function module - Set the names of the export commandfiles

SUBST_SET_COMMANDFILE_NAME is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name SUBST_SET_COMMANDFILE_NAME into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SUG7
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM SUBST_SET_COMMANDFILE_NAME - SUBST SET COMMANDFILE NAME

CALL FUNCTION 'SUBST_SET_COMMANDFILE_NAME' "Set the names of the export commandfiles
* EXPORTING
*   iv_sapvers = SPACE          " puttb-saprelease  SAP R/3 Release
  IMPORTING
    ev_custa =                  " e070-trkorr   Request/Task
    ev_repta =                  " e070-trkorr   Request/Task
    ev_genta =                  " e070-trkorr   Request/Task
    ev_ddvta =                  " e070-trkorr   Request/Task
    ev_addta =                  " e070-trkorr   Request/Task
    ev_tstta =                  " e070-trkorr   Request/Task
    ev_docta =                  " e070-trkorr   Request/Task
    ev_pckta =                  " e070-trkorr   Request/Task
    ev_lanta =                  " e070-trkorr   Request/Task
    .  "  SUBST_SET_COMMANDFILE_NAME

ABAP code example for Function Module SUBST_SET_COMMANDFILE_NAME

The ABAP code below is a full code listing to execute function module SUBST_SET_COMMANDFILE_NAME including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_ev_custa  
 
 TYPE E070-TRKORR
,
ld_ev_repta  
 
 TYPE E070-TRKORR
,
ld_ev_genta  
 
 TYPE E070-TRKORR
,
ld_ev_ddvta  
 
 TYPE E070-TRKORR
,
ld_ev_addta  
 
 TYPE E070-TRKORR
,
ld_ev_tstta  
 
 TYPE E070-TRKORR
,
ld_ev_docta  
 
 TYPE E070-TRKORR
,
ld_ev_pckta  
 
 TYPE E070-TRKORR
,
ld_ev_lanta  
 
 TYPE E070-TRKORR
.

 

SELECT single SAPRELEASE 
  FROM PUTTB 
  INTO @DATA(ld_iv_sapvers).

.

CALL FUNCTION 'SUBST_SET_COMMANDFILE_NAME'
* EXPORTING
*   iv_sapvers =                 ld_iv_sapvers
  IMPORTING
    ev_custa =                   ld_ev_custa
    ev_repta =                   ld_ev_repta
    ev_genta =                   ld_ev_genta
    ev_ddvta =                   ld_ev_ddvta
    ev_addta =                   ld_ev_addta
    ev_tstta =                   ld_ev_tstta
    ev_docta =                   ld_ev_docta
    ev_pckta =                   ld_ev_pckta
    ev_lanta =                   ld_ev_lanta
    .  "  SUBST_SET_COMMANDFILE_NAME

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_ev_custa
 
 TYPE E070-TRKORR ,
ld_iv_sapvers
 
 TYPE PUTTB-SAPRELEASE ,
ld_ev_repta
 
 TYPE E070-TRKORR ,
ld_ev_genta
 
 TYPE E070-TRKORR ,
ld_ev_ddvta
 
 TYPE E070-TRKORR ,
ld_ev_addta
 
 TYPE E070-TRKORR ,
ld_ev_tstta
 
 TYPE E070-TRKORR ,
ld_ev_docta
 
 TYPE E070-TRKORR ,
ld_ev_pckta
 
 TYPE E070-TRKORR ,
ld_ev_lanta
 
 TYPE E070-TRKORR .



SELECT single SAPRELEASE 
  FROM PUTTB 
  INTO ld_iv_sapvers.