Skip to Content

this Blog is dedicated to the developers who focus on EAM.

Are you aware that the order/ notification APIS have been enhanced to support more functionality like setting user status and is now support Custom fields? This has been an missing quite some time and is available Now.


This has been achieved by within the Customer Connect program which we have finalized quite some time ago.
The dedicated functionality which have been delivered in Customer Connect Cycle 3 you find in the Innovation Discovery
for Customers using SAP GUI Improvements in Asset Operations Maintenance

For Customers using the new Web User Interface  Improvements in Asset Operations Maintenance

The overall improvement Note  Note 2121573 lists all the changes which have been made recently in the APi´s


  • Notification APIS: Note 2145064 Note 2108975http://service.sap.com/sap/support/notes/2215722
    • Setting user status on task level is now supported by the new RFC enabled function module IBAPI_ALM_NOTIF_TASK_CHANGE_US
    • Setting the system status Deletion Flag is now supported by the new rfc enabled function module IBAPI_ALM_NOTIF_SETDELFLAG
    • Resetting the system Status Deletion Flag is now supported by the new rfc enabled function module IBAPI_ALM_NOTIF_RESETDELFLAG
    • Custom fields which have been appended in the table QMEL and QFME can now be maintained and read . Please review   Note 2108975
      1. BAPI_ALM_NOTIF_CREATE
      2. BAPI_ALM_NOTIF_DATA_ADD
      3. BAPI_ALM_NOTIF_DATA_MODIFY
      4. BAPI_ALM_NOTIF_GET_DETAIL
  • Order APIS:  Note 2032068 , Note 2095143 , Note 2125120 , Note 1991913
    • Setting the user status on order operation is now supported via function module BAPI_ALM_ORDER_MAINTAIN
    • Setting the system status “Locked” is now supported via function module BAPI_ALM_ORDER_MAINTAIN method LOCK
    • Resetting the system status “Locked” is now supported via function module BAPI_ALM_ORDER_MAINTAIN method UNLOCK
    • Setting the system status “Technically completed”  is now supported via function module BAPI_ALM_ORDER_MAINTAIN method TECHNICALCOMPLETE
    • Setting the system status “Technically completed” as well as setting the system status of the assigned notifications to “Notification completed” is now supported via function module BAPI_ALM_ORDER_MAINTAIN method TECO_WITH_NOTIF
    • Resetting the system status “Technically completed”  is now supported via function module BAPI_ALM_ORDER_MAINTAIN method CANCEL_TECHNICAL_COMPLETION 
    • Resetting the system status “Technically completed” as well as set  the system status of the assigned notification to “Notification in process” is now supported via function module BAPI_ALM_ORDER_MAINTAIN method CANCEL_TECO_WITH_NOTIF
    • Setting the system status “Closed ” which also is named as “Complete (Business)” is now supported via function module BAPI_ALM_ORDER_MAINTAIN method COMPLETE_BUSINESS
    • Setting the system status “Closed ” which also is named as “Complete (Business)” as well as set the status of all the assigned notification to “Notification completed”  is now supported via function module BAPI_ALM_ORDER_MAINTAIN method BUS_COMPL_WITH_NOTIF  
    • Reset the system status “Closed ” which also is named as “Complete (Business)” is now supported via function module BAPI_ALM_ORDER_MAINTAIN method CANCEL_BUSINESS_COMPLETION
    • Setting system status “Deletion Flag”  for the order is now supported via function module BAPI_ALM_ORDER_MAINTAIN method SET_DEL_FLAG
    • Setting system status “Deletion Flag”   for the order and as well as for the assigned notifications is now supported via function module BAPI_ALM_ORDER_MAINTAIN method SET_DLFL_WITH_NOTIF
    • Reset the  system status “Deletion Flag” for the order is now supported via function module BAPI_ALM_ORDER_MAINTAIN method RESET_DEL_FLAG                                                                                             
    • Reset the  system status “Deletion Flag” for the order as well as for the assigned notifications  is now supported via function module BAPI_ALM_ORDER_MAINTAIN method RESET_DLFL_WITH_NOTIF                                                                                   
    • For orders which are in status “Created” it is possible to execute the Do not Execute functionality via function module BAPI_ALM_ORDER_MAINTAIN method DO_NOT_EXECUTE
    • For orders which are in status “Created” it is possible to execute the Do not Execute functionality and also set for all the assigned notifications  the system status “Notification Completed” via function module BAPI_ALM_ORDER_MAINTAIN method DO_NOT_EXEC_NOTIF_CLOSE                                                                                                 
    • For orders which are in status Open it is possible to execute the Do not Execute functionality and also deallocate the assigned notifications from the order via function module BAPI_ALM_ORDER_MAINTAIN method DO_NOT_EXEC_NOTIF_DEALLOC 
    • Set the requirement date for an component in an BOM is supported via function module BAPI_ALM_ORDER_MAINTAIN

Within  the blog EAM Master Data API´s support now Custom Fields and User Status I will give you insights about the changes in the Master Data API´s

We hope that you enjoy and use this new functionality

thanks

Stephan Bantlin

To report this post you need to login first.

6 Comments

You must be Logged on to comment or reply to a post.

  1. Ziv Markovich

    Hi Stephan,

    Thanks from the information , It look like FM IBAPI_ALM_NOTIF_TASK_CHANGE_US  is “not released” yet , any idea when and if it  will be  supported  by OSS ?


    Regards,

    Ziv

    (0) 

Leave a Reply