SAP Function Modules

ME_READ_CONTRACTS_MULT SAP Function module







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

Associated Function Group: MEXF
Released Date: Not Released
Processing type: Remote-Enabled
remote enabled module settings


Pattern for FM ME_READ_CONTRACTS_MULT - ME READ CONTRACTS MULT





CALL FUNCTION 'ME_READ_CONTRACTS_MULT' "
* EXPORTING
*   i_vendor_id =               " lifnr
*   i_material =                " matnr         Material Number
*   i_agreement_date =          " vedat
*   i_material_group =          " matkl         Material Group
*   i_valid_start_date =        " kdatb
*   i_valid_end_date =          " kdate
*   i_contract_number =         " ebeln         Purchasing Document Number
*   i_contract_amount =         " bprei
*   i_contract_quantity =       " ktmng         Target quantity
  TABLES
    et_contract_itms =          " contract_itms
    .  "  ME_READ_CONTRACTS_MULT

ABAP code example for Function Module ME_READ_CONTRACTS_MULT





The ABAP code below is a full code listing to execute function module ME_READ_CONTRACTS_MULT 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:
it_et_contract_itms  TYPE STANDARD TABLE OF CONTRACT_ITMS,"TABLES PARAM
wa_et_contract_itms  LIKE LINE OF it_et_contract_itms .

DATA(ld_i_vendor_id) = 'Check type of data required'.
DATA(ld_i_material) = 'Check type of data required'.
DATA(ld_i_agreement_date) = 'Check type of data required'.
DATA(ld_i_material_group) = 'Check type of data required'.
DATA(ld_i_valid_start_date) = 'Check type of data required'.
DATA(ld_i_valid_end_date) = 'Check type of data required'.
DATA(ld_i_contract_number) = 'Check type of data required'.
DATA(ld_i_contract_amount) = 'Check type of data required'.
DATA(ld_i_contract_quantity) = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_et_contract_itms to it_et_contract_itms. . CALL FUNCTION 'ME_READ_CONTRACTS_MULT' * EXPORTING * i_vendor_id = ld_i_vendor_id * i_material = ld_i_material * i_agreement_date = ld_i_agreement_date * i_material_group = ld_i_material_group * i_valid_start_date = ld_i_valid_start_date * i_valid_end_date = ld_i_valid_end_date * i_contract_number = ld_i_contract_number * i_contract_amount = ld_i_contract_amount * i_contract_quantity = ld_i_contract_quantity TABLES et_contract_itms = it_et_contract_itms . " ME_READ_CONTRACTS_MULT
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_i_vendor_id  TYPE LIFNR ,
it_et_contract_itms  TYPE STANDARD TABLE OF CONTRACT_ITMS ,
wa_et_contract_itms  LIKE LINE OF it_et_contract_itms,
ld_i_material  TYPE MATNR ,
ld_i_agreement_date  TYPE VEDAT ,
ld_i_material_group  TYPE MATKL ,
ld_i_valid_start_date  TYPE KDATB ,
ld_i_valid_end_date  TYPE KDATE ,
ld_i_contract_number  TYPE EBELN ,
ld_i_contract_amount  TYPE BPREI ,
ld_i_contract_quantity  TYPE KTMNG .

ld_i_vendor_id = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_et_contract_itms to it_et_contract_itms.
ld_i_material = 'Check type of data required'.
ld_i_agreement_date = 'Check type of data required'.
ld_i_material_group = 'Check type of data required'.
ld_i_valid_start_date = 'Check type of data required'.
ld_i_valid_end_date = 'Check type of data required'.
ld_i_contract_number = 'Check type of data required'.
ld_i_contract_amount = 'Check type of data required'.
ld_i_contract_quantity = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name ME_READ_CONTRACTS_MULT or its description.