SAP SOTR_SERV_TABLE_TO_STRING Function Module for Convert Table to String









SOTR_SERV_TABLE_TO_STRING is a standard sotr serv table to string SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Convert Table to String 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 sotr serv table to string FM, simply by entering the name SOTR_SERV_TABLE_TO_STRING into the relevant SAP transaction such as SE37 or SE38.

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



Function SOTR_SERV_TABLE_TO_STRING 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 'SOTR_SERV_TABLE_TO_STRING'"Convert Table to String
EXPORTING
* FLAG_NO_LINE_BREAKS = 'X' "Flag (X or blank)
* LINE_LENGTH = "
* LANGU = SY-LANGU "SAP R/3 System, Current Language

IMPORTING
TEXT = "

TABLES
TEXT_TAB = "
.



IMPORTING Parameters details for SOTR_SERV_TABLE_TO_STRING

FLAG_NO_LINE_BREAKS - Flag (X or blank)

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

LINE_LENGTH -

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

LANGU - SAP R/3 System, Current Language

Data type: SYLANGU
Default: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for SOTR_SERV_TABLE_TO_STRING

TEXT -

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

TABLES Parameters details for SOTR_SERV_TABLE_TO_STRING

TEXT_TAB -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for SOTR_SERV_TABLE_TO_STRING 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_text  TYPE STRING, "   
lt_text_tab  TYPE STANDARD TABLE OF STRING, "   
lv_flag_no_line_breaks  TYPE AS4FLAG, "   'X'
lv_line_length  TYPE I, "   
lv_langu  TYPE SYLANGU. "   SY-LANGU

  CALL FUNCTION 'SOTR_SERV_TABLE_TO_STRING'  "Convert Table to String
    EXPORTING
         FLAG_NO_LINE_BREAKS = lv_flag_no_line_breaks
         LINE_LENGTH = lv_line_length
         LANGU = lv_langu
    IMPORTING
         TEXT = lv_text
    TABLES
         TEXT_TAB = lt_text_tab
. " SOTR_SERV_TABLE_TO_STRING




ABAP code using 7.40 inline data declarations to call FM SOTR_SERV_TABLE_TO_STRING

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.

 
 
DATA(ld_flag_no_line_breaks) = 'X'.
 
 
DATA(ld_langu) = SY-LANGU.
 


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!