SAP DOCCHG_POST_DOC Function Module for
DOCCHG_POST_DOC is a standard docchg post doc SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 docchg post doc FM, simply by entering the name DOCCHG_POST_DOC into the relevant SAP transaction such as SE37 or SE38.
Function Group: DOC_CHANGE_EXT
Program Name: SAPLDOC_CHANGE_EXT
Main Program: SAPLDOC_CHANGE_EXT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DOCCHG_POST_DOC 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 'DOCCHG_POST_DOC'".
TABLES
IT_ITEMS = "## AUTOMATICALLY GENERATED. DO NOT CHANGE OR RE-USE ! ##
IT_CHGFLD = "Fields to Be Changed
XT_MSGCOL = "
EXCEPTIONS
NO_OPENITEM = 1
TABLES Parameters details for DOCCHG_POST_DOC
IT_ITEMS - ## AUTOMATICALLY GENERATED. DO NOT CHANGE OR RE-USE ! ##
Data type: RFPOSXEXTOptional: No
Call by Reference: Yes
IT_CHGFLD - Fields to Be Changed
Data type: FDCEX_T_CHGFLDOptional: No
Call by Reference: Yes
XT_MSGCOL -
Data type: FDCEX_T_MSGCOLOptional: No
Call by Reference: Yes
EXCEPTIONS details
NO_OPENITEM - No open items
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for DOCCHG_POST_DOC 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_it_items | TYPE STANDARD TABLE OF RFPOSXEXT, " | |||
| lv_no_openitem | TYPE RFPOSXEXT, " | |||
| lt_it_chgfld | TYPE STANDARD TABLE OF FDCEX_T_CHGFLD, " | |||
| lt_xt_msgcol | TYPE STANDARD TABLE OF FDCEX_T_MSGCOL. " |
|   CALL FUNCTION 'DOCCHG_POST_DOC' " |
| TABLES | ||
| IT_ITEMS | = lt_it_items | |
| IT_CHGFLD | = lt_it_chgfld | |
| XT_MSGCOL | = lt_xt_msgcol | |
| EXCEPTIONS | ||
| NO_OPENITEM = 1 | ||
| . " DOCCHG_POST_DOC | ||
ABAP code using 7.40 inline data declarations to call FM DOCCHG_POST_DOC
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