SAP SPI_LS_READ Function Module for









SPI_LS_READ is a standard spi ls 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 spi ls read FM, simply by entering the name SPI_LS_READ into the relevant SAP transaction such as SE37 or SE38.

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



Function SPI_LS_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 'SPI_LS_READ'"
  EXPORTING
*  IP_CLIENT =  "Client
*  IP_MAX = 1000 "
*  IT_AGENTS =  "
*  IP_TRANSID =  "Transaction ID
   IP_TSTFROM =  "UTC time stamp in long form (YYYYMMDDhhmmssmmmuuun)
   IP_TSTTO =  "UTC time stamp in long form (YYYYMMDDhhmmssmmmuuun)

 IMPORTING
   ET_RECORDS =  "Local Store: Tracking Record Output
   EP_HASMORE =  "Single-Character Flag
   EP_TSTMP =  "UTC time stamp in long form (YYYYMMDDhhmmssmmmuuun)

EXCEPTIONS
   ASTAT_READ_ERROR = 1
.



IMPORTING Parameters details for SPI_LS_READ

IP_CLIENT - Client

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

IP_MAX -

Data type: I
Default: 1000
Optional: Yes
Call by Reference: No ( called with pass by value option)

IT_AGENTS -

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

IP_TRANSID - Transaction ID

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

IP_TSTFROM - UTC time stamp in long form (YYYYMMDDhhmmssmmmuuun)

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

IP_TSTTO - UTC time stamp in long form (YYYYMMDDhhmmssmmmuuun)

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

EXPORTING Parameters details for SPI_LS_READ

ET_RECORDS - Local Store: Tracking Record Output

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

EP_HASMORE - Single-Character Flag

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

EP_TSTMP - UTC time stamp in long form (YYYYMMDDhhmmssmmmuuun)

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

EXCEPTIONS details

ASTAT_READ_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SPI_LS_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_ip_client  TYPE MANDT, "   
lv_et_records  TYPE TSPIROX, "   
lv_astat_read_error  TYPE TSPIROX, "   
lv_ip_max  TYPE I, "   1000
lv_ep_hasmore  TYPE CHAR1, "   
lv_ep_tstmp  TYPE TIMESTAMPL, "   
lv_it_agents  TYPE TSPIAGID, "   
lv_ip_transid  TYPE CHAR32, "   
lv_ip_tstfrom  TYPE TIMESTAMPL, "   
lv_ip_tstto  TYPE TIMESTAMPL. "   

  CALL FUNCTION 'SPI_LS_READ'  "
    EXPORTING
         IP_CLIENT = lv_ip_client
         IP_MAX = lv_ip_max
         IT_AGENTS = lv_it_agents
         IP_TRANSID = lv_ip_transid
         IP_TSTFROM = lv_ip_tstfrom
         IP_TSTTO = lv_ip_tstto
    IMPORTING
         ET_RECORDS = lv_et_records
         EP_HASMORE = lv_ep_hasmore
         EP_TSTMP = lv_ep_tstmp
    EXCEPTIONS
        ASTAT_READ_ERROR = 1
. " SPI_LS_READ




ABAP code using 7.40 inline data declarations to call FM SPI_LS_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.

 
 
 
DATA(ld_ip_max) = 1000.
 
 
 
 
 
 
 


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!