SAP Function Modules
REPORT_TEXT_EDIT_OPEN SAP Function module
REPORT_TEXT_EDIT_OPEN is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.
See here to view full function module documentation and code listing, simply by entering the name REPORT_TEXT_EDIT_OPEN into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
GRWR
Released Date:
Not Released
Processing type: Normal fucntion module
Pattern for FM REPORT_TEXT_EDIT_OPEN - REPORT TEXT EDIT OPEN
CALL FUNCTION 'REPORT_TEXT_EDIT_OPEN' "
EXPORTING
application = " applclass Application
* def_number_of_lines = 0 " i
* langu = SY-LANGU " sy-langu Language
* left_margin = 0 " i Left Margin
* page_width = SY-LINSZ " sy-linsz Page Width
* right_margin = 0 " i Right Margin
text_name = " Text Module Name
text_type = " rtxttype
* reporting_table = SPACE " rtxcs-rep_table
* translate_only = SPACE " flag
* display_only = SPACE " flag
IMPORTING
number_of_lines = "
* TABLES
* common_symbols = " rtxcsyms
* fields = " rtxflds
* variables = " rtxvars
EXCEPTIONS
INVALID_APPLICATION = 1 "
INVALID_TEXT_TYPE = 2 "
. " REPORT_TEXT_EDIT_OPEN
ABAP code example for Function Module REPORT_TEXT_EDIT_OPEN
The ABAP code below is a full code listing to execute function module REPORT_TEXT_EDIT_OPEN including all data declarations. The code uses 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 original method of declaring data variables up front. 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).
| ld_number_of_lines | TYPE STRING , |
| it_common_symbols | TYPE STANDARD TABLE OF RTXCSYMS,"TABLES PARAM |
| wa_common_symbols | LIKE LINE OF it_common_symbols , |
| it_fields | TYPE STANDARD TABLE OF RTXFLDS,"TABLES PARAM |
| wa_fields | LIKE LINE OF it_fields , |
| it_variables | TYPE STANDARD TABLE OF RTXVARS,"TABLES PARAM |
| wa_variables | LIKE LINE OF it_variables . |
DATA(ld_application) = 'Check type of data required'.
DATA(ld_def_number_of_lines) = 'Check type of data required'.
DATA(ld_langu) = 'Check type of data required'.
DATA(ld_left_margin) = 'Check type of data required'.
DATA(ld_page_width) = '123 '.
DATA(ld_right_margin) = 'Check type of data required'.
DATA(ld_text_name) = 'some text here'.
DATA(ld_text_type) = 'Check type of data required'.
SELECT single REP_TABLE
FROM RTXCS
INTO @DATA(ld_reporting_table).
DATA(ld_translate_only) = 'Check type of data required'.
DATA(ld_display_only) = 'Check type of data required'.
"populate fields of struture and append to itab
append wa_common_symbols to it_common_symbols.
"populate fields of struture and append to itab
append wa_fields to it_fields.
"populate fields of struture and append to itab
append wa_variables to it_variables. . CALL FUNCTION 'REPORT_TEXT_EDIT_OPEN' EXPORTING application = ld_application * def_number_of_lines = ld_def_number_of_lines * langu = ld_langu * left_margin = ld_left_margin * page_width = ld_page_width * right_margin = ld_right_margin text_name = ld_text_name text_type = ld_text_type * reporting_table = ld_reporting_table * translate_only = ld_translate_only * display_only = ld_display_only IMPORTING number_of_lines = ld_number_of_lines * TABLES * common_symbols = it_common_symbols * fields = it_fields * variables = it_variables EXCEPTIONS INVALID_APPLICATION = 1 INVALID_TEXT_TYPE = 2 . " REPORT_TEXT_EDIT_OPEN
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 2. "Exception "Add code for exception here ENDIF.
ABAP code to compare 7.40 inline data declaration with original syntax
The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.
DATA:
| ld_number_of_lines | TYPE STRING , |
| ld_application | TYPE APPLCLASS , |
| it_common_symbols | TYPE STANDARD TABLE OF RTXCSYMS , |
| wa_common_symbols | LIKE LINE OF it_common_symbols, |
| ld_def_number_of_lines | TYPE I , |
| it_fields | TYPE STANDARD TABLE OF RTXFLDS , |
| wa_fields | LIKE LINE OF it_fields, |
| ld_langu | TYPE SY-LANGU , |
| it_variables | TYPE STANDARD TABLE OF RTXVARS , |
| wa_variables | LIKE LINE OF it_variables, |
| ld_left_margin | TYPE I , |
| ld_page_width | TYPE SY-LINSZ , |
| ld_right_margin | TYPE I , |
| ld_text_name | TYPE STRING , |
| ld_text_type | TYPE RTXTTYPE , |
| ld_reporting_table | TYPE RTXCS-REP_TABLE , |
| ld_translate_only | TYPE FLAG , |
| ld_display_only | TYPE FLAG . |
ld_application = 'Check type of data required'.
"populate fields of struture and append to itab
append wa_common_symbols to it_common_symbols.
ld_def_number_of_lines = 'Check type of data required'.
"populate fields of struture and append to itab
append wa_fields to it_fields.
ld_langu = 'Check type of data required'.
"populate fields of struture and append to itab
append wa_variables to it_variables.
ld_left_margin = 'Check type of data required'.
ld_page_width = '123 '.
ld_right_margin = 'Check type of data required'.
ld_text_name = 'some text here'.
ld_text_type = 'Check type of data required'.
SELECT single REP_TABLE
FROM RTXCS
INTO ld_reporting_table.
ld_translate_only = 'Check type of data required'.
ld_display_only = 'Check type of data required'.
Contribute (Add Comments)
Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name REPORT_TEXT_EDIT_OPEN or its description.