SAP MD_ALLOWED_QUANTITY_UNIT Function Module for NOTRANSL: Bestimmung der erlaubten Mengeneinheiten









MD_ALLOWED_QUANTITY_UNIT is a standard md allowed quantity unit 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: Bestimmung der erlaubten Mengeneinheiten 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 md allowed quantity unit FM, simply by entering the name MD_ALLOWED_QUANTITY_UNIT into the relevant SAP transaction such as SE37 or SE38.

Function Group: MDR1
Program Name: SAPLMDR1
Main Program: SAPLMDR1
Appliation area: W
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function MD_ALLOWED_QUANTITY_UNIT 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 'MD_ALLOWED_QUANTITY_UNIT'"NOTRANSL: Bestimmung der erlaubten Mengeneinheiten
  EXPORTING
   I_S_GENERAL =  "
*  I_S_MARA =  "
*  I_S_EINA =  "
*  I_S_EINE =  "
*  I_S_MARC =  "
*  I_S_MARC_2 =  "
*  I_S_MVKE =  "
*  I_S_KNMT =  "
*  I_S_KNVV =  "

TABLES
   O_T_QT_UNITS =  "

EXCEPTIONS
   BAD_PARAMS = 1    ERROR = 2
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLMDR1_001 User Exit for Removing Invalid UN decimal Points
EXIT_SAPLMDR1_002 User Exit for Defining Allowed Units of Measure
EXIT_SAPLMDR1_003 User Exit for Implementing Customer-Specific Method of Rounding
EXIT_SAPLMDR1_004 User Exit for Customer-Specific Correction of Rounding Result
EXIT_SAPLMDR1_005 User Exit for Customer-Specific Correction of Rounding Parameters

IMPORTING Parameters details for MD_ALLOWED_QUANTITY_UNIT

I_S_GENERAL -

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

I_S_MARA -

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

I_S_EINA -

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

I_S_EINE -

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

I_S_MARC -

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

I_S_MARC_2 -

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

I_S_MVKE -

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

I_S_KNMT -

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

I_S_KNVV -

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

TABLES Parameters details for MD_ALLOWED_QUANTITY_UNIT

O_T_QT_UNITS -

Data type: MDR1TOUTALLOWEDQTUNIT
Optional: No
Call by Reference: Yes

EXCEPTIONS details

BAD_PARAMS - Incorrect input parameters

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

ERROR - Critical Error

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

Copy and paste ABAP code example for MD_ALLOWED_QUANTITY_UNIT 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_bad_params  TYPE STRING, "   
lv_i_s_general  TYPE MDR1INALLOWEDQTUNIT, "   
lt_o_t_qt_units  TYPE STANDARD TABLE OF MDR1TOUTALLOWEDQTUNIT, "   
lv_error  TYPE MDR1TOUTALLOWEDQTUNIT, "   
lv_i_s_mara  TYPE MARA, "   
lv_i_s_eina  TYPE EINA, "   
lv_i_s_eine  TYPE EINE, "   
lv_i_s_marc  TYPE MARC, "   
lv_i_s_marc_2  TYPE MARC, "   
lv_i_s_mvke  TYPE MVKE, "   
lv_i_s_knmt  TYPE KNMT, "   
lv_i_s_knvv  TYPE KNVV. "   

  CALL FUNCTION 'MD_ALLOWED_QUANTITY_UNIT'  "NOTRANSL: Bestimmung der erlaubten Mengeneinheiten
    EXPORTING
         I_S_GENERAL = lv_i_s_general
         I_S_MARA = lv_i_s_mara
         I_S_EINA = lv_i_s_eina
         I_S_EINE = lv_i_s_eine
         I_S_MARC = lv_i_s_marc
         I_S_MARC_2 = lv_i_s_marc_2
         I_S_MVKE = lv_i_s_mvke
         I_S_KNMT = lv_i_s_knmt
         I_S_KNVV = lv_i_s_knvv
    TABLES
         O_T_QT_UNITS = lt_o_t_qt_units
    EXCEPTIONS
        BAD_PARAMS = 1
        ERROR = 2
. " MD_ALLOWED_QUANTITY_UNIT




ABAP code using 7.40 inline data declarations to call FM MD_ALLOWED_QUANTITY_UNIT

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.

 
 
 
 
 
 
 
 
 
 
 
 


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!