SAP MD_SINGLE_ROUNDING Function Module for NOTRANSL: Mengeneinheitenoptimierung und Rundung auf logist. Einheiten
MD_SINGLE_ROUNDING is a standard md single rounding 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: Mengeneinheitenoptimierung und Rundung auf logist. Einheiten 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 single rounding FM, simply by entering the name MD_SINGLE_ROUNDING 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_SINGLE_ROUNDING 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_SINGLE_ROUNDING'"NOTRANSL: Mengeneinheitenoptimierung und Rundung auf logist. Einheiten.
EXPORTING
I_S_GENERAL = "
* I_S_MPN = "
IMPORTING
E_S_RESULTS = "
TABLES
* E_T_ROUND_REASONS = "Reasons for Rounding
EXCEPTIONS
INVALID_OPCODE = 1 ERROR = 10 NO_PURCHASE_ORG = 2 RDPR_NOT_FOUND = 3 MATERIAL_NOT_FOUND = 4 MEINH_NOT_FOUND = 5 BAD_PARAMS = 6 DEBITOR_NOT_FOUND = 7 NO_ROUND = 8 RDPRF_NOT_FOUND = 9
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_SINGLE_ROUNDING
I_S_GENERAL -
Data type: MDR1INSINGLEROUNDOptional: No
Call by Reference: No ( called with pass by value option)
I_S_MPN -
Data type: MDR1INSINGLEROUND_MPNOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for MD_SINGLE_ROUNDING
E_S_RESULTS -
Data type: MDR1OUTSINGLEROUNDOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for MD_SINGLE_ROUNDING
E_T_ROUND_REASONS - Reasons for Rounding
Data type: MDR1TRUNDUNGSGRUNDOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
INVALID_OPCODE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_PURCHASE_ORG -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
RDPR_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MATERIAL_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MEINH_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
BAD_PARAMS - Incorrect input parameters
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DEBITOR_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_ROUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
RDPRF_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for MD_SINGLE_ROUNDING 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_e_s_results | TYPE MDR1OUTSINGLEROUND, " | |||
| lv_i_s_general | TYPE MDR1INSINGLEROUND, " | |||
| lv_invalid_opcode | TYPE MDR1INSINGLEROUND, " | |||
| lt_e_t_round_reasons | TYPE STANDARD TABLE OF MDR1TRUNDUNGSGRUND, " | |||
| lv_error | TYPE MDR1TRUNDUNGSGRUND, " | |||
| lv_i_s_mpn | TYPE MDR1INSINGLEROUND_MPN, " | |||
| lv_no_purchase_org | TYPE MDR1INSINGLEROUND_MPN, " | |||
| lv_rdpr_not_found | TYPE MDR1INSINGLEROUND_MPN, " | |||
| lv_material_not_found | TYPE MDR1INSINGLEROUND_MPN, " | |||
| lv_meinh_not_found | TYPE MDR1INSINGLEROUND_MPN, " | |||
| lv_bad_params | TYPE MDR1INSINGLEROUND_MPN, " | |||
| lv_debitor_not_found | TYPE MDR1INSINGLEROUND_MPN, " | |||
| lv_no_round | TYPE MDR1INSINGLEROUND_MPN, " | |||
| lv_rdprf_not_found | TYPE MDR1INSINGLEROUND_MPN. " |
|   CALL FUNCTION 'MD_SINGLE_ROUNDING' "NOTRANSL: Mengeneinheitenoptimierung und Rundung auf logist. Einheiten |
| EXPORTING | ||
| I_S_GENERAL | = lv_i_s_general | |
| I_S_MPN | = lv_i_s_mpn | |
| IMPORTING | ||
| E_S_RESULTS | = lv_e_s_results | |
| TABLES | ||
| E_T_ROUND_REASONS | = lt_e_t_round_reasons | |
| EXCEPTIONS | ||
| INVALID_OPCODE = 1 | ||
| ERROR = 10 | ||
| NO_PURCHASE_ORG = 2 | ||
| RDPR_NOT_FOUND = 3 | ||
| MATERIAL_NOT_FOUND = 4 | ||
| MEINH_NOT_FOUND = 5 | ||
| BAD_PARAMS = 6 | ||
| DEBITOR_NOT_FOUND = 7 | ||
| NO_ROUND = 8 | ||
| RDPRF_NOT_FOUND = 9 | ||
| . " MD_SINGLE_ROUNDING | ||
ABAP code using 7.40 inline data declarations to call FM MD_SINGLE_ROUNDING
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