SAP PSBW_GET_TEXT_COMPONENT Function Module for NOTRANSL: Template: Übertragung von Texten









PSBW_GET_TEXT_COMPONENT is a standard psbw get text component 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: Template: Übertragung von Texten 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 psbw get text component FM, simply by entering the name PSBW_GET_TEXT_COMPONENT into the relevant SAP transaction such as SE37 or SE38.

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



Function PSBW_GET_TEXT_COMPONENT 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 'PSBW_GET_TEXT_COMPONENT'"NOTRANSL: Template: Übertragung von Texten
EXPORTING
I_REQUNR = "Request Number: Identif. a Data Request
* I_CHABASNM = "Name of Basic Characteristic
* I_MAXSIZE = "Maximum Number of Rows of Output Table
* I_INITFLAG = "Initialization 'X' or Data Transfer ' '
* I_UPDMODE = "Transfer Mode (See Fixed Values for Domain)
* I_RLOGSYS = "Source system of the receiver

TABLES
* I_T_SELECT = "Selection Criteria
* E_T_PSBWCMPTXT = "Output Table with Texts

EXCEPTIONS
NO_MORE_DATA = 1 ERROR_PASSED_TO_MESS_HANDLER = 2
.



IMPORTING Parameters details for PSBW_GET_TEXT_COMPONENT

I_REQUNR - Request Number: Identif. a Data Request

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

I_CHABASNM - Name of Basic Characteristic

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

I_MAXSIZE - Maximum Number of Rows of Output Table

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

I_INITFLAG - Initialization 'X' or Data Transfer ' '

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

I_UPDMODE - Transfer Mode (See Fixed Values for Domain)

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

I_RLOGSYS - Source system of the receiver

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

TABLES Parameters details for PSBW_GET_TEXT_COMPONENT

I_T_SELECT - Selection Criteria

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

E_T_PSBWCMPTXT - Output Table with Texts

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

EXCEPTIONS details

NO_MORE_DATA - Data Was Transferred Completely

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

ERROR_PASSED_TO_MESS_HANDLER - Exit Due to Error; Message in Message Handler

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

Copy and paste ABAP code example for PSBW_GET_TEXT_COMPONENT 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_i_requnr  TYPE SBIWA_S_INTERFACE-REQUNR, "   
lt_i_t_select  TYPE STANDARD TABLE OF SBIWA_T_SELECT, "   
lv_no_more_data  TYPE SBIWA_T_SELECT, "   
lv_i_chabasnm  TYPE SBIWA_S_INTERFACE-CHABASNM, "   
lt_e_t_psbwcmptxt  TYPE STANDARD TABLE OF PSBWCMPTXT, "   
lv_error_passed_to_mess_handler  TYPE PSBWCMPTXT, "   
lv_i_maxsize  TYPE SBIWA_S_INTERFACE-MAXSIZE, "   
lv_i_initflag  TYPE SBIWA_S_INTERFACE-INITFLAG, "   
lv_i_updmode  TYPE SBIWA_S_INTERFACE-UPDMODE, "   
lv_i_rlogsys  TYPE ROOSPRMSC-RLOGSYS. "   

  CALL FUNCTION 'PSBW_GET_TEXT_COMPONENT'  "NOTRANSL: Template: Übertragung von Texten
    EXPORTING
         I_REQUNR = lv_i_requnr
         I_CHABASNM = lv_i_chabasnm
         I_MAXSIZE = lv_i_maxsize
         I_INITFLAG = lv_i_initflag
         I_UPDMODE = lv_i_updmode
         I_RLOGSYS = lv_i_rlogsys
    TABLES
         I_T_SELECT = lt_i_t_select
         E_T_PSBWCMPTXT = lt_e_t_psbwcmptxt
    EXCEPTIONS
        NO_MORE_DATA = 1
        ERROR_PASSED_TO_MESS_HANDLER = 2
. " PSBW_GET_TEXT_COMPONENT




ABAP code using 7.40 inline data declarations to call FM PSBW_GET_TEXT_COMPONENT

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 REQUNR FROM SBIWA_S_INTERFACE INTO @DATA(ld_i_requnr).
 
 
 
"SELECT single CHABASNM FROM SBIWA_S_INTERFACE INTO @DATA(ld_i_chabasnm).
 
 
 
"SELECT single MAXSIZE FROM SBIWA_S_INTERFACE INTO @DATA(ld_i_maxsize).
 
"SELECT single INITFLAG FROM SBIWA_S_INTERFACE INTO @DATA(ld_i_initflag).
 
"SELECT single UPDMODE FROM SBIWA_S_INTERFACE INTO @DATA(ld_i_updmode).
 
"SELECT single RLOGSYS FROM ROOSPRMSC INTO @DATA(ld_i_rlogsys).
 


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!