SAP ME_CONFIRMATION_DELIVERY_TYPE Function Module for NOTRANSL: Ermitteln Zuordnung Bestätigungstyp zu Lieferart









ME_CONFIRMATION_DELIVERY_TYPE is a standard me confirmation delivery type 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: Ermitteln Zuordnung Bestätigungstyp zu Lieferart 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 delivery type FM, simply by entering the name ME_CONFIRMATION_DELIVERY_TYPE 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_DELIVERY_TYPE 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_DELIVERY_TYPE'"NOTRANSL: Ermitteln Zuordnung Bestätigungstyp zu Lieferart
EXPORTING
* I_FUNC = ' ' "
* IV_FLS_RSTO = "
* IV_CCOMP = "Posting Logic in the Case of Stock Transfers
* IV_SIT = ' ' "

CHANGING
* C_IBTYP = ' ' "
* C_LFART = ' ' "
* C_EBTYP = ' ' "Confirmation Category

EXCEPTIONS
FUNCTION_NOT_VALID = 1 PARAM_VALUE_MISSING = 2 NO_ITEM_FOUND = 3
.



IMPORTING Parameters details for ME_CONFIRMATION_DELIVERY_TYPE

I_FUNC -

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

IV_FLS_RSTO -

Data type: EKPO-FLS_RSTO
Optional: Yes
Call by Reference: Yes

IV_CCOMP - Posting Logic in the Case of Stock Transfers

Data type: EKPO-CCOMP
Optional: Yes
Call by Reference: Yes

IV_SIT -

Data type: XFELD
Default: SPACE
Optional: Yes
Call by Reference: Yes

CHANGING Parameters details for ME_CONFIRMATION_DELIVERY_TYPE

C_IBTYP -

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

C_LFART -

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

C_EBTYP - Confirmation Category

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

EXCEPTIONS details

FUNCTION_NOT_VALID -

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

PARAM_VALUE_MISSING -

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

NO_ITEM_FOUND -

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

Copy and paste ABAP code example for ME_CONFIRMATION_DELIVERY_TYPE 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:
lv_i_func  TYPE STRING, "   SPACE
lv_c_ibtyp  TYPE T163D-IBTYP, "   SPACE
lv_function_not_valid  TYPE T163D, "   
lv_c_lfart  TYPE LIKP-LFART, "   SPACE
lv_iv_fls_rsto  TYPE EKPO-FLS_RSTO, "   
lv_param_value_missing  TYPE EKPO, "   
lv_c_ebtyp  TYPE T163D-EBTYP, "   SPACE
lv_iv_ccomp  TYPE EKPO-CCOMP, "   
lv_no_item_found  TYPE EKPO, "   
lv_iv_sit  TYPE XFELD. "   SPACE

  CALL FUNCTION 'ME_CONFIRMATION_DELIVERY_TYPE'  "NOTRANSL: Ermitteln Zuordnung Bestätigungstyp zu Lieferart
    EXPORTING
         I_FUNC = lv_i_func
         IV_FLS_RSTO = lv_iv_fls_rsto
         IV_CCOMP = lv_iv_ccomp
         IV_SIT = lv_iv_sit
    CHANGING
         C_IBTYP = lv_c_ibtyp
         C_LFART = lv_c_lfart
         C_EBTYP = lv_c_ebtyp
    EXCEPTIONS
        FUNCTION_NOT_VALID = 1
        PARAM_VALUE_MISSING = 2
        NO_ITEM_FOUND = 3
. " ME_CONFIRMATION_DELIVERY_TYPE




ABAP code using 7.40 inline data declarations to call FM ME_CONFIRMATION_DELIVERY_TYPE

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.

DATA(ld_i_func) = ' '.
 
"SELECT single IBTYP FROM T163D INTO @DATA(ld_c_ibtyp).
DATA(ld_c_ibtyp) = ' '.
 
 
"SELECT single LFART FROM LIKP INTO @DATA(ld_c_lfart).
DATA(ld_c_lfart) = ' '.
 
"SELECT single FLS_RSTO FROM EKPO INTO @DATA(ld_iv_fls_rsto).
 
 
"SELECT single EBTYP FROM T163D INTO @DATA(ld_c_ebtyp).
DATA(ld_c_ebtyp) = ' '.
 
"SELECT single CCOMP FROM EKPO INTO @DATA(ld_iv_ccomp).
 
 
DATA(ld_iv_sit) = ' '.
 


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!