SAP BAPI_SERVNOT_CLOSE Function Module for Complete service notification
BAPI_SERVNOT_CLOSE is a standard bapi servnot close SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Complete service notification 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 servnot close FM, simply by entering the name BAPI_SERVNOT_CLOSE into the relevant SAP transaction such as SE37 or SE38.
Function Group: IQS6
Program Name: SAPLIQS6
Main Program: SAPLIQS6
Appliation area: I
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BAPI_SERVNOT_CLOSE 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_SERVNOT_CLOSE'"Complete service notification.
EXPORTING
NUMBER = "Notification number
SYSTSTAT = "Completion data
* TESTRUN = ' ' "Check only indicator
IMPORTING
SYSTEMSTATUS = "Notification system status
USERSTATUS = "Notification user status
TABLES
* RETURN = "Message type:S success, E error, W warning, I information
IMPORTING Parameters details for BAPI_SERVNOT_CLOSE
NUMBER - Notification number
Data type: BAPI2080_NOTHDRE-NOTIF_NOOptional: No
Call by Reference: No ( called with pass by value option)
SYSTSTAT - Completion data
Data type: BAPI2080_NOTSTIOptional: No
Call by Reference: No ( called with pass by value option)
TESTRUN - Check only indicator
Data type: BAPI20783T-STATUS_INDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_SERVNOT_CLOSE
SYSTEMSTATUS - Notification system status
Data type: BAPI2080_NOTADT-SYSTATUSOptional: No
Call by Reference: No ( called with pass by value option)
USERSTATUS - Notification user status
Data type: BAPI2080_NOTADT-USRSTATUSOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BAPI_SERVNOT_CLOSE
RETURN - Message type:S success, E error, W warning, I information
Data type: BAPIRET2Optional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_SERVNOT_CLOSE 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_number | TYPE BAPI2080_NOTHDRE-NOTIF_NO, " | |||
| lt_return | TYPE STANDARD TABLE OF BAPIRET2, " | |||
| lv_systemstatus | TYPE BAPI2080_NOTADT-SYSTATUS, " | |||
| lv_syststat | TYPE BAPI2080_NOTSTI, " | |||
| lv_userstatus | TYPE BAPI2080_NOTADT-USRSTATUS, " | |||
| lv_testrun | TYPE BAPI20783T-STATUS_IND. " SPACE |
|   CALL FUNCTION 'BAPI_SERVNOT_CLOSE' "Complete service notification |
| EXPORTING | ||
| NUMBER | = lv_number | |
| SYSTSTAT | = lv_syststat | |
| TESTRUN | = lv_testrun | |
| IMPORTING | ||
| SYSTEMSTATUS | = lv_systemstatus | |
| USERSTATUS | = lv_userstatus | |
| TABLES | ||
| RETURN | = lt_return | |
| . " BAPI_SERVNOT_CLOSE | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_SERVNOT_CLOSE
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 NOTIF_NO FROM BAPI2080_NOTHDRE INTO @DATA(ld_number). | ||||
| "SELECT single SYSTATUS FROM BAPI2080_NOTADT INTO @DATA(ld_systemstatus). | ||||
| "SELECT single USRSTATUS FROM BAPI2080_NOTADT INTO @DATA(ld_userstatus). | ||||
| "SELECT single STATUS_IND FROM BAPI20783T INTO @DATA(ld_testrun). | ||||
| DATA(ld_testrun) | = ' '. | |||
Search for further information about these or an SAP related objects