SAP EHPRC_CP_CK03_CHECK_BASE Function Module for CP: Execute BASE check
EHPRC_CP_CK03_CHECK_BASE is a standard ehprc cp ck03 check base 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: Execute BASE check 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 ck03 check base FM, simply by entering the name EHPRC_CP_CK03_CHECK_BASE into the relevant SAP transaction such as SE37 or SE38.
Function Group: EHPRC_CP_CK03
Program Name: SAPLEHPRC_CP_CK03
Main Program: SAPLEHPRC_CP_CK03
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EHPRC_CP_CK03_CHECK_BASE 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_CK03_CHECK_BASE'"CP: Execute BASE check.
EXPORTING
* I_COMPL_DATA_KEY = "NodeID
* I_SUBID = "
I_CHECK = "Check
* I_REGLIST = "Regulatory/Customer List
I_ADDINF = "
* IV_FORCE_FULL_CHECK = ABAP_FALSE "Truth Value
* IO_DATA_SOURCE = "CP: Interface for data and norm handler
IMPORTING
ET_CHECK_RESULT = "
ET_MESSAGE = "
ET_FAILED_KEYS = "CP: Message table
IMPORTING Parameters details for EHPRC_CP_CK03_CHECK_BASE
I_COMPL_DATA_KEY - NodeID
Data type: /BOBF/CONF_KEYOptional: Yes
Call by Reference: Yes
I_SUBID -
Data type: ESESUBIDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_CHECK - Check
Data type: EHFND_CHECKOptional: No
Call by Reference: No ( called with pass by value option)
I_REGLIST - Regulatory/Customer List
Data type: EHFND_REGLISTOptional: Yes
Call by Reference: No ( called with pass by value option)
I_ADDINF -
Data type: RCGADDINFOptional: No
Call by Reference: No ( called with pass by value option)
IV_FORCE_FULL_CHECK - Truth Value
Data type: ESEBOOLEDefault: ABAP_FALSE
Optional: Yes
Call by Reference: Yes
IO_DATA_SOURCE - CP: Interface for data and norm handler
Data type: IF_EHPRC_BOS_DATA_HANDLEROptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for EHPRC_CP_CK03_CHECK_BASE
ET_CHECK_RESULT -
Data type: EHPRCT_CHECK_RESULTOptional: No
Call by Reference: Yes
ET_MESSAGE -
Data type: EHPRCT_MESSAGESOptional: No
Call by Reference: Yes
ET_FAILED_KEYS - CP: Message table
Data type: EHPRCT_FAILED_KEYSOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for EHPRC_CP_CK03_CHECK_BASE 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_check_result | TYPE EHPRCT_CHECK_RESULT, " | |||
| lv_i_compl_data_key | TYPE /BOBF/CONF_KEY, " | |||
| lv_i_subid | TYPE ESESUBID, " | |||
| lv_et_message | TYPE EHPRCT_MESSAGES, " | |||
| lv_i_check | TYPE EHFND_CHECK, " | |||
| lv_et_failed_keys | TYPE EHPRCT_FAILED_KEYS, " | |||
| lv_i_reglist | TYPE EHFND_REGLIST, " | |||
| lv_i_addinf | TYPE RCGADDINF, " | |||
| lv_iv_force_full_check | TYPE ESEBOOLE, " ABAP_FALSE | |||
| lv_io_data_source | TYPE IF_EHPRC_BOS_DATA_HANDLER. " |
|   CALL FUNCTION 'EHPRC_CP_CK03_CHECK_BASE' "CP: Execute BASE check |
| EXPORTING | ||
| I_COMPL_DATA_KEY | = lv_i_compl_data_key | |
| I_SUBID | = lv_i_subid | |
| I_CHECK | = lv_i_check | |
| I_REGLIST | = lv_i_reglist | |
| I_ADDINF | = lv_i_addinf | |
| IV_FORCE_FULL_CHECK | = lv_iv_force_full_check | |
| IO_DATA_SOURCE | = lv_io_data_source | |
| IMPORTING | ||
| ET_CHECK_RESULT | = lv_et_check_result | |
| ET_MESSAGE | = lv_et_message | |
| ET_FAILED_KEYS | = lv_et_failed_keys | |
| . " EHPRC_CP_CK03_CHECK_BASE | ||
ABAP code using 7.40 inline data declarations to call FM EHPRC_CP_CK03_CHECK_BASE
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.| DATA(ld_iv_force_full_check) | = ABAP_FALSE. | |||
Search for further information about these or an SAP related objects