Solution : https://service.sap.com/sap/support/notes/455832 (SAP Service marketplace login required)
Summary :
When using BAPIs from function group IQS6 to create or modify service notifications, issues may occur, such as failures to create or change notifications, even without error feedback from the return table. This typically arises due to the non-execution of BAPI_SERVNOT_SAVE after calling processing BAPIs like BAPI_SERVNOT_CREATE or BAPI_SERVOT_MODIFY. To resolve this, ensure the correct order of operations: first execute the processing BAPI, then BAPI_SERVNOT save, and finally, initiate an update using BAPI_TRANSACTION_COMMIT. This sequence must also be respected when BAPIs are invoked via workflow methods.
Key words :
change service notifications, function group iqs6, process problems occur, additional key words 1, function module bapi_transaction_commit, save-bapi bapi_servnot_save 3, return table, return errors, processing-bapis 1, commit work
Related Notes :
| 1467042 | BAPI_ALM_NOTIF_CREATE : Message IX011 - Partner function ... |