Skip to Content
0
Feb 15, 2018 at 02:42 PM

Notification activity LT indicator not set due to irregular parallel processing

765 Views

Hello Community,

I have a very strange case happening with activity long texts in PM notifications. Please find below the scenario:

  1. User calls IW42 from a custom built transaction and the order number is filled in the screen and all of the operations listed;
  2. User populates all of the confirmations for all operations in IW42;
  3. We have the requirement that activities must be populated with the start date/time and end date/time populated;
  4. For each activity the user can populate a long text and when they do, in IW42, the image of the long text that has been created is shown;
  5. The user will then perform the technical completion from the confirmation and subsequently save in the same session/transaction.

99.9% of the time, the activity long text is saved correctly in the notification and the icon shows correctly in IW23. In 0.1% of cases the activity long text is saved and what happens here is very strange, the icon is not shown in IW23. I realise that the INDXT not being updated has already been looked at in the post https://archive.sap.com/discussions/thread/1933660, however, here the problem is different:

  • The notification is saved and the activity with the short text is created in QMMA;
  • The activity long text header is created in STXH and long text is available in the cluster table;
  • The long text indicator is not populated in the notification in IW23;
  • When in IW22, clicking on the activity long text create Icon, the long text appears.

When checking STXH, it is possible to see that the user has created two or more records on STXH at exactly the same time (HH:MM:SS) as completely different notifications processed earlier during the users working time. We have checked with users regarding use of two or more parallel sessions and pressing save quickly, but this is not the case. Each time they have stated they are only inputting in one session.

Our current gut feeling is that the two or more previous texts are hanging and have not been committed to the database although all other attributes were saved at the correct time (or a couple of minutes earlier)

Has anyone else faced this? Does anyone have a potential solution?