SAP GET_STAS Function Module for NOTRANSL: liest STAS teilsequentiell

Search SAP Function Modules

GET_STAS is a standard get stas SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: liest STAS teilsequentiell 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 get stas FM, simply by entering the name GET_STAS into the relevant SAP transaction such as SE37 or SE38.

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

Function GET_STAS 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 'GET_STAS'"NOTRANSL: liest STAS teilsequentiell
  EXPORTING
*  ALL = ' ' "
*  DATUB = 00000000 "
*  DATUV = 00000000 "
*  NO_BUFFER = ' ' "ignore buffered data
*  SET = ' ' "
*  VALID = 'X' "
*  WACRD = ' ' "

TABLES
   WA =  "

EXCEPTIONS
   CALL_INVALID = 1    END_OF_TABLE = 2    GET_WITHOUT_SET = 3    KEY_INCOMPLETE = 4    KEY_INVALID = 5    NO_RECORD_FOUND = 6 

.

IMPORTING Parameters details for GET_STAS

ALL -

Data type: CSDATA-XFELD
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

DATUB -

Data type: STAS-DATUV
Default: 00000000
Optional: Yes
Call by Reference: No ( called with pass by value option)

DATUV -

Data type: STAS-DATUV
Default: 00000000
Optional: Yes
Call by Reference: No ( called with pass by value option)

NO_BUFFER - ignore buffered data

Data type: CSDATA-XFELD
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

SET -

Data type: CSDATA-XFELD
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

VALID -

Data type: CSDATA-XFELD
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

WACRD -

Data type: CSDATA-XFELD
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for GET_STAS

WA -

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

EXCEPTIONS details

CALL_INVALID - Parameter combination invalid

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

END_OF_TABLE - no (further) data records selected

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

GET_WITHOUT_SET - Call without previous SET = 'X'

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

KEY_INCOMPLETE - (partial) key incomplete

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

KEY_INVALID - (partial) key invalid

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

NO_RECORD_FOUND - Record not available

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

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

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