SAP BAPI_ALM_NOTIF_TASK_SUCCESS Function Module for PM/CS Notification: Set Task to Successful









BAPI_ALM_NOTIF_TASK_SUCCESS is a standard bapi alm notif task success SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for PM/CS Notification: Set Task to Successful 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 task success FM, simply by entering the name BAPI_ALM_NOTIF_TASK_SUCCESS into the relevant SAP transaction such as SE37 or SE38.

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



Function BAPI_ALM_NOTIF_TASK_SUCCESS 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_TASK_SUCCESS'"PM/CS Notification: Set Task to Successful
  EXPORTING
   NUMBER =  "Notification No
   TASK_KEY =  "Task Number
*  LANGU = SY-LANGU "Language
*  LANGUISO =  "Language According to ISO 639
*  TESTRUN = ' ' "Check Only

 IMPORTING
   SYSTEMSTATUS =  "System Status of Task
   USERSTATUS =  "User Status of Task

TABLES
*  RETURN =  "Return Parameters
.



IMPORTING Parameters details for BAPI_ALM_NOTIF_TASK_SUCCESS

NUMBER - Notification No

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

TASK_KEY - Task Number

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

LANGU - Language

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

LANGUISO - Language According to ISO 639

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

TESTRUN - Check Only

Data type: BAPI20783T-STATUS_IND
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BAPI_ALM_NOTIF_TASK_SUCCESS

SYSTEMSTATUS - System Status of Task

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

USERSTATUS - User Status of Task

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

TABLES Parameters details for BAPI_ALM_NOTIF_TASK_SUCCESS

RETURN - Return Parameters

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

Copy and paste ABAP code example for BAPI_ALM_NOTIF_TASK_SUCCESS 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_task_key  TYPE BAPI2080_NOTTASKE-TASK_KEY, "   
lv_userstatus  TYPE BAPI2080_NOTADT-USRSTATUS, "   
lv_langu  TYPE BAPI2080_NOTSTI-LANGU, "   SY-LANGU
lv_languiso  TYPE BAPI2080_NOTSTI-LANGUISO, "   
lv_testrun  TYPE BAPI20783T-STATUS_IND. "   SPACE

  CALL FUNCTION 'BAPI_ALM_NOTIF_TASK_SUCCESS'  "PM/CS Notification: Set Task to Successful
    EXPORTING
         NUMBER = lv_number
         TASK_KEY = lv_task_key
         LANGU = lv_langu
         LANGUISO = lv_languiso
         TESTRUN = lv_testrun
    IMPORTING
         SYSTEMSTATUS = lv_systemstatus
         USERSTATUS = lv_userstatus
    TABLES
         RETURN = lt_return
. " BAPI_ALM_NOTIF_TASK_SUCCESS




ABAP code using 7.40 inline data declarations to call FM BAPI_ALM_NOTIF_TASK_SUCCESS

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 TASK_KEY FROM BAPI2080_NOTTASKE INTO @DATA(ld_task_key).
 
"SELECT single USRSTATUS FROM BAPI2080_NOTADT INTO @DATA(ld_userstatus).
 
"SELECT single LANGU FROM BAPI2080_NOTSTI INTO @DATA(ld_langu).
DATA(ld_langu) = SY-LANGU.
 
"SELECT single LANGUISO FROM BAPI2080_NOTSTI INTO @DATA(ld_languiso).
 
"SELECT single STATUS_IND FROM BAPI20783T INTO @DATA(ld_testrun).
DATA(ld_testrun) = ' '.
 


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!