SAP READ_STYLE Function Module for









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

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



Function READ_STYLE 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_STYLE'"
  EXPORTING
*  CLIENT = SY-MANDT "
*  LANGUAGE = SY-LANGU "
*  OLANGUAGE = ' ' "
*  OSTATUS = ' ' "
*  STATUS = ' ' "
*  STYLE = ' ' "
*  THROUGHCLIENT = ' ' "
*  THROUGHLANGUAGE = ' ' "

 IMPORTING
   FOUND =  "
   OLANGUAGE =  "
   STYLE_HEADER =  "

TABLES
   PARAGRAPHS =  "
   STRINGS =  "
   TABS =  "
.



IMPORTING Parameters details for READ_STYLE

CLIENT -

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

LANGUAGE -

Data type: SY-LANGU
Default: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)

OLANGUAGE -

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

OSTATUS -

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

STATUS -

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

STYLE -

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

THROUGHCLIENT -

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

THROUGHLANGUAGE -

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

EXPORTING Parameters details for READ_STYLE

FOUND -

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

OLANGUAGE -

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

STYLE_HEADER -

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

TABLES Parameters details for READ_STYLE

PARAGRAPHS -

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

STRINGS -

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

TABS -

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

Copy and paste ABAP code example for READ_STYLE 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_found  TYPE STRING, "   
lv_client  TYPE SY-MANDT, "   SY-MANDT
lt_paragraphs  TYPE STANDARD TABLE OF ITCDP, "   
lt_strings  TYPE STANDARD TABLE OF ITCDS, "   
lv_language  TYPE SY-LANGU, "   SY-LANGU
lv_olanguage  TYPE SY-LANGU, "   
lt_tabs  TYPE STANDARD TABLE OF ITCDQ, "   
lv_olanguage  TYPE SY-LANGU, "   SPACE
lv_style_header  TYPE ITCDA, "   
lv_ostatus  TYPE ITCDA-TDSTATUS, "   SPACE
lv_status  TYPE ITCDA-TDSTATUS, "   SPACE
lv_style  TYPE ITCDA-TDSTYLE, "   SPACE
lv_throughclient  TYPE ITCDA, "   SPACE
lv_throughlanguage  TYPE ITCDA. "   SPACE

  CALL FUNCTION 'READ_STYLE'  "
    EXPORTING
         CLIENT = lv_client
         LANGUAGE = lv_language
         OLANGUAGE = lv_olanguage
         OSTATUS = lv_ostatus
         STATUS = lv_status
         STYLE = lv_style
         THROUGHCLIENT = lv_throughclient
         THROUGHLANGUAGE = lv_throughlanguage
    IMPORTING
         FOUND = lv_found
         OLANGUAGE = lv_olanguage
         STYLE_HEADER = lv_style_header
    TABLES
         PARAGRAPHS = lt_paragraphs
         STRINGS = lt_strings
         TABS = lt_tabs
. " READ_STYLE




ABAP code using 7.40 inline data declarations to call FM READ_STYLE

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 MANDT FROM SY INTO @DATA(ld_client).
DATA(ld_client) = SY-MANDT.
 
 
 
"SELECT single LANGU FROM SY INTO @DATA(ld_language).
DATA(ld_language) = SY-LANGU.
 
"SELECT single LANGU FROM SY INTO @DATA(ld_olanguage).
 
 
"SELECT single LANGU FROM SY INTO @DATA(ld_olanguage).
DATA(ld_olanguage) = ' '.
 
 
"SELECT single TDSTATUS FROM ITCDA INTO @DATA(ld_ostatus).
DATA(ld_ostatus) = ' '.
 
"SELECT single TDSTATUS FROM ITCDA INTO @DATA(ld_status).
DATA(ld_status) = ' '.
 
"SELECT single TDSTYLE FROM ITCDA INTO @DATA(ld_style).
DATA(ld_style) = ' '.
 
DATA(ld_throughclient) = ' '.
 
DATA(ld_throughlanguage) = ' '.
 


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!