SAP LE_MOB_PRINT Function Module for Print from RF transactions
LE_MOB_PRINT is a standard le mob print SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Print from RF transactions 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 le mob print FM, simply by entering the name LE_MOB_PRINT into the relevant SAP transaction such as SE37 or SE38.
Function Group: LMGT
Program Name: SAPLLMGT
Main Program: SAPLLMGT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function LE_MOB_PRINT 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 'LE_MOB_PRINT'"Print from RF transactions.
EXPORTING
I_OK_CODE = "
I_PRINT_PARM = "
EXCEPTIONS
PRINT_NOT_ENABLED = 1 GENERAL_FAILURE = 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_SAPLLMGT_001 Extension for barcode translation
EXIT_SAPLLMGT_083 User exit for print
IMPORTING Parameters details for LE_MOB_PRINT
I_OK_CODE -
Data type: COptional: No
Call by Reference: Yes
I_PRINT_PARM -
Data type: COptional: No
Call by Reference: Yes
EXCEPTIONS details
PRINT_NOT_ENABLED -
Data type:Optional: No
Call by Reference: Yes
GENERAL_FAILURE -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for LE_MOB_PRINT 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_ok_code | TYPE C, " | |||
| lv_print_not_enabled | TYPE C, " | |||
| lv_i_print_parm | TYPE C, " | |||
| lv_general_failure | TYPE C. " |
|   CALL FUNCTION 'LE_MOB_PRINT' "Print from RF transactions |
| EXPORTING | ||
| I_OK_CODE | = lv_i_ok_code | |
| I_PRINT_PARM | = lv_i_print_parm | |
| EXCEPTIONS | ||
| PRINT_NOT_ENABLED = 1 | ||
| GENERAL_FAILURE = 2 | ||
| . " LE_MOB_PRINT | ||
ABAP code using 7.40 inline data declarations to call FM LE_MOB_PRINT
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