SAP LM_DPS_END Function Module for End for Financial Objects (Mass Processing)
LM_DPS_END is a standard lm dps end SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for End for Financial Objects (Mass Processing) 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 lm dps end FM, simply by entering the name LM_DPS_END into the relevant SAP transaction such as SE37 or SE38.
Function Group: LMDPS
Program Name: SAPLLMDPS
Main Program: SAPLLMDPS
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function LM_DPS_END 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 'LM_DPS_END'"End for Financial Objects (Mass Processing).
EXPORTING
I_PROG_CONTROLS = "Control Parameters of Function Module
TABLES
IT_ERROR = "Message Table
EXCEPTIONS
ERROR = 1
IMPORTING Parameters details for LM_DPS_END
I_PROG_CONTROLS - Control Parameters of Function Module
Data type: JBDPS_PROG_CONTROLSOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for LM_DPS_END
IT_ERROR - Message Table
Data type: SPROT_XOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR - Fatal Error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for LM_DPS_END 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_error | TYPE STRING, " | |||
| lt_it_error | TYPE STANDARD TABLE OF SPROT_X, " | |||
| lv_i_prog_controls | TYPE JBDPS_PROG_CONTROLS. " |
|   CALL FUNCTION 'LM_DPS_END' "End for Financial Objects (Mass Processing) |
| EXPORTING | ||
| I_PROG_CONTROLS | = lv_i_prog_controls | |
| TABLES | ||
| IT_ERROR | = lt_it_error | |
| EXCEPTIONS | ||
| ERROR = 1 | ||
| . " LM_DPS_END | ||
ABAP code using 7.40 inline data declarations to call FM LM_DPS_END
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