SAP READ_T499S Function Module for









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

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



Function READ_T499S 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 'READ_T499S'"
EXPORTING
I_STAND = "
I_WERKS = "

IMPORTING
E_T499S = "

EXCEPTIONS
NOT_FOUND = 1
.



IMPORTING Parameters details for READ_T499S

I_STAND -

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

I_WERKS -

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

EXPORTING Parameters details for READ_T499S

E_T499S -

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

EXCEPTIONS details

NOT_FOUND -

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

Copy and paste ABAP code example for READ_T499S 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_e_t499s  TYPE T499S, "   
lv_i_stand  TYPE T499S-STAND, "   
lv_not_found  TYPE T499S, "   
lv_i_werks  TYPE T499S-WERKS. "   

  CALL FUNCTION 'READ_T499S'  "
    EXPORTING
         I_STAND = lv_i_stand
         I_WERKS = lv_i_werks
    IMPORTING
         E_T499S = lv_e_t499s
    EXCEPTIONS
        NOT_FOUND = 1
. " READ_T499S




ABAP code using 7.40 inline data declarations to call FM READ_T499S

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.

 
"SELECT single STAND FROM T499S INTO @DATA(ld_i_stand).
 
 
"SELECT single WERKS FROM T499S INTO @DATA(ld_i_werks).
 


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!