SAP FRML545_CONV_TO_MAX_UNIT Function Module for NOTRANSL: Konvertiert Positionen auf maximale Einheit









FRML545_CONV_TO_MAX_UNIT is a standard frml545 conv to max 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: Konvertiert Positionen auf maximale Einheit 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 frml545 conv to max unit FM, simply by entering the name FRML545_CONV_TO_MAX_UNIT into the relevant SAP transaction such as SE37 or SE38.

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



Function FRML545_CONV_TO_MAX_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 'FRML545_CONV_TO_MAX_UNIT'"NOTRANSL: Konvertiert Positionen auf maximale Einheit
EXPORTING
IS_ADDINF = "RMS-FRM: Additional Information for Function Module Calls
I_BASE_QTY = "Base Quantity of a Formula
I_BASE_UNIT = "Base Unit of Measure of a Formula

IMPORTING
E_FLG_MESSAGE = "
E_FLG_CANCEL = "
ET_LOG = "RMS-FRM: Messages for Application Log

CHANGING
XT_IOTAB = "RMS-FRM: Screen Structure for LoM - LoRS
XS_KEYPATH = "RMS-FRM: Formula 'Key' Path for Function Module Call

EXCEPTIONS
PARAMETER_ERROR = 1 NO_AUTHORITY = 2 CONVERSION_ERROR = 3 RNAL_ERROR = 4 API_ERROR = 5
.



IMPORTING Parameters details for FRML545_CONV_TO_MAX_UNIT

IS_ADDINF - RMS-FRM: Additional Information for Function Module Calls

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

I_BASE_QTY - Base Quantity of a Formula

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

I_BASE_UNIT - Base Unit of Measure of a Formula

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

EXPORTING Parameters details for FRML545_CONV_TO_MAX_UNIT

E_FLG_MESSAGE -

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

E_FLG_CANCEL -

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

ET_LOG - RMS-FRM: Messages for Application Log

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

CHANGING Parameters details for FRML545_CONV_TO_MAX_UNIT

XT_IOTAB - RMS-FRM: Screen Structure for LoM - LoRS

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

XS_KEYPATH - RMS-FRM: Formula 'Key' Path for Function Module Call

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

EXCEPTIONS details

PARAMETER_ERROR -

Data type:
Optional: No
Call by Reference: Yes

NO_AUTHORITY -

Data type:
Optional: No
Call by Reference: Yes

CONVERSION_ERROR -

Data type:
Optional: No
Call by Reference: Yes

RNAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

API_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FRML545_CONV_TO_MAX_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_xt_iotab  TYPE FRM10_IOT_SCR_TAB, "   
lv_is_addinf  TYPE FRMLS_ADDINF, "   
lv_e_flg_message  TYPE ESP1_BOOLEAN, "   
lv_parameter_error  TYPE ESP1_BOOLEAN, "   
lv_i_base_qty  TYPE FRMLE_BASEQUAN, "   
lv_xs_keypath  TYPE FRMLS_KEYPATH, "   
lv_e_flg_cancel  TYPE ESP1_BOOLEAN, "   
lv_no_authority  TYPE ESP1_BOOLEAN, "   
lv_et_log  TYPE FRMLTY_LOG_REC, "   
lv_i_base_unit  TYPE FRMLE_BASEUNIT, "   
lv_conversion_error  TYPE FRMLE_BASEUNIT, "   
lv_rnal_error  TYPE FRMLE_BASEUNIT, "   
lv_api_error  TYPE FRMLE_BASEUNIT. "   

  CALL FUNCTION 'FRML545_CONV_TO_MAX_UNIT'  "NOTRANSL: Konvertiert Positionen auf maximale Einheit
    EXPORTING
         IS_ADDINF = lv_is_addinf
         I_BASE_QTY = lv_i_base_qty
         I_BASE_UNIT = lv_i_base_unit
    IMPORTING
         E_FLG_MESSAGE = lv_e_flg_message
         E_FLG_CANCEL = lv_e_flg_cancel
         ET_LOG = lv_et_log
    CHANGING
         XT_IOTAB = lv_xt_iotab
         XS_KEYPATH = lv_xs_keypath
    EXCEPTIONS
        PARAMETER_ERROR = 1
        NO_AUTHORITY = 2
        CONVERSION_ERROR = 3
        RNAL_ERROR = 4
        API_ERROR = 5
. " FRML545_CONV_TO_MAX_UNIT




ABAP code using 7.40 inline data declarations to call FM FRML545_CONV_TO_MAX_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!