SAP BAPI_ALM_NOTIF_LIST_EQUI Function Module for Select PM/CS Notifications by Equipment









BAPI_ALM_NOTIF_LIST_EQUI is a standard bapi alm notif list equi SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Select PM/CS Notifications by Equipment 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 bapi alm notif list equi FM, simply by entering the name BAPI_ALM_NOTIF_LIST_EQUI into the relevant SAP transaction such as SE37 or SE38.

Function Group: IWOPM
Program Name: SAPLIWOPM
Main Program: SAPLIWOPM
Appliation area: I
Release date: 08-May-2002
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_ALM_NOTIF_LIST_EQUI 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 'BAPI_ALM_NOTIF_LIST_EQUI'"Select PM/CS Notifications by Equipment
EXPORTING
EQUIPMENT = "Equipment Number
* NOTIFICATION_DATE = SY-DATUM "Notification Date
* COMPLETE = 'X' "Completed Notifications
* PARTNERFUNCTION = "Partner Function
* PARTNER = "Partner
* PARTNER_USER = "Partner

IMPORTING
RETURN = "Return Parameters

TABLES
NOTIFICATION = "Table of service notifications
.



IMPORTING Parameters details for BAPI_ALM_NOTIF_LIST_EQUI

EQUIPMENT - Equipment Number

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

NOTIFICATION_DATE - Notification Date

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

COMPLETE - Completed Notifications

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

PARTNERFUNCTION - Partner Function

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

PARTNER - Partner

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

PARTNER_USER - Partner

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

EXPORTING Parameters details for BAPI_ALM_NOTIF_LIST_EQUI

RETURN - Return Parameters

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

TABLES Parameters details for BAPI_ALM_NOTIF_LIST_EQUI

NOTIFICATION - Table of service notifications

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

Copy and paste ABAP code example for BAPI_ALM_NOTIF_LIST_EQUI 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_return  TYPE BAPIRETURN, "   
lv_equipment  TYPE BAPI_ITOB_PARMS-EQUIPMENT, "   
lt_notification  TYPE STANDARD TABLE OF BAPI2080_1, "   
lv_notification_date  TYPE BAPI2080_1-NOTIFDATE, "   SY-DATUM
lv_complete  TYPE BAPI2080_2-COMPLETE, "   'X'
lv_partnerfunction  TYPE BAPIIHPA-PAR_FUNCT, "   
lv_partner  TYPE BAPIIHPA-PAR_NUM, "   
lv_partner_user  TYPE BAPI_IHPA-PARTNER. "   

  CALL FUNCTION 'BAPI_ALM_NOTIF_LIST_EQUI'  "Select PM/CS Notifications by Equipment
    EXPORTING
         EQUIPMENT = lv_equipment
         NOTIFICATION_DATE = lv_notification_date
         COMPLETE = lv_complete
         PARTNERFUNCTION = lv_partnerfunction
         PARTNER = lv_partner
         PARTNER_USER = lv_partner_user
    IMPORTING
         RETURN = lv_return
    TABLES
         NOTIFICATION = lt_notification
. " BAPI_ALM_NOTIF_LIST_EQUI




ABAP code using 7.40 inline data declarations to call FM BAPI_ALM_NOTIF_LIST_EQUI

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 EQUIPMENT FROM BAPI_ITOB_PARMS INTO @DATA(ld_equipment).
 
 
"SELECT single NOTIFDATE FROM BAPI2080_1 INTO @DATA(ld_notification_date).
DATA(ld_notification_date) = SY-DATUM.
 
"SELECT single COMPLETE FROM BAPI2080_2 INTO @DATA(ld_complete).
DATA(ld_complete) = 'X'.
 
"SELECT single PAR_FUNCT FROM BAPIIHPA INTO @DATA(ld_partnerfunction).
 
"SELECT single PAR_NUM FROM BAPIIHPA INTO @DATA(ld_partner).
 
"SELECT single PARTNER FROM BAPI_IHPA INTO @DATA(ld_partner_user).
 


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!