EHPRC_CP_CK03_CHECK_COMPL SAP Function module - CP: Compliance Check

EHPRC_CP_CK03_CHECK_COMPL is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name EHPRC_CP_CK03_CHECK_COMPL into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: EHPRC_CP_CK03
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM EHPRC_CP_CK03_CHECK_COMPL - EHPRC CP CK03 CHECK COMPL

CALL FUNCTION 'EHPRC_CP_CK03_CHECK_COMPL' "CP: Compliance Check
  EXPORTING
*   i_compl_data_key =          " /bobf/conf_key  NodeID
*   i_subid =                   " esesubid
    i_check =                   " ehfnd_check   Check
*   i_reglist =                 " ehfnd_reglist  Regulatory/Customer List
    i_addinf =                  " rcgaddinf
*   i_flg_buf_write = ESP1_TRUE  " eseboole     Truth Value
*   io_data_source =            " if_ehprc_bos_data_handler  Reference to data handler object
*   is_normvar =                " ehprcs_norma_input_fields  CP: Normalization key fields for identification
*   iv_set_class = ESP1_FALSE   " eseboole      Set classification
*   iv_force_full_check = ABAP_FALSE  " eseboole  Truth Value
  IMPORTING
    et_check_result =           " ehprct_check_result
    et_pure_violate =           " ehprct_pure_violate
    et_message =                " ehprct_messages
    et_failed_keys =            " ehprct_failed_keys  Structure containing failed keys and reasons
    .  "  EHPRC_CP_CK03_CHECK_COMPL

ABAP code example for Function Module EHPRC_CP_CK03_CHECK_COMPL

The ABAP code below is a full code listing to execute function module EHPRC_CP_CK03_CHECK_COMPL including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_et_check_result  
 
 TYPE EHPRCT_CHECK_RESULT
,
ld_et_pure_violate  
 
 TYPE EHPRCT_PURE_VIOLATE
,
ld_et_message  
 
 TYPE EHPRCT_MESSAGES
,
ld_et_failed_keys  
 
 TYPE EHPRCT_FAILED_KEYS
.


DATA(ld_i_compl_data_key) = 'Check type of data required'.

DATA(ld_i_subid) = 'Check type of data required'.

DATA(ld_i_check) = 'Check type of data required'.

DATA(ld_i_reglist) = 'Check type of data required'.

DATA(ld_i_addinf) = 'Check type of data required'.

DATA(ld_i_flg_buf_write) = 'Check type of data required'.

DATA(ld_io_data_source) = 'Check type of data required'.

DATA(ld_is_normvar) = 'Check type of data required'.

DATA(ld_iv_set_class) = 'Check type of data required'.

DATA(ld_iv_force_full_check) = 'Check type of data required'.
.

CALL FUNCTION 'EHPRC_CP_CK03_CHECK_COMPL'
  EXPORTING
*   i_compl_data_key =           ld_i_compl_data_key
*   i_subid =                    ld_i_subid
    i_check =                    ld_i_check
*   i_reglist =                  ld_i_reglist
    i_addinf =                   ld_i_addinf
*   i_flg_buf_write =            ld_i_flg_buf_write
*   io_data_source =             ld_io_data_source
*   is_normvar =                 ld_is_normvar
*   iv_set_class =               ld_iv_set_class
*   iv_force_full_check =        ld_iv_force_full_check
  IMPORTING
    et_check_result =            ld_et_check_result
    et_pure_violate =            ld_et_pure_violate
    et_message =                 ld_et_message
    et_failed_keys =             ld_et_failed_keys
    .  "  EHPRC_CP_CK03_CHECK_COMPL

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_et_check_result
 
 TYPE EHPRCT_CHECK_RESULT ,
ld_i_compl_data_key
 
 TYPE /BOBF/CONF_KEY ,
ld_et_pure_violate
 
 TYPE EHPRCT_PURE_VIOLATE ,
ld_i_subid
 
 TYPE ESESUBID ,
ld_et_message
 
 TYPE EHPRCT_MESSAGES ,
ld_i_check
 
 TYPE EHFND_CHECK ,
ld_et_failed_keys
 
 TYPE EHPRCT_FAILED_KEYS ,
ld_i_reglist
 
 TYPE EHFND_REGLIST ,
ld_i_addinf
 
 TYPE RCGADDINF ,
ld_i_flg_buf_write
 
 TYPE ESEBOOLE ,
ld_io_data_source
 
 TYPE IF_EHPRC_BOS_DATA_HANDLER ,
ld_is_normvar
 
 TYPE EHPRCS_NORMA_INPUT_FIELDS ,
ld_iv_set_class
 
 TYPE ESEBOOLE ,
ld_iv_force_full_check
 
 TYPE ESEBOOLE .


ld_i_compl_data_key = 'Check type of data required'.
ld_i_subid = 'Check type of data required'.
ld_i_check = 'Check type of data required'.
ld_i_reglist = 'Check type of data required'.
ld_i_addinf = 'Check type of data required'.
ld_i_flg_buf_write = 'Check type of data required'.
ld_io_data_source = 'Check type of data required'.
ld_is_normvar = 'Check type of data required'.
ld_iv_set_class = 'Check type of data required'.
ld_iv_force_full_check = 'Check type of data required'.