SAP NOTICE_LIST Function Module for









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

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



Function NOTICE_LIST 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_LIST'"
EXPORTING
* X_SPRAS = SY-LANGU "
* XT_NOTICE_KEYS = "
* XT_NOTICES = "Note object data
* X_HEADER = '2145' "
* X_FLG_FORCE_LIST = "
.



IMPORTING Parameters details for NOTICE_LIST

X_SPRAS -

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

XT_NOTICE_KEYS -

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

XT_NOTICES - Note object data

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

X_HEADER -

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

X_FLG_FORCE_LIST -

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

Copy and paste ABAP code example for NOTICE_LIST 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_x_spras  TYPE SY-LANGU, "   SY-LANGU
lv_xt_notice_keys  TYPE EENOT_NOTICE_KEY_TAB, "   
lv_xt_notices  TYPE EENOT_NOTICE_TAB, "   
lv_x_header  TYPE EENO_GEN-LISTHEADER, "   '2145'
lv_x_flg_force_list  TYPE C. "   

  CALL FUNCTION 'NOTICE_LIST'  "
    EXPORTING
         X_SPRAS = lv_x_spras
         XT_NOTICE_KEYS = lv_xt_notice_keys
         XT_NOTICES = lv_xt_notices
         X_HEADER = lv_x_header
         X_FLG_FORCE_LIST = lv_x_flg_force_list
. " NOTICE_LIST




ABAP code using 7.40 inline data declarations to call FM NOTICE_LIST

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 LANGU FROM SY INTO @DATA(ld_x_spras).
DATA(ld_x_spras) = SY-LANGU.
 
 
 
"SELECT single LISTHEADER FROM EENO_GEN INTO @DATA(ld_x_header).
DATA(ld_x_header) = '2145'.
 
 


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!