SAP LE_DSP_RESOLVE_GET_DATA Function Module for Sperren von Belegen

Search SAP Function Modules

LE_DSP_RESOLVE_GET_DATA is a standard le dsp resolve get data 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 resolve get data FM, simply by entering the name LE_DSP_RESOLVE_GET_DATA 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_RESOLVE_GET_DATA 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_RESOLVE_GET_DATA'"Sperren von Belegen
  EXPORTING
   IT_VPOBJ =  "

 IMPORTING
   EF_SUBRC =  "

CHANGING
   WA =  "

EXCEPTIONS
   NOT_AN_UPMOST_HU = 1    NOTHING_TODO = 10    SPLIT_QUANTITY_TO_HIGH = 11    WRONG_CALL = 12    LOCKING_ERROR = 13    PACKED_ITEM = 2    HU_MULTIPLE_SPECIFIED = 3    MULTIPLE_HIGHEST_LEVEL = 4    INTERNAL_ERROR = 5    SPLITPROFILE_NOT_FOUND = 6    TVLK_NOT_FOUND = 7    VARIABEL_ERROR = 8    INCONSISTENT_RES_OLD = 9 

.

IMPORTING Parameters details for LE_DSP_RESOLVE_GET_DATA

IT_VPOBJ -

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

EXPORTING Parameters details for LE_DSP_RESOLVE_GET_DATA

EF_SUBRC -

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

CHANGING Parameters details for LE_DSP_RESOLVE_GET_DATA

WA -

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

EXCEPTIONS details

NOT_AN_UPMOST_HU -

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

NOTHING_TODO -

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

SPLIT_QUANTITY_TO_HIGH -

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

WRONG_CALL -

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

LOCKING_ERROR -

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

PACKED_ITEM -

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

HU_MULTIPLE_SPECIFIED -

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

MULTIPLE_HIGHEST_LEVEL -

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)

SPLITPROFILE_NOT_FOUND -

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

TVLK_NOT_FOUND -

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

VARIABEL_ERROR -

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

INCONSISTENT_RES_OLD -

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

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

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