REEX_CALLBACK_FI_CHECK_CONTR SAP Function module

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

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

Pattern for FM REEX_CALLBACK_FI_CHECK_CONTR - REEX CALLBACK FI CHECK CONTR

CALL FUNCTION 'REEX_CALLBACK_FI_CHECK_CONTR' "
  EXPORTING
    id_company_code =           " bukrs
    id_contract_ident =         " ranl
*   id_contract_type = '9'      " rantyp
*   id_customer =               " kunnr
*   id_vendor =                 " lifnr
  EXCEPTIONS
    CONTRACT_CUSTOMER_NOT_MATCHED = 1  "
    CONTRACT_VENDOR_NOT_MATCHED = 2  "
    NOT_FOUND = 3               "
    .  "  REEX_CALLBACK_FI_CHECK_CONTR

ABAP code example for Function Module REEX_CALLBACK_FI_CHECK_CONTR

The ABAP code below is a full code listing to execute function module REEX_CALLBACK_FI_CHECK_CONTR 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_id_company_code) = 'Check type of data required'.

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

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

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

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

CALL FUNCTION 'REEX_CALLBACK_FI_CHECK_CONTR'
  EXPORTING
    id_company_code =            ld_id_company_code
    id_contract_ident =          ld_id_contract_ident
*   id_contract_type =           ld_id_contract_type
*   id_customer =                ld_id_customer
*   id_vendor =                  ld_id_vendor
  EXCEPTIONS
    CONTRACT_CUSTOMER_NOT_MATCHED =    1
    CONTRACT_VENDOR_NOT_MATCHED =    2
    NOT_FOUND =                  3
    .  "  REEX_CALLBACK_FI_CHECK_CONTR

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "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_id_company_code
 
 TYPE BUKRS ,
ld_id_contract_ident
 
 TYPE RANL ,
ld_id_contract_type
 
 TYPE RANTYP ,
ld_id_customer
 
 TYPE KUNNR ,
ld_id_vendor
 
 TYPE LIFNR .


ld_id_company_code = 'Check type of data required'.
ld_id_contract_ident = 'Check type of data required'.
ld_id_contract_type = 'Check type of data required'.
ld_id_customer = 'Check type of data required'.
ld_id_vendor = 'Check type of data required'.