SAP ME_CONFIRMATION_DUNNING_QTY Function Module for NOTRANSL: Liefert mahnrelevante Mengen und Termine einer Position









ME_CONFIRMATION_DUNNING_QTY is a standard me confirmation dunning qty SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Liefert mahnrelevante Mengen und Termine einer Position processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for me confirmation dunning qty FM, simply by entering the name ME_CONFIRMATION_DUNNING_QTY into the relevant SAP transaction such as SE37 or SE38.

Function Group: EINB
Program Name: SAPLEINB
Main Program: SAPLEINB
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ME_CONFIRMATION_DUNNING_QTY pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'ME_CONFIRMATION_DUNNING_QTY'"NOTRANSL: Liefert mahnrelevante Mengen und Termine einer Position
EXPORTING
I_EBELN = "Purchasing Document Number
I_EBELP = "Item Number of Purchasing Document
* I_EINDT = '99991230' "Item Delivery Date
* I_ABRUF_SEL = ' ' "
I_MENGE = "Purchase Order Quantity
I_BSTAE = "Confirmation Control Key
I_FABKZ = "Indicator: Item Relevant to JIT Delivery Schedules

TABLES
XEKET = "Tfr. Structure Sch. Lines for Ord. Acceptance Confirmations
.



IMPORTING Parameters details for ME_CONFIRMATION_DUNNING_QTY

I_EBELN - Purchasing Document Number

Data type: EKKO-EBELN
Optional: No
Call by Reference: No ( called with pass by value option)

I_EBELP - Item Number of Purchasing Document

Data type: EKPO-EBELP
Optional: No
Call by Reference: No ( called with pass by value option)

I_EINDT - Item Delivery Date

Data type: EKET-EINDT
Default: '99991230'
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_ABRUF_SEL -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_MENGE - Purchase Order Quantity

Data type: EKPO-MENGE
Optional: No
Call by Reference: No ( called with pass by value option)

I_BSTAE - Confirmation Control Key

Data type: EKPO-BSTAE
Optional: No
Call by Reference: No ( called with pass by value option)

I_FABKZ - Indicator: Item Relevant to JIT Delivery Schedules

Data type: EKPO-FABKZ
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for ME_CONFIRMATION_DUNNING_QTY

XEKET - Tfr. Structure Sch. Lines for Ord. Acceptance Confirmations

Data type: BEKET
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for ME_CONFIRMATION_DUNNING_QTY Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lt_xeket  TYPE STANDARD TABLE OF BEKET, "   
lv_i_ebeln  TYPE EKKO-EBELN, "   
lv_i_ebelp  TYPE EKPO-EBELP, "   
lv_i_eindt  TYPE EKET-EINDT, "   '99991230'
lv_i_abruf_sel  TYPE EKET, "   SPACE
lv_i_menge  TYPE EKPO-MENGE, "   
lv_i_bstae  TYPE EKPO-BSTAE, "   
lv_i_fabkz  TYPE EKPO-FABKZ. "   

  CALL FUNCTION 'ME_CONFIRMATION_DUNNING_QTY'  "NOTRANSL: Liefert mahnrelevante Mengen und Termine einer Position
    EXPORTING
         I_EBELN = lv_i_ebeln
         I_EBELP = lv_i_ebelp
         I_EINDT = lv_i_eindt
         I_ABRUF_SEL = lv_i_abruf_sel
         I_MENGE = lv_i_menge
         I_BSTAE = lv_i_bstae
         I_FABKZ = lv_i_fabkz
    TABLES
         XEKET = lt_xeket
. " ME_CONFIRMATION_DUNNING_QTY




ABAP code using 7.40 inline data declarations to call FM ME_CONFIRMATION_DUNNING_QTY

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
"SELECT single EBELN FROM EKKO INTO @DATA(ld_i_ebeln).
 
"SELECT single EBELP FROM EKPO INTO @DATA(ld_i_ebelp).
 
"SELECT single EINDT FROM EKET INTO @DATA(ld_i_eindt).
DATA(ld_i_eindt) = '99991230'.
 
DATA(ld_i_abruf_sel) = ' '.
 
"SELECT single MENGE FROM EKPO INTO @DATA(ld_i_menge).
 
"SELECT single BSTAE FROM EKPO INTO @DATA(ld_i_bstae).
 
"SELECT single FABKZ FROM EKPO INTO @DATA(ld_i_fabkz).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!