SAP /SAPSLL/TLEPS_DB_BUF_READ Function Module for









/SAPSLL/TLEPS_DB_BUF_READ is a standard /sapsll/tleps db buf read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 /sapsll/tleps db buf read FM, simply by entering the name /SAPSLL/TLEPS_DB_BUF_READ into the relevant SAP transaction such as SE37 or SE38.

Function Group: /SAPSLL/TLEPS_DB
Program Name: /SAPSLL/SAPLTLEPS_DB
Main Program: /SAPSLL/SAPLTLEPS_DB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function /SAPSLL/TLEPS_DB_BUF_READ 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 '/SAPSLL/TLEPS_DB_BUF_READ'"
EXPORTING
* IS_CRIT = "
IS_DEBUG = "

IMPORTING
ET_RESULT = "

EXCEPTIONS
NO_DATA = 1
.



IMPORTING Parameters details for /SAPSLL/TLEPS_DB_BUF_READ

IS_CRIT -

Data type: /SAPSLL/TLEPS_CRIT_S
Optional: Yes
Call by Reference: Yes

IS_DEBUG -

Data type: /SAPSLL/DEBUG_S
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for /SAPSLL/TLEPS_DB_BUF_READ

ET_RESULT -

Data type: /SAPSLL/TLEPS_T
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NO_DATA -

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

Copy and paste ABAP code example for /SAPSLL/TLEPS_DB_BUF_READ 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_is_crit  TYPE /SAPSLL/TLEPS_CRIT_S, "   
lv_no_data  TYPE /SAPSLL/TLEPS_CRIT_S, "   
lv_et_result  TYPE /SAPSLL/TLEPS_T, "   
lv_is_debug  TYPE /SAPSLL/DEBUG_S. "   

  CALL FUNCTION '/SAPSLL/TLEPS_DB_BUF_READ'  "
    EXPORTING
         IS_CRIT = lv_is_crit
         IS_DEBUG = lv_is_debug
    IMPORTING
         ET_RESULT = lv_et_result
    EXCEPTIONS
        NO_DATA = 1
. " /SAPSLL/TLEPS_DB_BUF_READ




ABAP code using 7.40 inline data declarations to call FM /SAPSLL/TLEPS_DB_BUF_READ

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



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!