SAP RH_NOTE_ACTION Function Module for HRMS: Note - Display/Change/Create
RH_NOTE_ACTION is a standard rh note action SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for HRMS: Note - Display/Change/Create 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 rh note action FM, simply by entering the name RH_NOTE_ACTION into the relevant SAP transaction such as SE37 or SE38.
Function Group: RHNT
Program Name: SAPLRHNT
Main Program: SAPLRHNT
Appliation area: H
Release date: 01-Oct-1998
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RH_NOTE_ACTION 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 'RH_NOTE_ACTION'"HRMS: Note - Display/Change/Create.
EXPORTING
INFOTYPE = "Infotype for which note should be edited
* FCODE = 'DISPLAY' "'DISPLAY'= display; 'CHANGE'= change/create
* DIRECT_DB_CHANGE = ' ' "Direct database change (no buffering)
TABLES
* COLLECT_INFOTYPES = "Infotype tables for note transfer
EXCEPTIONS
INTERNAL_ERROR = 1 NO_AUTHORITY = 2 ILLEGAL_INFOTYPE = 3 NOTE_NOT_FOUND = 4 NOTE_NOT_CREATED = 5 WRONG_FCODE = 6 NOTE_LOCKED = 7
IMPORTING Parameters details for RH_NOTE_ACTION
INFOTYPE - Infotype for which note should be edited
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
FCODE - 'DISPLAY'= display; 'CHANGE'= change/create
Data type: SY-UCOMMDefault: 'DISPLAY'
Optional: Yes
Call by Reference: No ( called with pass by value option)
DIRECT_DB_CHANGE - Direct database change (no buffering)
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for RH_NOTE_ACTION
COLLECT_INFOTYPES - Infotype tables for note transfer
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
INTERNAL_ERROR - System error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_AUTHORITY - Note is not allowed for this relationship
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ILLEGAL_INFOTYPE - Note is not allowed for this infotype
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOTE_NOT_FOUND - Note could not be found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOTE_NOT_CREATED - No note was created
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WRONG_FCODE - Invalid value in parameter FCODE
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NOTE_LOCKED - Note locked by another user
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RH_NOTE_ACTION 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_infotype | TYPE STRING, " | |||
| lv_internal_error | TYPE STRING, " | |||
| lt_collect_infotypes | TYPE STANDARD TABLE OF STRING, " | |||
| lv_fcode | TYPE SY-UCOMM, " 'DISPLAY' | |||
| lv_no_authority | TYPE SY, " | |||
| lv_direct_db_change | TYPE C, " SPACE | |||
| lv_illegal_infotype | TYPE C, " | |||
| lv_note_not_found | TYPE C, " | |||
| lv_note_not_created | TYPE C, " | |||
| lv_wrong_fcode | TYPE C, " | |||
| lv_note_locked | TYPE C. " |
|   CALL FUNCTION 'RH_NOTE_ACTION' "HRMS: Note - Display/Change/Create |
| EXPORTING | ||
| INFOTYPE | = lv_infotype | |
| FCODE | = lv_fcode | |
| DIRECT_DB_CHANGE | = lv_direct_db_change | |
| TABLES | ||
| COLLECT_INFOTYPES | = lt_collect_infotypes | |
| EXCEPTIONS | ||
| INTERNAL_ERROR = 1 | ||
| NO_AUTHORITY = 2 | ||
| ILLEGAL_INFOTYPE = 3 | ||
| NOTE_NOT_FOUND = 4 | ||
| NOTE_NOT_CREATED = 5 | ||
| WRONG_FCODE = 6 | ||
| NOTE_LOCKED = 7 | ||
| . " RH_NOTE_ACTION | ||
ABAP code using 7.40 inline data declarations to call FM RH_NOTE_ACTION
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 UCOMM FROM SY INTO @DATA(ld_fcode). | ||||
| DATA(ld_fcode) | = 'DISPLAY'. | |||
| DATA(ld_direct_db_change) | = ' '. | |||
Search for further information about these or an SAP related objects