SAP NOTICE_ACTION Function Module for INTERNAL: ACTION Module for Note Object









NOTICE_ACTION is a standard notice 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 INTERNAL: ACTION Module for Note Object 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 notice action FM, simply by entering the name NOTICE_ACTION into the relevant SAP transaction such as SE37 or SE38.

Function Group: EENO
Program Name: SAPLEENO
Main Program: SAPLEENO
Appliation area:
Release date: 15-Dec-1995
Mode(Normal, Remote etc): Normal Function Module
Update:



Function NOTICE_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 'NOTICE_ACTION'"INTERNAL: ACTION Module for Note Object
EXPORTING
X_ACTION = "Function to be Performed
* X_NEW_KEY = ' ' "New Key for Notes
* X_VERSION = ' ' "Create New Version -> See Documentation
* X_LANGU = "Return Value of ABAP Statements

IMPORTING
YT_LINE_TABLE = "Table of First Lines of all Notes
Y_CURSOR_FOCUS = "Cursor Focus

CHANGING
XY_OBJ = "Object Data
* XY_OBJ_COPY_TARGET = "Target Object for Copying Notes

EXCEPTIONS
ACTION_NOT_SUPPORTED = 1
.



IMPORTING Parameters details for NOTICE_ACTION

X_ACTION - Function to be Performed

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

X_NEW_KEY - New Key for Notes

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

X_VERSION - Create New Version -> See Documentation

Data type: EENO_GEN-VERSION
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_LANGU - Return Value of ABAP Statements

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

EXPORTING Parameters details for NOTICE_ACTION

YT_LINE_TABLE - Table of First Lines of all Notes

Data type: EENOT_NOTICE_LINE_TABLE
Optional: No
Call by Reference: Yes

Y_CURSOR_FOCUS - Cursor Focus

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

CHANGING Parameters details for NOTICE_ACTION

XY_OBJ - Object Data

Data type: EENOT_NOTICE
Optional: No
Call by Reference: Yes

XY_OBJ_COPY_TARGET - Target Object for Copying Notes

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

EXCEPTIONS details

ACTION_NOT_SUPPORTED - This function is not supported

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

Copy and paste ABAP code example for NOTICE_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_xy_obj  TYPE EENOT_NOTICE, "   
lv_x_action  TYPE EENO_GEN-OKCODE, "   
lv_yt_line_table  TYPE EENOT_NOTICE_LINE_TABLE, "   
lv_action_not_supported  TYPE EENOT_NOTICE_LINE_TABLE, "   
lv_x_new_key  TYPE THEAD-TDNAME, "   ' '
lv_y_cursor_focus  TYPE EENO_GEN-CURSOR_FOCUS, "   
lv_xy_obj_copy_target  TYPE EENOT_NOTICE, "   
lv_x_version  TYPE EENO_GEN-VERSION, "   ' '
lv_x_langu  TYPE SY-LANGU. "   

  CALL FUNCTION 'NOTICE_ACTION'  "INTERNAL: ACTION Module for Note Object
    EXPORTING
         X_ACTION = lv_x_action
         X_NEW_KEY = lv_x_new_key
         X_VERSION = lv_x_version
         X_LANGU = lv_x_langu
    IMPORTING
         YT_LINE_TABLE = lv_yt_line_table
         Y_CURSOR_FOCUS = lv_y_cursor_focus
    CHANGING
         XY_OBJ = lv_xy_obj
         XY_OBJ_COPY_TARGET = lv_xy_obj_copy_target
    EXCEPTIONS
        ACTION_NOT_SUPPORTED = 1
. " NOTICE_ACTION




ABAP code using 7.40 inline data declarations to call FM NOTICE_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 OKCODE FROM EENO_GEN INTO @DATA(ld_x_action).
 
 
 
"SELECT single TDNAME FROM THEAD INTO @DATA(ld_x_new_key).
DATA(ld_x_new_key) = ' '.
 
"SELECT single CURSOR_FOCUS FROM EENO_GEN INTO @DATA(ld_y_cursor_focus).
 
 
"SELECT single VERSION FROM EENO_GEN INTO @DATA(ld_x_version).
DATA(ld_x_version) = ' '.
 
"SELECT single LANGU FROM SY INTO @DATA(ld_x_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!