Skip to Content
Former Member
Jan 08, 2008 at 01:57 PM




We have a scenario while using the BAPI - BAPI_ALM_NOTIF_DATA_DELETE.

We execute this BAPI in a loop -

1)The input tasks are deleted for the first notification and the status is set to say, 'ATCO'. This status is stored in an internal table g_sttab inside the BAPI.

2)We have saved the notification using SAVE BAPI for notification and then the COMMIT BAPI.

3)In the next loop pass, we send the 2nd notification to the BAPI_ALM_NOTIF_DATA_DELETE - but the status of the previous notification is still retained in the internal table g_sttab. As a result, it is wrongly updating the status of the 2nd notification.

Has anyone encountered this problem before? Is there any way to refresh this internal table present in the BAPI?

I could not find any FMs/BAPIs for refreshing the internal tables in the corresponding function group.

Any pointers are requested...