SAP SUBST_UPDATE_COMMANDFILE_SUG7 Function Module for Update command file
SUBST_UPDATE_COMMANDFILE_SUG7 is a standard subst update commandfile sug7 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Update command file 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 update commandfile sug7 FM, simply by entering the name SUBST_UPDATE_COMMANDFILE_SUG7 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_UPDATE_COMMANDFILE_SUG7 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_UPDATE_COMMANDFILE_SUG7'"Update command file.
EXPORTING
IV_KORRNAME = "Command file
TABLES
E071_TAB = "List of objects which will be inserted
LOG_TAB = "Log Generation Interface
EXCEPTIONS
ERROR_UPDATE_COMMANDFILE = 1
IMPORTING Parameters details for SUBST_UPDATE_COMMANDFILE_SUG7
IV_KORRNAME - Command file
Data type: E070-TRKORROptional: No
Call by Reference: Yes
TABLES Parameters details for SUBST_UPDATE_COMMANDFILE_SUG7
E071_TAB - List of objects which will be inserted
Data type: E071Optional: No
Call by Reference: Yes
LOG_TAB - Log Generation Interface
Data type: SPROT_UOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR_UPDATE_COMMANDFILE - Error when updating the command file
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SUBST_UPDATE_COMMANDFILE_SUG7 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: | ||||
| lt_e071_tab | TYPE STANDARD TABLE OF E071, " | |||
| lv_iv_korrname | TYPE E070-TRKORR, " | |||
| lv_error_update_commandfile | TYPE E070, " | |||
| lt_log_tab | TYPE STANDARD TABLE OF SPROT_U. " |
|   CALL FUNCTION 'SUBST_UPDATE_COMMANDFILE_SUG7' "Update command file |
| EXPORTING | ||
| IV_KORRNAME | = lv_iv_korrname | |
| TABLES | ||
| E071_TAB | = lt_e071_tab | |
| LOG_TAB | = lt_log_tab | |
| EXCEPTIONS | ||
| ERROR_UPDATE_COMMANDFILE = 1 | ||
| . " SUBST_UPDATE_COMMANDFILE_SUG7 | ||
ABAP code using 7.40 inline data declarations to call FM SUBST_UPDATE_COMMANDFILE_SUG7
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_iv_korrname). | ||||
Search for further information about these or an SAP related objects