SAP SD_TEXT_GET_STRING Function Module for NOTRANSL: Lesen Text und Konvertierung in Text-Stream









SD_TEXT_GET_STRING is a standard sd text get string 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: Lesen Text und Konvertierung in Text-Stream 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 sd text get string FM, simply by entering the name SD_TEXT_GET_STRING into the relevant SAP transaction such as SE37 or SE38.

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



Function SD_TEXT_GET_STRING 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 'SD_TEXT_GET_STRING'"NOTRANSL: Lesen Text und Konvertierung in Text-Stream
EXPORTING
IV_ID = "Text ID
IV_SPRAS = "Language Key

IMPORTING
EV_FIRST_TLINE = "
EV_TEXT_STRING = "
EF_MULTIPLE_LINES = "General Indicator
EF_ONLY_DISPLAY = "General Indicator
EF_WITH_FORMAT = "General Indicator
.



IMPORTING Parameters details for SD_TEXT_GET_STRING

IV_ID - Text ID

Data type: TDID
Optional: No
Call by Reference: Yes

IV_SPRAS - Language Key

Data type: SPRAS
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for SD_TEXT_GET_STRING

EV_FIRST_TLINE -

Data type: STRING
Optional: No
Call by Reference: Yes

EV_TEXT_STRING -

Data type: STRING
Optional: No
Call by Reference: Yes

EF_MULTIPLE_LINES - General Indicator

Data type: FLAG
Optional: No
Call by Reference: Yes

EF_ONLY_DISPLAY - General Indicator

Data type: FLAG
Optional: No
Call by Reference: Yes

EF_WITH_FORMAT - General Indicator

Data type: FLAG
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SD_TEXT_GET_STRING 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_iv_id  TYPE TDID, "   
lv_ev_first_tline  TYPE STRING, "   
lv_iv_spras  TYPE SPRAS, "   
lv_ev_text_string  TYPE STRING, "   
lv_ef_multiple_lines  TYPE FLAG, "   
lv_ef_only_display  TYPE FLAG, "   
lv_ef_with_format  TYPE FLAG. "   

  CALL FUNCTION 'SD_TEXT_GET_STRING'  "NOTRANSL: Lesen Text und Konvertierung in Text-Stream
    EXPORTING
         IV_ID = lv_iv_id
         IV_SPRAS = lv_iv_spras
    IMPORTING
         EV_FIRST_TLINE = lv_ev_first_tline
         EV_TEXT_STRING = lv_ev_text_string
         EF_MULTIPLE_LINES = lv_ef_multiple_lines
         EF_ONLY_DISPLAY = lv_ef_only_display
         EF_WITH_FORMAT = lv_ef_with_format
. " SD_TEXT_GET_STRING




ABAP code using 7.40 inline data declarations to call FM SD_TEXT_GET_STRING

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



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!