SAP BAPI_SERVICENOTIFICAT_GETLIST Function Module for Select service notifications according to customer or contact person
BAPI_SERVICENOTIFICAT_GETLIST is a standard bapi servicenotificat getlist 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 service notifications according to customer or contact person 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 servicenotificat getlist FM, simply by entering the name BAPI_SERVICENOTIFICAT_GETLIST into the relevant SAP transaction such as SE37 or SE38.
Function Group: IWWW
Program Name: SAPLIWWW
Main Program: SAPLIWWW
Appliation area: I
Release date: 10-Oct-1997
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function BAPI_SERVICENOTIFICAT_GETLIST 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_SERVICENOTIFICAT_GETLIST'"Select service notifications according to customer or contact person.
EXPORTING
CUSTOMERNO = "Customer number
* NOTIFICATION_DATE = SY-DATUM "Notification date
* COMPLETE = 'X' "Completed notifications
* PARTNERFUNCTION = "Partner function
* PARTNER = "Partners
* PARTNER_USER = "Partner
IMPORTING
RETURN = "Structure for Return Parameters (Code, Text)
TABLES
NOTIFICATION = "Table of service notifications
IMPORTING Parameters details for BAPI_SERVICENOTIFICAT_GETLIST
CUSTOMERNO - Customer number
Data type: BAPI100601-CUSTMR_NOOptional: No
Call by Reference: No ( called with pass by value option)
NOTIFICATION_DATE - Notification date
Data type: BAPI2080_1-NOTIFDATEDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
COMPLETE - Completed notifications
Data type: BAPI2080_2-COMPLETEDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
PARTNERFUNCTION - Partner function
Data type: BAPIIHPA-PAR_FUNCTOptional: Yes
Call by Reference: No ( called with pass by value option)
PARTNER - Partners
Data type: BAPIIHPA-PAR_NUMOptional: Yes
Call by Reference: No ( called with pass by value option)
PARTNER_USER - Partner
Data type: BAPI_IHPA-PARTNEROptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_SERVICENOTIFICAT_GETLIST
RETURN - Structure for Return Parameters (Code, Text)
Data type: BAPIRETURNOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_SERVICENOTIFICAT_GETLIST
NOTIFICATION - Table of service notifications
Data type: BAPI2080_1Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_SERVICENOTIFICAT_GETLIST 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_customerno | TYPE BAPI100601-CUSTMR_NO, " | |||
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_SERVICENOTIFICAT_GETLIST' "Select service notifications according to customer or contact person |
EXPORTING | ||
CUSTOMERNO | = lv_customerno | |
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_SERVICENOTIFICAT_GETLIST |
ABAP code using 7.40 inline data declarations to call FM BAPI_SERVICENOTIFICAT_GETLIST
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 CUSTMR_NO FROM BAPI100601 INTO @DATA(ld_customerno). | ||||
"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