SAP G_READ_STANDARD_LAYOUT Function Module for Read Standard Layout









G_READ_STANDARD_LAYOUT is a standard g read standard layout SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read Standard Layout 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 g read standard layout FM, simply by entering the name G_READ_STANDARD_LAYOUT into the relevant SAP transaction such as SE37 or SE38.

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



Function G_READ_STANDARD_LAYOUT 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 'G_READ_STANDARD_LAYOUT'"Read Standard Layout
EXPORTING
* LANGUAGE = SY-LANGU "Maintenance language
STANDARD_LAYOUT = "Old standard layout

IMPORTING
E_T801W = "Language-dependent parameters
E_T801X = "Language-independent parameters

EXCEPTIONS
SL_NOT_EXIST = 1
.



IMPORTING Parameters details for G_READ_STANDARD_LAYOUT

LANGUAGE - Maintenance language

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

STANDARD_LAYOUT - Old standard layout

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

EXPORTING Parameters details for G_READ_STANDARD_LAYOUT

E_T801W - Language-dependent parameters

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

E_T801X - Language-independent parameters

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

EXCEPTIONS details

SL_NOT_EXIST -

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

Copy and paste ABAP code example for G_READ_STANDARD_LAYOUT 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_t801w  TYPE T801W, "   
lv_language  TYPE SY-LANGU, "   SY-LANGU
lv_sl_not_exist  TYPE SY, "   
lv_e_t801x  TYPE T801X, "   
lv_standard_layout  TYPE T800-DEFAU. "   

  CALL FUNCTION 'G_READ_STANDARD_LAYOUT'  "Read Standard Layout
    EXPORTING
         LANGUAGE = lv_language
         STANDARD_LAYOUT = lv_standard_layout
    IMPORTING
         E_T801W = lv_e_t801w
         E_T801X = lv_e_t801x
    EXCEPTIONS
        SL_NOT_EXIST = 1
. " G_READ_STANDARD_LAYOUT




ABAP code using 7.40 inline data declarations to call FM G_READ_STANDARD_LAYOUT

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 LANGU FROM SY INTO @DATA(ld_language).
DATA(ld_language) = SY-LANGU.
 
 
 
"SELECT single DEFAU FROM T800 INTO @DATA(ld_standard_layout).
 


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!