SAP LMFO_LO_EVT_SAVE_REQ Function Module for Test: Was data changed? Limit Part for FO Integration in Loans Management

Search SAP Function Modules

LMFO_LO_EVT_SAVE_REQ is a standard lmfo lo evt save req SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Test: Was data changed? Limit Part for FO Integration in Loans Management 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 lmfo lo evt save req FM, simply by entering the name LMFO_LO_EVT_SAVE_REQ into the relevant SAP transaction such as SE37 or SE38.

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

Function LMFO_LO_EVT_SAVE_REQ 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 'LMFO_LO_EVT_SAVE_REQ'"Test: Was data changed? Limit Part for FO Integration in Loans Management
  EXPORTING
*  L_EXPORT_RELEVANT =  "Indicator for Export Relevance (Basel II)
*  L_EXPORT_ACTIVE =  "Indicator: Export Is Active

 IMPORTING
   E_FLG_SAVE =  "

CHANGING
*  L_CHANGE_RELEVANT =  "Indicator for Change Relevance Basel II/IAS

.

IMPORTING Parameters details for LMFO_LO_EVT_SAVE_REQ

L_EXPORT_RELEVANT - Indicator for Export Relevance (Basel II)

Data type: JBDEXPRELFLG
Optional: Yes
Call by Reference: Yes

L_EXPORT_ACTIVE - Indicator: Export Is Active

Data type: JBD_DTE_EXPACT
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for LMFO_LO_EVT_SAVE_REQ

E_FLG_SAVE -

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

CHANGING Parameters details for LMFO_LO_EVT_SAVE_REQ

L_CHANGE_RELEVANT - Indicator for Change Relevance Basel II/IAS

Data type: JBDAENDRELFLG
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for LMFO_LO_EVT_SAVE_REQ 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.

ABAP code using 7.40 inline data declarations to call FM LMFO_LO_EVT_SAVE_REQ

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