SAP SD_TEXT_GET_XSTRING Function Module for NOTRANSL: Lesen DOC/RTF-Text und Konvertierung in XSTRING
SD_TEXT_GET_XSTRING is a standard sd text get xstring 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 DOC/RTF-Text und Konvertierung in XSTRING 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 xstring FM, simply by entering the name SD_TEXT_GET_XSTRING 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_XSTRING 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_XSTRING'"NOTRANSL: Lesen DOC/RTF-Text und Konvertierung in XSTRING.
EXPORTING
IV_ID = "Text ID
IV_SPRAS = "Language Key
* IV_HANDLE = "GUID in 'CHAR' Format in Uppercase
IMPORTING
EV_TEXT_XSTRING = "
EF_ONLY_DISPLAY = "General Indicator
IMPORTING Parameters details for SD_TEXT_GET_XSTRING
IV_ID - Text ID
Data type: TDIDOptional: No
Call by Reference: Yes
IV_SPRAS - Language Key
Data type: SPRASOptional: No
Call by Reference: Yes
IV_HANDLE - GUID in 'CHAR' Format in Uppercase
Data type: GUID_32Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for SD_TEXT_GET_XSTRING
EV_TEXT_XSTRING -
Data type: XSTRINGOptional: No
Call by Reference: Yes
EF_ONLY_DISPLAY - General Indicator
Data type: FLAGOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for SD_TEXT_GET_XSTRING 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_text_xstring | TYPE XSTRING, " | |||
lv_iv_spras | TYPE SPRAS, " | |||
lv_ef_only_display | TYPE FLAG, " | |||
lv_iv_handle | TYPE GUID_32. " |
  CALL FUNCTION 'SD_TEXT_GET_XSTRING' "NOTRANSL: Lesen DOC/RTF-Text und Konvertierung in XSTRING |
EXPORTING | ||
IV_ID | = lv_iv_id | |
IV_SPRAS | = lv_iv_spras | |
IV_HANDLE | = lv_iv_handle | |
IMPORTING | ||
EV_TEXT_XSTRING | = lv_ev_text_xstring | |
EF_ONLY_DISPLAY | = lv_ef_only_display | |
. " SD_TEXT_GET_XSTRING |
ABAP code using 7.40 inline data declarations to call FM SD_TEXT_GET_XSTRING
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