SAP GM_CHANGE_DOCUMENT_READ_PROGR Function Module for Read Change Document Header
GM_CHANGE_DOCUMENT_READ_PROGR is a standard gm change document read progr SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read Change Document Header 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 gm change document read progr FM, simply by entering the name GM_CHANGE_DOCUMENT_READ_PROGR into the relevant SAP transaction such as SE37 or SE38.
Function Group: GMSO
Program Name: SAPLGMSO
Main Program: SAPLGMSO
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GM_CHANGE_DOCUMENT_READ_PROGR 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 'GM_CHANGE_DOCUMENT_READ_PROGR'"Read Change Document Header.
TABLES
* T_GMSPPROGRAM = "Structure for FM Object Assignment
TABLES Parameters details for GM_CHANGE_DOCUMENT_READ_PROGR
T_GMSPPROGRAM - Structure for FM Object Assignment
Data type: GMSPPROGRAMOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for GM_CHANGE_DOCUMENT_READ_PROGR 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_t_gmspprogram | TYPE STANDARD TABLE OF GMSPPROGRAM. " |
|   CALL FUNCTION 'GM_CHANGE_DOCUMENT_READ_PROGR' "Read Change Document Header |
| TABLES | ||
| T_GMSPPROGRAM | = lt_t_gmspprogram | |
| . " GM_CHANGE_DOCUMENT_READ_PROGR | ||
ABAP code using 7.40 inline data declarations to call FM GM_CHANGE_DOCUMENT_READ_PROGR
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