SAP ROMT2_OBJTYPE_GET_TEXTS Function Module for









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

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



Function ROMT2_OBJTYPE_GET_TEXTS 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 'ROMT2_OBJTYPE_GET_TEXTS'"
EXPORTING
I_REQUNR = "
* I_CHABASNM = "
* I_MAXSIZE = "
* I_INITFLAG = "
* I_UPDMODE = "
* I_DATAPAKID = "
* I_S_TIMEINT = "

TABLES
* I_T_LANGU = "
* I_T_SELECT = "
* E_T_TEXTS = "
* E_T_BWCO_TX_IOBJSV = "BW Data Collection For CO Object Texts

EXCEPTIONS
NO_MORE_DATA = 1 ERROR_PASSED_TO_MESS_HANDLER = 2
.



IMPORTING Parameters details for ROMT2_OBJTYPE_GET_TEXTS

I_REQUNR -

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

I_CHABASNM -

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

I_MAXSIZE -

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

I_INITFLAG -

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

I_UPDMODE -

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

I_DATAPAKID -

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

I_S_TIMEINT -

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

TABLES Parameters details for ROMT2_OBJTYPE_GET_TEXTS

I_T_LANGU -

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

I_T_SELECT -

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

E_T_TEXTS -

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

E_T_BWCO_TX_IOBJSV - BW Data Collection For CO Object Texts

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

EXCEPTIONS details

NO_MORE_DATA -

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

ERROR_PASSED_TO_MESS_HANDLER -

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

Copy and paste ABAP code example for ROMT2_OBJTYPE_GET_TEXTS 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_langu  TYPE STANDARD TABLE OF SBIWA_T_LANGU, "   
lv_no_more_data  TYPE SBIWA_T_LANGU, "   
lv_i_chabasnm  TYPE SBIWA_S_INTERFACE-CHABASNM, "   
lt_i_t_select  TYPE STANDARD TABLE OF SBIWA_T_SELECT, "   
lv_error_passed_to_mess_handler  TYPE SBIWA_T_SELECT, "   
lt_e_t_texts  TYPE STANDARD TABLE OF SBIWA_T_TEXTS, "   
lv_i_maxsize  TYPE SBIWA_S_INTERFACE-MAXSIZE, "   
lv_i_initflag  TYPE SBIWA_S_INTERFACE-INITFLAG, "   
lt_e_t_bwco_tx_iobjsv  TYPE STANDARD TABLE OF BWCO_TX_IOBJSV, "   
lv_i_updmode  TYPE SBIWA_S_INTERFACE-UPDMODE, "   
lv_i_datapakid  TYPE SBIWA_S_INTERFACE-DATAPAKID, "   
lv_i_s_timeint  TYPE SBIWA_S_TIMEINT. "   

  CALL FUNCTION 'ROMT2_OBJTYPE_GET_TEXTS'  "
    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_DATAPAKID = lv_i_datapakid
         I_S_TIMEINT = lv_i_s_timeint
    TABLES
         I_T_LANGU = lt_i_t_langu
         I_T_SELECT = lt_i_t_select
         E_T_TEXTS = lt_e_t_texts
         E_T_BWCO_TX_IOBJSV = lt_e_t_bwco_tx_iobjsv
    EXCEPTIONS
        NO_MORE_DATA = 1
        ERROR_PASSED_TO_MESS_HANDLER = 2
. " ROMT2_OBJTYPE_GET_TEXTS




ABAP code using 7.40 inline data declarations to call FM ROMT2_OBJTYPE_GET_TEXTS

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 DATAPAKID FROM SBIWA_S_INTERFACE INTO @DATA(ld_i_datapakid).
 
 


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!