Anyone else confused by QM status management?

[Michael Pokraka]

Greetings to all who were ever confused by Notification events,

Just thought I'd post a quick update now that this is resolved by SAP:

The SAP-delivered workflow also does not get triggered for all notification
processing scenarios. This is because we can have multiple CREATED events
for one notifiaction; or we can have no CREATED event if an approver created
and approved a notification in one go (a most unusual process I might add...
not!). So it does not work. Other times there is neither CREATED nor
INPROCESS.

This is our fault for trying to use functionality provided in QM01 and SAP
have provided user enhamcements for us to make it work. I quote part of
their last response below.

Cheers
Mike

The so called inconsistancies are caused by the
following facts:

- The customer creates and releases a notification simultaneously

- The customer reopens an unapproved notification

- Finally the customer does not create the correspondent event.

In all cases the customer has the oppertunity to create their own
events using the user enhancements




Schmidinger, Heinz (Unaxis IT BZ) wrote:
> I can add an other kombination:
>
> If you create a notification and add e.g. an order directly out of the
> notification (IW51), Event 'CREATE' is not fired, instead 'INPROCESS' is
> fired.
>
> I have reported it to OSS 2 years ago but after discussions with SAP about
> these inconsistencies I have creted my own events, because SAP is not
> willing to clear these inconstensies.
>
> -----Ursprüngliche Nachricht-----
> Von: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]Im Auftrag von
> Michael Pokraka
> Gesendet am: Mittwoch, 24. November 2004 12:27
> An: SAP-WUG at MITVMA.MIT.EDU
> Betreff: Anyone else confused by QM status management?
>
> Greetings all,
> I'm just wondering if I'm the only one confused by the SAP standard
> status/event settings around notifications?
>
> Completing a notification and putting it back into process raises an
> INPROCESSAGAIN. Rejecting a notification and putting it back into process
> raises both a CREATED and INPROCESSAGAIN event. Deleting it and putting it
> back into process only raises an INPROCESS. Other combinations raise
> INPROCESSAGAIN and INPROCESS, or some other random sets of events.
>
> The basic problem seems to be that some events are raised directly in the
> code and others via status management (And a few custom events for good
> measure, including changedocuments). There just seems to be some
> inconsistency and I'm getting tired of catering for all the bizarre
> combinations of actions our functional folks can think up to produce a new
> set of event/status combinations for the same basic process.
>
> I suppose it's more of a rant/discussion rather than a problem, but putting
> in the fourth 'special case' fix for inconsistent events within the standard
> is getting tedious. At least it's made for some interesting debugging and a
> lot of headscratching.
>
> Cheers
> Mike
>
>