SAP REPORT_TEXTS_GET Function Module for









REPORT_TEXTS_GET is a standard report texts get 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 report texts get FM, simply by entering the name REPORT_TEXTS_GET into the relevant SAP transaction such as SE37 or SE38.

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



Function REPORT_TEXTS_GET 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 'REPORT_TEXTS_GET'"
EXPORTING
VALUEIN1 = "Input value short text
VALUEIN2 = "Input value medium text
VALUEIN3 = "Input value long text
* I_DISPLAY = ' ' "

IMPORTING
ANSWER = "Response
VALUEOUT1 = "Output value short text
VALUEOUT2 = "Output value medium text
VALUEOUT3 = "Output value long text
.



IMPORTING Parameters details for REPORT_TEXTS_GET

VALUEIN1 - Input value short text

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

VALUEIN2 - Input value medium text

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

VALUEIN3 - Input value long text

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

I_DISPLAY -

Data type: CCVALID-XFELD
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for REPORT_TEXTS_GET

ANSWER - Response

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

VALUEOUT1 - Output value short text

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

VALUEOUT2 - Output value medium text

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

VALUEOUT3 - Output value long text

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

Copy and paste ABAP code example for REPORT_TEXTS_GET 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_answer  TYPE C, "   
lv_valuein1  TYPE TKEB2-TXTKZ, "   
lv_valuein2  TYPE TKEB2-TXTMT, "   
lv_valueout1  TYPE TKEB2-TXTKZ, "   
lv_valuein3  TYPE TKEB2-TXTLG, "   
lv_valueout2  TYPE TKEB2-TXTMT, "   
lv_i_display  TYPE CCVALID-XFELD, "   ' '
lv_valueout3  TYPE TKEB2-TXTLG. "   

  CALL FUNCTION 'REPORT_TEXTS_GET'  "
    EXPORTING
         VALUEIN1 = lv_valuein1
         VALUEIN2 = lv_valuein2
         VALUEIN3 = lv_valuein3
         I_DISPLAY = lv_i_display
    IMPORTING
         ANSWER = lv_answer
         VALUEOUT1 = lv_valueout1
         VALUEOUT2 = lv_valueout2
         VALUEOUT3 = lv_valueout3
. " REPORT_TEXTS_GET




ABAP code using 7.40 inline data declarations to call FM REPORT_TEXTS_GET

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 TXTKZ FROM TKEB2 INTO @DATA(ld_valuein1).
 
"SELECT single TXTMT FROM TKEB2 INTO @DATA(ld_valuein2).
 
"SELECT single TXTKZ FROM TKEB2 INTO @DATA(ld_valueout1).
 
"SELECT single TXTLG FROM TKEB2 INTO @DATA(ld_valuein3).
 
"SELECT single TXTMT FROM TKEB2 INTO @DATA(ld_valueout2).
 
"SELECT single XFELD FROM CCVALID INTO @DATA(ld_i_display).
DATA(ld_i_display) = ' '.
 
"SELECT single TXTLG FROM TKEB2 INTO @DATA(ld_valueout3).
 


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!