SAP LE_DSP_READ_FLUSH Function Module for Sperren von Belegen









LE_DSP_READ_FLUSH is a standard le dsp read flush SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Sperren von Belegen 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 dsp read flush FM, simply by entering the name LE_DSP_READ_FLUSH into the relevant SAP transaction such as SE37 or SE38.

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



Function LE_DSP_READ_FLUSH 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_DSP_READ_FLUSH'"Sperren von Belegen
EXPORTING
* IF_TABNAME = "

IMPORTING
EF_SUBRC = "

CHANGING
WA = "

EXCEPTIONS
NOT_A_VALID_TABNAME = 1 NOT_A_VALID_KEYNAME = 2 NOT_A_VALID_KEY_SEQUENCE = 3 INTERNAL_ERROR = 4
.



IMPORTING Parameters details for LE_DSP_READ_FLUSH

IF_TABNAME -

Data type: LEDSP_RQ-TABNAME
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for LE_DSP_READ_FLUSH

EF_SUBRC -

Data type: SY-SUBRC
Optional: No
Call by Reference: Yes

CHANGING Parameters details for LE_DSP_READ_FLUSH

WA -

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

EXCEPTIONS details

NOT_A_VALID_TABNAME -

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

NOT_A_VALID_KEYNAME -

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

NOT_A_VALID_KEY_SEQUENCE -

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

INTERNAL_ERROR -

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

Copy and paste ABAP code example for LE_DSP_READ_FLUSH 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_wa  TYPE LEDSP_ALL, "   
lv_ef_subrc  TYPE SY-SUBRC, "   
lv_if_tabname  TYPE LEDSP_RQ-TABNAME, "   
lv_not_a_valid_tabname  TYPE LEDSP_RQ, "   
lv_not_a_valid_keyname  TYPE LEDSP_RQ, "   
lv_not_a_valid_key_sequence  TYPE LEDSP_RQ, "   
lv_internal_error  TYPE LEDSP_RQ. "   

  CALL FUNCTION 'LE_DSP_READ_FLUSH'  "Sperren von Belegen
    EXPORTING
         IF_TABNAME = lv_if_tabname
    IMPORTING
         EF_SUBRC = lv_ef_subrc
    CHANGING
         WA = lv_wa
    EXCEPTIONS
        NOT_A_VALID_TABNAME = 1
        NOT_A_VALID_KEYNAME = 2
        NOT_A_VALID_KEY_SEQUENCE = 3
        INTERNAL_ERROR = 4
. " LE_DSP_READ_FLUSH




ABAP code using 7.40 inline data declarations to call FM LE_DSP_READ_FLUSH

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 SUBRC FROM SY INTO @DATA(ld_ef_subrc).
 
"SELECT single TABNAME FROM LEDSP_RQ INTO @DATA(ld_if_tabname).
 
 
 
 
 


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!