SAP SUBST_GET_MODIFICATION_STATE Function Module for Ermittelt den Modifikations-Status eines Transportobjektes
SUBST_GET_MODIFICATION_STATE is a standard subst get modification state SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Ermittelt den Modifikations-Status eines Transportobjektes 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 get modification state FM, simply by entering the name SUBST_GET_MODIFICATION_STATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SUGI
Program Name: SAPLSUGI
Main Program: SAPLSUGI
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SUBST_GET_MODIFICATION_STATE 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_GET_MODIFICATION_STATE'"Ermittelt den Modifikations-Status eines Transportobjektes.
EXPORTING
IV_PGMID = "Programm-ID des Transportobjekts (LIMU, R3TR)
IV_OBJECT = "Objekttyp des Transportobjekts
IV_OBJ_NAME = "Transport object name
* IV_NO_STD = ' ' "Objekte auf SAP Standard unterdrücken
IMPORTING
EV_CHSTATE = "Modification status
EV_LASTMOD = "Klasse des Verursachers
IMPORTING Parameters details for SUBST_GET_MODIFICATION_STATE
IV_PGMID - Programm-ID des Transportobjekts (LIMU, R3TR)
Data type: E071-PGMIDOptional: No
Call by Reference: No ( called with pass by value option)
IV_OBJECT - Objekttyp des Transportobjekts
Data type: E071-OBJECTOptional: No
Call by Reference: No ( called with pass by value option)
IV_OBJ_NAME - Transport object name
Data type: E071-OBJ_NAMEOptional: No
Call by Reference: No ( called with pass by value option)
IV_NO_STD - Objekte auf SAP Standard unterdrücken
Data type: GSUGI_PA-W_TADIRDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for SUBST_GET_MODIFICATION_STATE
EV_CHSTATE - Modification status
Data type: GSUGI_PA-W_CHSTATEOptional: No
Call by Reference: No ( called with pass by value option)
EV_LASTMOD - Klasse des Verursachers
Data type: GSUGI_PA-W_MODCLASSOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for SUBST_GET_MODIFICATION_STATE 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_iv_pgmid | TYPE E071-PGMID, " | |||
| lv_ev_chstate | TYPE GSUGI_PA-W_CHSTATE, " | |||
| lv_iv_object | TYPE E071-OBJECT, " | |||
| lv_ev_lastmod | TYPE GSUGI_PA-W_MODCLASS, " | |||
| lv_iv_obj_name | TYPE E071-OBJ_NAME, " | |||
| lv_iv_no_std | TYPE GSUGI_PA-W_TADIR. " ' ' |
|   CALL FUNCTION 'SUBST_GET_MODIFICATION_STATE' "Ermittelt den Modifikations-Status eines Transportobjektes |
| EXPORTING | ||
| IV_PGMID | = lv_iv_pgmid | |
| IV_OBJECT | = lv_iv_object | |
| IV_OBJ_NAME | = lv_iv_obj_name | |
| IV_NO_STD | = lv_iv_no_std | |
| IMPORTING | ||
| EV_CHSTATE | = lv_ev_chstate | |
| EV_LASTMOD | = lv_ev_lastmod | |
| . " SUBST_GET_MODIFICATION_STATE | ||
ABAP code using 7.40 inline data declarations to call FM SUBST_GET_MODIFICATION_STATE
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 PGMID FROM E071 INTO @DATA(ld_iv_pgmid). | ||||
| "SELECT single W_CHSTATE FROM GSUGI_PA INTO @DATA(ld_ev_chstate). | ||||
| "SELECT single OBJECT FROM E071 INTO @DATA(ld_iv_object). | ||||
| "SELECT single W_MODCLASS FROM GSUGI_PA INTO @DATA(ld_ev_lastmod). | ||||
| "SELECT single OBJ_NAME FROM E071 INTO @DATA(ld_iv_obj_name). | ||||
| "SELECT single W_TADIR FROM GSUGI_PA INTO @DATA(ld_iv_no_std). | ||||
| DATA(ld_iv_no_std) | = ' '. | |||
Search for further information about these or an SAP related objects