SAP RHNT_NOTE_EDITOR Function Module for









RHNT_NOTE_EDITOR is a standard rhnt note editor 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 rhnt note editor FM, simply by entering the name RHNT_NOTE_EDITOR into the relevant SAP transaction such as SE37 or SE38.

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



Function RHNT_NOTE_EDITOR 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 'RHNT_NOTE_EDITOR'"
  EXPORTING
*  DISPLAY = ' ' "Flag: Display mode
*  LOCAL_CAT = ' ' "Text catalog local
*  PLAINTEXT_EDIT = ' ' "
*  EDITOR_TITLE = ' ' "Text for editor title line
   HEADER =  "Text header of the text to be edited
*  PAGE = ' ' "
*  WINDOW = ' ' "
*  SAVE = 'X' "Indicator: Saving by editor
*  LINE_EDITOR = ' ' "Indicator: Line editor or PC editor
*  CONTROL = ' ' "Control parameter for the editor
*  PROGRAM = ' ' "Program name for program symbol replacement

 IMPORTING
   FUNCTION =  "Flag: Processing status
   NEWHEADER =  "Text header (changed)
   RESULT =  "Editor status information

TABLES
   LINES =  "Lines of text being edited

EXCEPTIONS
   ID = 1    LANGUAGE = 2    LINESIZE = 3    NAME = 4    OBJECT = 5    TEXTFORMAT = 6    COMMUNICATION = 7
.



IMPORTING Parameters details for RHNT_NOTE_EDITOR

DISPLAY - Flag: Display mode

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

LOCAL_CAT - Text catalog local

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

PLAINTEXT_EDIT -

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

EDITOR_TITLE - Text for editor title line

Data type: TTXIT-TDTEXT
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

HEADER - Text header of the text to be edited

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

PAGE -

Data type: ITCTH-TDPAGE
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

WINDOW -

Data type: ITCTH-TDWINDOW
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

SAVE - Indicator: Saving by editor

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

LINE_EDITOR - Indicator: Line editor or PC editor

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

CONTROL - Control parameter for the editor

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

PROGRAM - Program name for program symbol replacement

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

EXPORTING Parameters details for RHNT_NOTE_EDITOR

FUNCTION - Flag: Processing status

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

NEWHEADER - Text header (changed)

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

RESULT - Editor status information

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

TABLES Parameters details for RHNT_NOTE_EDITOR

LINES - Lines of text being edited

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

EXCEPTIONS details

ID - Text ID in text headers is invalid

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

LANGUAGE - Language in text header invalid

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

LINESIZE - Line width in text header invalid

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

NAME - Text name in text header invalid

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

OBJECT - Text object in text header invalid

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

TEXTFORMAT - Text format cannot be processed

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

COMMUNICATION - Communication Error

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

Copy and paste ABAP code example for RHNT_NOTE_EDITOR 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_id  TYPE STRING, "   
lt_lines  TYPE STANDARD TABLE OF TLINE, "   
lv_display  TYPE FLAG, "   SPACE
lv_function  TYPE FLAG, "   
lv_local_cat  TYPE ANY, "   SPACE
lv_plaintext_edit  TYPE FLAG, "   SPACE
lv_language  TYPE FLAG, "   
lv_newheader  TYPE THEAD, "   
lv_editor_title  TYPE TTXIT-TDTEXT, "   SPACE
lv_header  TYPE THEAD, "   
lv_result  TYPE ITCER, "   
lv_linesize  TYPE ITCER, "   
lv_name  TYPE ITCER, "   
lv_page  TYPE ITCTH-TDPAGE, "   SPACE
lv_object  TYPE ITCTH, "   
lv_window  TYPE ITCTH-TDWINDOW, "   SPACE
lv_save  TYPE FLAG, "   'X'
lv_textformat  TYPE FLAG, "   
lv_line_editor  TYPE C, "   SPACE
lv_communication  TYPE C, "   
lv_control  TYPE ITCED, "   SPACE
lv_program  TYPE SY-REPID. "   SPACE

  CALL FUNCTION 'RHNT_NOTE_EDITOR'  "
    EXPORTING
         DISPLAY = lv_display
         LOCAL_CAT = lv_local_cat
         PLAINTEXT_EDIT = lv_plaintext_edit
         EDITOR_TITLE = lv_editor_title
         HEADER = lv_header
         PAGE = lv_page
         WINDOW = lv_window
         SAVE = lv_save
         LINE_EDITOR = lv_line_editor
         CONTROL = lv_control
         PROGRAM = lv_program
    IMPORTING
         FUNCTION = lv_function
         NEWHEADER = lv_newheader
         RESULT = lv_result
    TABLES
         LINES = lt_lines
    EXCEPTIONS
        ID = 1
        LANGUAGE = 2
        LINESIZE = 3
        NAME = 4
        OBJECT = 5
        TEXTFORMAT = 6
        COMMUNICATION = 7
. " RHNT_NOTE_EDITOR




ABAP code using 7.40 inline data declarations to call FM RHNT_NOTE_EDITOR

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_display) = ' '.
 
 
DATA(ld_local_cat) = ' '.
 
DATA(ld_plaintext_edit) = ' '.
 
 
 
"SELECT single TDTEXT FROM TTXIT INTO @DATA(ld_editor_title).
DATA(ld_editor_title) = ' '.
 
 
 
 
 
"SELECT single TDPAGE FROM ITCTH INTO @DATA(ld_page).
DATA(ld_page) = ' '.
 
 
"SELECT single TDWINDOW FROM ITCTH INTO @DATA(ld_window).
DATA(ld_window) = ' '.
 
DATA(ld_save) = 'X'.
 
 
DATA(ld_line_editor) = ' '.
 
 
DATA(ld_control) = ' '.
 
"SELECT single REPID FROM SY INTO @DATA(ld_program).
DATA(ld_program) = ' '.
 


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!