SAP EHPRC_CP_CD01_CHKDOC_READ Function Module for CP: Get change documents from substance_save_to_db
EHPRC_CP_CD01_CHKDOC_READ is a standard ehprc cp cd01 chkdoc read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for CP: Get change documents from substance_save_to_db 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 ehprc cp cd01 chkdoc read FM, simply by entering the name EHPRC_CP_CD01_CHKDOC_READ into the relevant SAP transaction such as SE37 or SE38.
Function Group: EHPRC_CP_CD01
Program Name: SAPLEHPRC_CP_CD01
Main Program: SAPLEHPRC_CP_CD01
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EHPRC_CP_CD01_CHKDOC_READ 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 'EHPRC_CP_CD01_CHKDOC_READ'"CP: Get change documents from substance_save_to_db.
IMPORTING
ET_EHS_CHG_DOCS = "CP: Table type of est_change_docs
EO_LOGGER = "CP: Logger for the application log.
EXPORTING Parameters details for EHPRC_CP_CD01_CHKDOC_READ
ET_EHS_CHG_DOCS - CP: Table type of est_change_docs
Data type: EHPRCT_EST_CHANGE_DOCSOptional: No
Call by Reference: Yes
EO_LOGGER - CP: Logger for the application log.
Data type: CL_EHPRC_LOGGEROptional: No
Call by Reference: Yes
Copy and paste ABAP code example for EHPRC_CP_CD01_CHKDOC_READ 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_et_ehs_chg_docs | TYPE EHPRCT_EST_CHANGE_DOCS, " | |||
| lv_eo_logger | TYPE CL_EHPRC_LOGGER. " |
|   CALL FUNCTION 'EHPRC_CP_CD01_CHKDOC_READ' "CP: Get change documents from substance_save_to_db |
| IMPORTING | ||
| ET_EHS_CHG_DOCS | = lv_et_ehs_chg_docs | |
| EO_LOGGER | = lv_eo_logger | |
| . " EHPRC_CP_CD01_CHKDOC_READ | ||
ABAP code using 7.40 inline data declarations to call FM EHPRC_CP_CD01_CHKDOC_READ
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