SAP SWU_GET_TASK_TEXTLINES Function Module for









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

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



Function SWU_GET_TASK_TEXTLINES 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 'SWU_GET_TASK_TEXTLINES'"
EXPORTING
TASK = "
* WI_ID = "
* WIHEADER = "
USAGE = "
* LINEWIDTH = 75 "
* LANGUAGE = SY-LANGU "
* CONTAINER_HANDLE = "Container - Implementation of a 'Collection'
* CONTEXT = ' ' "
* HTML_ESCAPE_FORMAT = "

TABLES
* ASCII_TEXT_LINES = "
* CONTAINER = "
* HTML_TEXT_LINES = "
* ITF_TEXT_LINES = "
* STREAM_TEXT_LINES = "
* COMMAND_LINES = "

EXCEPTIONS
WRONG_USAGE = 1 TEXT_NOT_FOUND = 2 TEXT_SYSTEM_ERROR = 3
.



IMPORTING Parameters details for SWU_GET_TASK_TEXTLINES

TASK -

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

WI_ID -

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

WIHEADER -

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

USAGE -

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

LINEWIDTH -

Data type: THEAD-TDLINESIZE
Default: 75
Optional: Yes
Call by Reference: No ( called with pass by value option)

LANGUAGE -

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

CONTAINER_HANDLE - Container - Implementation of a 'Collection'

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

CONTEXT -

Data type: CHAR1
Default: SPACE
Optional: Yes
Call by Reference: Yes

HTML_ESCAPE_FORMAT -

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

TABLES Parameters details for SWU_GET_TASK_TEXTLINES

ASCII_TEXT_LINES -

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

CONTAINER -

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

HTML_TEXT_LINES -

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

ITF_TEXT_LINES -

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

STREAM_TEXT_LINES -

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

COMMAND_LINES -

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

EXCEPTIONS details

WRONG_USAGE -

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

TEXT_NOT_FOUND -

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

TEXT_SYSTEM_ERROR -

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

Copy and paste ABAP code example for SWU_GET_TASK_TEXTLINES 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_task  TYPE RHOBJECTS-OBJECT, "   
lv_wrong_usage  TYPE RHOBJECTS, "   
lt_ascii_text_lines  TYPE STANDARD TABLE OF TLINE, "   
lv_wi_id  TYPE SWWWIHEAD-WI_ID, "   
lt_container  TYPE STANDARD TABLE OF SWCONT, "   
lv_text_not_found  TYPE SWCONT, "   
lv_wiheader  TYPE SWWWIHEAD, "   
lt_html_text_lines  TYPE STANDARD TABLE OF HTMLLINE, "   
lv_text_system_error  TYPE HTMLLINE, "   
lv_usage  TYPE SWWWIHEAD-WI_TYPE, "   
lt_itf_text_lines  TYPE STANDARD TABLE OF TLINE, "   
lv_linewidth  TYPE THEAD-TDLINESIZE, "   75
lt_stream_text_lines  TYPE STANDARD TABLE OF SWR_TXTLIN, "   
lv_language  TYPE SY-LANGU, "   SY-LANGU
lt_command_lines  TYPE STANDARD TABLE OF TLINE, "   
lv_container_handle  TYPE IF_SWF_CNT_CONTAINER, "   
lv_context  TYPE CHAR1, "   SPACE
lv_html_escape_format  TYPE STRING. "   

  CALL FUNCTION 'SWU_GET_TASK_TEXTLINES'  "
    EXPORTING
         TASK = lv_task
         WI_ID = lv_wi_id
         WIHEADER = lv_wiheader
         USAGE = lv_usage
         LINEWIDTH = lv_linewidth
         LANGUAGE = lv_language
         CONTAINER_HANDLE = lv_container_handle
         CONTEXT = lv_context
         HTML_ESCAPE_FORMAT = lv_html_escape_format
    TABLES
         ASCII_TEXT_LINES = lt_ascii_text_lines
         CONTAINER = lt_container
         HTML_TEXT_LINES = lt_html_text_lines
         ITF_TEXT_LINES = lt_itf_text_lines
         STREAM_TEXT_LINES = lt_stream_text_lines
         COMMAND_LINES = lt_command_lines
    EXCEPTIONS
        WRONG_USAGE = 1
        TEXT_NOT_FOUND = 2
        TEXT_SYSTEM_ERROR = 3
. " SWU_GET_TASK_TEXTLINES




ABAP code using 7.40 inline data declarations to call FM SWU_GET_TASK_TEXTLINES

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 OBJECT FROM RHOBJECTS INTO @DATA(ld_task).
 
 
 
"SELECT single WI_ID FROM SWWWIHEAD INTO @DATA(ld_wi_id).
 
 
 
 
 
 
"SELECT single WI_TYPE FROM SWWWIHEAD INTO @DATA(ld_usage).
 
 
"SELECT single TDLINESIZE FROM THEAD INTO @DATA(ld_linewidth).
DATA(ld_linewidth) = 75.
 
 
"SELECT single LANGU FROM SY INTO @DATA(ld_language).
DATA(ld_language) = SY-LANGU.
 
 
 
DATA(ld_context) = ' '.
 
 


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!