SPI_LS_READ SAP Function module

SPI_LS_READ is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name SPI_LS_READ into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SPILSR
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM SPI_LS_READ - SPI LS READ

CALL FUNCTION 'SPI_LS_READ' "
  EXPORTING
*   ip_client =                 " mandt         Client
*   ip_max = 1000               " i
*   it_agents =                 " tspiagid
*   ip_transid =                " char32        Transaction ID
    ip_tstfrom =                " timestampl    UTC time stamp in long form (YYYYMMDDhhmmssmmmuuun)
    ip_tstto =                  " timestampl    UTC time stamp in long form (YYYYMMDDhhmmssmmmuuun)
  IMPORTING
    et_records =                " tspirox       Local Store: Tracking Record Output
    ep_hasmore =                " char1         Single-Character Flag
    ep_tstmp =                  " timestampl    UTC time stamp in long form (YYYYMMDDhhmmssmmmuuun)
  EXCEPTIONS
    ASTAT_READ_ERROR = 1        "
    .  "  SPI_LS_READ

ABAP code example for Function Module SPI_LS_READ

The ABAP code below is a full code listing to execute function module SPI_LS_READ including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_et_records  
 
 TYPE TSPIROX
,
ld_ep_hasmore  
 
 TYPE CHAR1
,
ld_ep_tstmp  
 
 TYPE TIMESTAMPL
.


DATA(ld_ip_client) = 'Check type of data required'.

DATA(ld_ip_max) = 'Check type of data required'.

DATA(ld_it_agents) = 'Check type of data required'.

DATA(ld_ip_transid) = 'Check type of data required'.

DATA(ld_ip_tstfrom) = 'Check type of data required'.

DATA(ld_ip_tstto) = 'Check type of data required'.
.

CALL FUNCTION 'SPI_LS_READ'
  EXPORTING
*   ip_client =                  ld_ip_client
*   ip_max =                     ld_ip_max
*   it_agents =                  ld_it_agents
*   ip_transid =                 ld_ip_transid
    ip_tstfrom =                 ld_ip_tstfrom
    ip_tstto =                   ld_ip_tstto
  IMPORTING
    et_records =                 ld_et_records
    ep_hasmore =                 ld_ep_hasmore
    ep_tstmp =                   ld_ep_tstmp
  EXCEPTIONS
    ASTAT_READ_ERROR =           1
    .  "  SPI_LS_READ

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_et_records
 
 TYPE TSPIROX ,
ld_ip_client
 
 TYPE MANDT ,
ld_ep_hasmore
 
 TYPE CHAR1 ,
ld_ip_max
 
 TYPE I ,
ld_ep_tstmp
 
 TYPE TIMESTAMPL ,
ld_it_agents
 
 TYPE TSPIAGID ,
ld_ip_transid
 
 TYPE CHAR32 ,
ld_ip_tstfrom
 
 TYPE TIMESTAMPL ,
ld_ip_tstto
 
 TYPE TIMESTAMPL .


ld_ip_client = 'Check type of data required'.
ld_ip_max = 'Check type of data required'.
ld_it_agents = 'Check type of data required'.
ld_ip_transid = 'Check type of data required'.
ld_ip_tstfrom = 'Check type of data required'.
ld_ip_tstto = 'Check type of data required'.