SAP FCOM_MON_LINE_DATA_GET Function Module for Return all LineItem data for one user
FCOM_MON_LINE_DATA_GET is a standard fcom mon line data get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Return all LineItem data for one user 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 fcom mon line data get FM, simply by entering the name FCOM_MON_LINE_DATA_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: FCOM_MON_LINE_EXT
Program Name: SAPLFCOM_MON_LINE_EXT
Main Program: SAPLFCOM_MON_LINE_EXT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function FCOM_MON_LINE_DATA_GET 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 'FCOM_MON_LINE_DATA_GET'"Return all LineItem data for one user.
EXPORTING
ID_MONAPPL = "Monitor Application
* ID_UNAME = SY-UNAME "SAP System, User Logon Name
* ID_RULEID = "Rule Number
IMPORTING
ED_EVALDATE = "ABAP Time Stamp
TABLES
ET_DATA_TOP = "External Format of Line Item Results
ET_RETURN = "Return Parameter
ET_TCURX = "Decimal Places in Currencies
ET_DATA = "External Format of Line Item Results
ET_DETAIL = "Details on Line Item
ET_DFIES = "DD: Field List
IMPORTING Parameters details for FCOM_MON_LINE_DATA_GET
ID_MONAPPL - Monitor Application
Data type: FPB_MONAPPLOptional: No
Call by Reference: No ( called with pass by value option)
ID_UNAME - SAP System, User Logon Name
Data type: SY-UNAMEDefault: SY-UNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)
ID_RULEID - Rule Number
Data type: FPB_RULEIDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FCOM_MON_LINE_DATA_GET
ED_EVALDATE - ABAP Time Stamp
Data type: ABSTAMPOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for FCOM_MON_LINE_DATA_GET
ET_DATA_TOP - External Format of Line Item Results
Data type: FPB_S_LINE_DATA_EXT_TOPOptional: No
Call by Reference: Yes
ET_RETURN - Return Parameter
Data type: BAPIRETURN1Optional: No
Call by Reference: Yes
ET_TCURX - Decimal Places in Currencies
Data type: TCURXOptional: No
Call by Reference: Yes
ET_DATA - External Format of Line Item Results
Data type: FPB_S_LINE_DATA_EXT_DETAILOptional: No
Call by Reference: Yes
ET_DETAIL - Details on Line Item
Data type: FCOM_S_LINE_DETAIL_EXTOptional: No
Call by Reference: Yes
ET_DFIES - DD: Field List
Data type: DDFIELDSOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FCOM_MON_LINE_DATA_GET 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_id_monappl | TYPE FPB_MONAPPL, " | |||
| lv_ed_evaldate | TYPE ABSTAMP, " | |||
| lt_et_data_top | TYPE STANDARD TABLE OF FPB_S_LINE_DATA_EXT_TOP, " | |||
| lv_id_uname | TYPE SY-UNAME, " SY-UNAME | |||
| lt_et_return | TYPE STANDARD TABLE OF BAPIRETURN1, " | |||
| lt_et_tcurx | TYPE STANDARD TABLE OF TCURX, " | |||
| lv_id_ruleid | TYPE FPB_RULEID, " | |||
| lt_et_data | TYPE STANDARD TABLE OF FPB_S_LINE_DATA_EXT_DETAIL, " | |||
| lt_et_detail | TYPE STANDARD TABLE OF FCOM_S_LINE_DETAIL_EXT, " | |||
| lt_et_dfies | TYPE STANDARD TABLE OF DDFIELDS. " |
|   CALL FUNCTION 'FCOM_MON_LINE_DATA_GET' "Return all LineItem data for one user |
| EXPORTING | ||
| ID_MONAPPL | = lv_id_monappl | |
| ID_UNAME | = lv_id_uname | |
| ID_RULEID | = lv_id_ruleid | |
| IMPORTING | ||
| ED_EVALDATE | = lv_ed_evaldate | |
| TABLES | ||
| ET_DATA_TOP | = lt_et_data_top | |
| ET_RETURN | = lt_et_return | |
| ET_TCURX | = lt_et_tcurx | |
| ET_DATA | = lt_et_data | |
| ET_DETAIL | = lt_et_detail | |
| ET_DFIES | = lt_et_dfies | |
| . " FCOM_MON_LINE_DATA_GET | ||
ABAP code using 7.40 inline data declarations to call FM FCOM_MON_LINE_DATA_GET
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.| "SELECT single UNAME FROM SY INTO @DATA(ld_id_uname). | ||||
| DATA(ld_id_uname) | = SY-UNAME. | |||
Search for further information about these or an SAP related objects