SAP Function Modules

ME_CONFIRMATION_CHECK_QUANTITY SAP Function module







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

Associated Function Group: EINB
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM ME_CONFIRMATION_CHECK_QUANTITY - ME CONFIRMATION CHECK QUANTITY





CALL FUNCTION 'ME_CONFIRMATION_CHECK_QUANTITY' "
  EXPORTING
*   i_ebeln = SPACE             " ekko-ebeln    Purchase Order
*   i_ebelp = 0                 " ekpo-ebelp    Purchase Order Item
    i_meins =                   " ekpo-meins    Purchase Order Unit of Measure
    i_menge =                   " ekpo-menge    Quantity
*   i_vbeln = SPACE             " ekes-vbeln
*   i_vbelp = 0                 " ekes-vbelp
*   i_date = 19960101           " ekes-eindt
*   i_ibtyp =                   " t163d-ibtyp
*   i_umrez =                   " komdlgn-umvkn
*   i_umren =                   " komdlgn-umvkn
*   i_msg = 'X'                 "
*   i_collect_messages =        " xfeld         Checkbox
*   i_ekbeh =                   " c
    i_new_conf = ' '            " mmpur_bool
  IMPORTING
    e_umrez =                   " komdlgn-umvkn
    e_umren =                   " komdlgn-umvkn
* TABLES
*   errors =                    " wuebs
*   t_ekes =                    " uekes         Change Document Structure: Generated by RSSCD000
  EXCEPTIONS
    CONFIRMATION_NOT_FOUND = 1  "
    CONVERSION_NOT_POSSIBLE = 2  "
    PO_NOT_FOUND = 3            "               Purchase order does not exist
    PO_NOT_VALID = 4            "
    .  "  ME_CONFIRMATION_CHECK_QUANTITY

ABAP code example for Function Module ME_CONFIRMATION_CHECK_QUANTITY





The ABAP code below is a full code listing to execute function module ME_CONFIRMATION_CHECK_QUANTITY 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_e_umrez  TYPE KOMDLGN-UMVKN ,
ld_e_umren  TYPE KOMDLGN-UMVKN ,
it_errors  TYPE STANDARD TABLE OF WUEBS,"TABLES PARAM
wa_errors  LIKE LINE OF it_errors ,
it_t_ekes  TYPE STANDARD TABLE OF UEKES,"TABLES PARAM
wa_t_ekes  LIKE LINE OF it_t_ekes .


SELECT single EBELN
FROM EKKO
INTO @DATA(ld_i_ebeln).


SELECT single EBELP
FROM EKPO
INTO @DATA(ld_i_ebelp).


SELECT single MEINS
FROM EKPO
INTO @DATA(ld_i_meins).


SELECT single MENGE
FROM EKPO
INTO @DATA(ld_i_menge).


SELECT single VBELN
FROM EKES
INTO @DATA(ld_i_vbeln).


SELECT single VBELP
FROM EKES
INTO @DATA(ld_i_vbelp).


SELECT single EINDT
FROM EKES
INTO @DATA(ld_i_date).


SELECT single IBTYP
FROM T163D
INTO @DATA(ld_i_ibtyp).


DATA(ld_i_umrez) = Check type of data required

DATA(ld_i_umren) = Check type of data required
DATA(ld_i_msg) = 'some text here'.
DATA(ld_i_collect_messages) = 'Check type of data required'.
DATA(ld_i_ekbeh) = 'Check type of data required'.
DATA(ld_i_new_conf) = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_errors to it_errors.

"populate fields of struture and append to itab
append wa_t_ekes to it_t_ekes. . CALL FUNCTION 'ME_CONFIRMATION_CHECK_QUANTITY' EXPORTING * i_ebeln = ld_i_ebeln * i_ebelp = ld_i_ebelp i_meins = ld_i_meins i_menge = ld_i_menge * i_vbeln = ld_i_vbeln * i_vbelp = ld_i_vbelp * i_date = ld_i_date * i_ibtyp = ld_i_ibtyp * i_umrez = ld_i_umrez * i_umren = ld_i_umren * i_msg = ld_i_msg * i_collect_messages = ld_i_collect_messages * i_ekbeh = ld_i_ekbeh i_new_conf = ld_i_new_conf IMPORTING e_umrez = ld_e_umrez e_umren = ld_e_umren * TABLES * errors = it_errors * t_ekes = it_t_ekes EXCEPTIONS CONFIRMATION_NOT_FOUND = 1 CONVERSION_NOT_POSSIBLE = 2 PO_NOT_FOUND = 3 PO_NOT_VALID = 4 . " ME_CONFIRMATION_CHECK_QUANTITY
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 ELSEIF SY-SUBRC EQ 4. "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_e_umrez  TYPE KOMDLGN-UMVKN ,
ld_i_ebeln  TYPE EKKO-EBELN ,
it_errors  TYPE STANDARD TABLE OF WUEBS ,
wa_errors  LIKE LINE OF it_errors,
ld_e_umren  TYPE KOMDLGN-UMVKN ,
ld_i_ebelp  TYPE EKPO-EBELP ,
it_t_ekes  TYPE STANDARD TABLE OF UEKES ,
wa_t_ekes  LIKE LINE OF it_t_ekes,
ld_i_meins  TYPE EKPO-MEINS ,
ld_i_menge  TYPE EKPO-MENGE ,
ld_i_vbeln  TYPE EKES-VBELN ,
ld_i_vbelp  TYPE EKES-VBELP ,
ld_i_date  TYPE EKES-EINDT ,
ld_i_ibtyp  TYPE T163D-IBTYP ,
ld_i_umrez  TYPE KOMDLGN-UMVKN ,
ld_i_umren  TYPE KOMDLGN-UMVKN ,
ld_i_msg  TYPE STRING ,
ld_i_collect_messages  TYPE XFELD ,
ld_i_ekbeh  TYPE C ,
ld_i_new_conf  TYPE MMPUR_BOOL .


SELECT single EBELN
FROM EKKO
INTO ld_i_ebeln.


"populate fields of struture and append to itab
append wa_errors to it_errors.

SELECT single EBELP
FROM EKPO
INTO ld_i_ebelp.


"populate fields of struture and append to itab
append wa_t_ekes to it_t_ekes.

SELECT single MEINS
FROM EKPO
INTO ld_i_meins.


SELECT single MENGE
FROM EKPO
INTO ld_i_menge.


SELECT single VBELN
FROM EKES
INTO ld_i_vbeln.


SELECT single VBELP
FROM EKES
INTO ld_i_vbelp.


SELECT single EINDT
FROM EKES
INTO ld_i_date.


SELECT single IBTYP
FROM T163D
INTO ld_i_ibtyp.


ld_i_umrez = Check type of data required

ld_i_umren = Check type of data required
ld_i_msg = 'some text here'.
ld_i_collect_messages = 'Check type of data required'.
ld_i_ekbeh = 'Check type of data required'.
ld_i_new_conf = '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_CONFIRMATION_CHECK_QUANTITY or its description.