SAP G_READ_TEXT Function Module for









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

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



Function G_READ_TEXT 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_TEXT'"
EXPORTING
* DATE_VALID = SY-DATUM "Validity date
FIELD = "Field name
* LANGU = SY-LANGU "Language
RECORD_KEY = "Record key for searching for the a
* T800D_TABLE = ' ' "Table for reading table T800D
TABLE = "Table
VALUE = "Value to be Checked

IMPORTING
LTEXT = "Long text
STEXT = "Short text

EXCEPTIONS
NOT_FOUND = 1
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLGUMD_001 Master Data User Exits for Reading Text
EXIT_SAPLGUMD_002 User exits for master data - check value
EXIT_SAPLGUMD_003 Master data user exits for reading value set
EXIT_SAPLGUMD_004 Master data user exits - FREE internally used tables
EXIT_SAPLGUMD_005 User exits for master data - REFRESH internally used tables
EXIT_SAPLGUMD_006 User exits for master data - add record with period-dependent add. info.
EXIT_SAPLGUMD_007 User Exits for Master Data - Derive Record with Period-Independent Info.

IMPORTING Parameters details for G_READ_TEXT

DATE_VALID - Validity date

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

FIELD - Field name

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

LANGU - Language

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

RECORD_KEY - Record key for searching for the a

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

T800D_TABLE - Table for reading table T800D

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

TABLE - Table

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

VALUE - Value to be Checked

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

EXPORTING Parameters details for G_READ_TEXT

LTEXT - Long text

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

STEXT - Short text

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

EXCEPTIONS details

NOT_FOUND - Value Not Valid

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

Copy and paste ABAP code example for G_READ_TEXT 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_ltext  TYPE STRING, "   
lv_not_found  TYPE STRING, "   
lv_date_valid  TYPE RGUMD-DATE_FROM, "   SY-DATUM
lv_field  TYPE RGUMD-FIELD, "   
lv_stext  TYPE RGUMD, "   
lv_langu  TYPE SY-LANGU, "   SY-LANGU
lv_record_key  TYPE ANY, "   
lv_t800d_table  TYPE RGUMD-TABLE, "   SPACE
lv_table  TYPE RGUMD-TABLE, "   
lv_value  TYPE RGUMD-VALUE. "   

  CALL FUNCTION 'G_READ_TEXT'  "
    EXPORTING
         DATE_VALID = lv_date_valid
         FIELD = lv_field
         LANGU = lv_langu
         RECORD_KEY = lv_record_key
         T800D_TABLE = lv_t800d_table
         TABLE = lv_table
         VALUE = lv_value
    IMPORTING
         LTEXT = lv_ltext
         STEXT = lv_stext
    EXCEPTIONS
        NOT_FOUND = 1
. " G_READ_TEXT




ABAP code using 7.40 inline data declarations to call FM G_READ_TEXT

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 DATE_FROM FROM RGUMD INTO @DATA(ld_date_valid).
DATA(ld_date_valid) = SY-DATUM.
 
"SELECT single FIELD FROM RGUMD INTO @DATA(ld_field).
 
 
"SELECT single LANGU FROM SY INTO @DATA(ld_langu).
DATA(ld_langu) = SY-LANGU.
 
 
"SELECT single TABLE FROM RGUMD INTO @DATA(ld_t800d_table).
DATA(ld_t800d_table) = ' '.
 
"SELECT single TABLE FROM RGUMD INTO @DATA(ld_table).
 
"SELECT single VALUE FROM RGUMD INTO @DATA(ld_value).
 


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!