SAP RFC_READ_TEXT Function Module for NOTRANSL: SAPScript Texte lesen
RFC_READ_TEXT is a standard rfc 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 for NOTRANSL: SAPScript Texte lesen 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 rfc read text FM, simply by entering the name RFC_READ_TEXT into the relevant SAP transaction such as SE37 or SE38.
Function Group: CADR
Program Name: SAPLCADR
Main Program: SAPLCADR
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function RFC_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 'RFC_READ_TEXT'"NOTRANSL: SAPScript Texte lesen.
TABLES
TEXT_LINES = "IBIP: Long text line with logical key
* MESSAGES = "Return Parameter(s)
* OBJECTLINKS = "Return Parameter(s)
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_SAPLCADR_001 User Exit: Read drawing head data
TABLES Parameters details for RFC_READ_TEXT
TEXT_LINES - IBIP: Long text line with logical key
Data type: IBIPTEXTLNOptional: No
Call by Reference: Yes
MESSAGES - Return Parameter(s)
Data type: BAPIRET2Optional: Yes
Call by Reference: Yes
OBJECTLINKS - Return Parameter(s)
Data type: BAPI_DOC_DRAD_KEYSOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for RFC_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: | ||||
| lt_text_lines | TYPE STANDARD TABLE OF IBIPTEXTLN, " | |||
| lt_messages | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lt_objectlinks | TYPE STANDARD TABLE OF BAPI_DOC_DRAD_KEYS. " |
|   CALL FUNCTION 'RFC_READ_TEXT' "NOTRANSL: SAPScript Texte lesen |
| TABLES | ||
| TEXT_LINES | = lt_text_lines | |
| MESSAGES | = lt_messages | |
| OBJECTLINKS | = lt_objectlinks | |
| . " RFC_READ_TEXT | ||
ABAP code using 7.40 inline data declarations to call FM RFC_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.Search for further information about these or an SAP related objects