PPECHKHDR_CONSISTENCY_CHECK SAP Function module

PPECHKHDR_CONSISTENCY_CHECK 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 PPECHKHDR_CONSISTENCY_CHECK into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM PPECHKHDR_CONSISTENCY_CHECK - PPECHKHDR CONSISTENCY CHECK

CALL FUNCTION 'PPECHKHDR_CONSISTENCY_CHECK' "
  EXPORTING
    it_ppeguid =                " ppet4_ppeguid_tab
    it_checkid =                " ppchk_check_id_tab
    iv_batch = PPET_FALSE       " c
*   iv_with_timewindows = PPET_FALSE  " c
*   iv_init_ecm = PPET_FALSE    " c
*   iv_package_size = 100       " i
*   iv_msg_context = PPCHK_MSG_CONT-PPECHK  " ppe_msg_context
  IMPORTING
    et_msg =                    " ppchk_appl_log_msg_tab
  EXCEPTIONS
    INTERNAL_ERROR = 1          "
    .  "  PPECHKHDR_CONSISTENCY_CHECK

ABAP code example for Function Module PPECHKHDR_CONSISTENCY_CHECK

The ABAP code below is a full code listing to execute function module PPECHKHDR_CONSISTENCY_CHECK 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_msg  
 
 TYPE PPCHK_APPL_LOG_MSG_TAB
.


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

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

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

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

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

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

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

CALL FUNCTION 'PPECHKHDR_CONSISTENCY_CHECK'
  EXPORTING
    it_ppeguid =                 ld_it_ppeguid
    it_checkid =                 ld_it_checkid
    iv_batch =                   ld_iv_batch
*   iv_with_timewindows =        ld_iv_with_timewindows
*   iv_init_ecm =                ld_iv_init_ecm
*   iv_package_size =            ld_iv_package_size
*   iv_msg_context =             ld_iv_msg_context
  IMPORTING
    et_msg =                     ld_et_msg
  EXCEPTIONS
    INTERNAL_ERROR =             1
    .  "  PPECHKHDR_CONSISTENCY_CHECK

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
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_msg
 
 TYPE PPCHK_APPL_LOG_MSG_TAB ,
ld_it_ppeguid
 
 TYPE PPET4_PPEGUID_TAB ,
ld_it_checkid
 
 TYPE PPCHK_CHECK_ID_TAB ,
ld_iv_batch
 
 TYPE C ,
ld_iv_with_timewindows
 
 TYPE C ,
ld_iv_init_ecm
 
 TYPE C ,
ld_iv_package_size
 
 TYPE I ,
ld_iv_msg_context
 
 TYPE PPE_MSG_CONTEXT .


ld_it_ppeguid = 'Check type of data required'.
ld_it_checkid = 'Check type of data required'.
ld_iv_batch = 'Check type of data required'.
ld_iv_with_timewindows = 'Check type of data required'.
ld_iv_init_ecm = 'Check type of data required'.
ld_iv_package_size = 'Check type of data required'.
ld_iv_msg_context = 'Check type of data required'.