AW: Anyone else confused by QM status management?

[Schmidinger, Heinz (Unaxis IT BZ)]

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=FCngliche 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