Reputation: 173
I'm creating and updating my PM notifications via BAPI_ALM_NOTIF_CREATE
and BAPI_ALM_NOTIF_DATA_MODIFY
respectively.
BAPI_ALM_NOTIF_CREATE
triggers user-exit EXIT_SAPLIQS0_017 (QQMA0025), but BAPI_ALM_NOTIF_DATA_MODIFY
does not trigger user-exit EXIT_SAPMIWO0_020 (QQMA0014).
I was wondering if there is another BAPI or FM that triggers the user-exit for saving the notification and triggering the user-exit.
If not, what are my other options? Would an explicit enhancement be the next best thing?
This is what Enhancement Spot ES_SAPLIWOPM
looks like. Does this mean only BAPI_ALM_NOTIF_DATA_DELETE
is supported?
Upvotes: 2
Views: 4524
Reputation: 6033
you could use the enhancement spot ES_SAPLIWOPM
, it offers three enhancement points within BAPI_ALM_NOTIF_DATA_MODIFY
. The enhancement spot doesn't seem to be limited to SAP internal use, so you could use it to implement your requirements. It also offers enhancement points for BAPI BAPI_ALM_NOTIF_CREATE
, which would allow you to implement your requirements for create and update scenarios in the same technology.
Regarding the user exit from extension QQMA0014
, the function module is contained in module pool SAPMIWO0
and seems to be called by a few function modules and from dynpro logic, but I'm not sure they are meant to be called from outside their regular dynpro scope. Often those function modules need quite a bit of preparation to work correctly. I would stick with the BAPIs, as they are clearly meant for this purpose and have extension points to implement additional requirements, which is always a big bonus in terms of extension maintenance.
edit: the enhancement spot is present in ECC 6.0 EHP8, I'm not sure about previous releases.
Upvotes: 0
Reputation: 33
Can you check if any BAdi is getting triggered as well.
I think badi NOTIF_EVENT_POST is triggered after exit QQMA0014.
Regards
Upvotes: -1