SAP RS_TEXTPOOL Function Module for









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

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



Function RS_TEXTPOOL 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 'RS_TEXTPOOL'"
EXPORTING
OBJECTNAME = "
* ACTION = 'DISPLAY' "WB Request: Operation within the ABAP Workbench
* TEXTTYPE = "
* TEXTKEY = "
* TEXTENTRY = "
* TEXTLENGTH = "
* STATUS_LDB = ' ' "
* WB_MANAGER = "

IMPORTING
FCODE = "

EXCEPTIONS
OBJECT_NOT_FOUND = 1 PERMISSION_FAILURE = 2 INVALID_PROGRAM_TYPE = 3
.



IMPORTING Parameters details for RS_TEXTPOOL

OBJECTNAME -

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

ACTION - WB Request: Operation within the ABAP Workbench

Data type: SEU_ACTION
Default: 'DISPLAY'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TEXTTYPE -

Data type: TEXTPOOL-ID
Optional: Yes
Call by Reference: No ( called with pass by value option)

TEXTKEY -

Data type: TEXTPOOL-KEY
Optional: Yes
Call by Reference: No ( called with pass by value option)

TEXTENTRY -

Data type: TEXTPOOL-ENTRY
Optional: Yes
Call by Reference: No ( called with pass by value option)

TEXTLENGTH -

Data type: TEXTPOOL-LENGTH
Optional: Yes
Call by Reference: No ( called with pass by value option)

STATUS_LDB -

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

WB_MANAGER -

Data type: IF_WB_MANAGER
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for RS_TEXTPOOL

FCODE -

Data type:
Optional: No
Call by Reference: Yes

EXCEPTIONS details

OBJECT_NOT_FOUND -

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

PERMISSION_FAILURE -

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

INVALID_PROGRAM_TYPE -

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

Copy and paste ABAP code example for RS_TEXTPOOL 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_fcode  TYPE STRING, "   
lv_objectname  TYPE RS38M-PROGRAMM, "   
lv_object_not_found  TYPE RS38M, "   
lv_action  TYPE SEU_ACTION, "   'DISPLAY'
lv_permission_failure  TYPE SEU_ACTION, "   
lv_texttype  TYPE TEXTPOOL-ID, "   
lv_invalid_program_type  TYPE TEXTPOOL, "   
lv_textkey  TYPE TEXTPOOL-KEY, "   
lv_textentry  TYPE TEXTPOOL-ENTRY, "   
lv_textlength  TYPE TEXTPOOL-LENGTH, "   
lv_status_ldb  TYPE TEXTPOOL, "   ' '
lv_wb_manager  TYPE IF_WB_MANAGER. "   

  CALL FUNCTION 'RS_TEXTPOOL'  "
    EXPORTING
         OBJECTNAME = lv_objectname
         ACTION = lv_action
         TEXTTYPE = lv_texttype
         TEXTKEY = lv_textkey
         TEXTENTRY = lv_textentry
         TEXTLENGTH = lv_textlength
         STATUS_LDB = lv_status_ldb
         WB_MANAGER = lv_wb_manager
    IMPORTING
         FCODE = lv_fcode
    EXCEPTIONS
        OBJECT_NOT_FOUND = 1
        PERMISSION_FAILURE = 2
        INVALID_PROGRAM_TYPE = 3
. " RS_TEXTPOOL




ABAP code using 7.40 inline data declarations to call FM RS_TEXTPOOL

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 PROGRAMM FROM RS38M INTO @DATA(ld_objectname).
 
 
DATA(ld_action) = 'DISPLAY'.
 
 
"SELECT single ID FROM TEXTPOOL INTO @DATA(ld_texttype).
 
 
"SELECT single KEY FROM TEXTPOOL INTO @DATA(ld_textkey).
 
"SELECT single ENTRY FROM TEXTPOOL INTO @DATA(ld_textentry).
 
"SELECT single LENGTH FROM TEXTPOOL INTO @DATA(ld_textlength).
 
DATA(ld_status_ldb) = ' '.
 
 


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!