R/3: Problem with revising a purchase requisition after rejection

Van Heerde, Arnoud arnoud.van.heerde at sap.com
Wed Jul 4 23:28:03 EDT 2001


Hi Workflowers,
 
Case:
Instead of merely informing a person with a work item (very ugly) that a
purchase requisition was rejected I would like to offer the user the
opportunity to revise it or delete it. In case the user revises the PR, it
may be significantly changed so that a different release strategy is
necessary. In case it is not significantly changed, the PR is submitted for
release again.
 
Problem:
Event BUS2105.ReleaseStepCreated is only automatically triggered after (in
fact simultaneously with) significant changes to a PR
(BUS2105.significantlyChanged). However when a user revises the PR without
the need for another release strategy, there is no event at all.
After revision we can create a new work item for the "releaser" by
triggering the event BUS2105.ReleaseStepCreated from the workflow (that will
trigger a new workflow). You only know that a PR was not significantly
changed if the event BUS2105.significantlyChanged was NOT triggered. The
real problem is thus the fact that there is no event to state that the
change was not significant. From the event log:
 
* Initial release step event triggered by standard application
BUS2105    RELEASESTEPCREATE    05.07.2001  10:13:49 WS01300030
* Rejection event triggered by standard application
BUS2105    REJECTED                     05.07.2001  10:14:32 WORKITEM
* Release step event triggered by workflow after revision
BUS2105    RELEASESTEPCREATE    05.07.2001  10:15:20 WS01300030
* However significant changes were made so both release step event and
BUS2105    RELEASESTEPCREATE    05.07.2001  10:15:20 WS01300030
* significant change event are triggered by standard application
BUS2105    SIGNIFICANTLYCHAN    05.07.2001  10:15:20 EVENTITEM
 
One solution may be to add the attribute "Release strategy" to a subtype and
work with delegation and container operations and condition steps. But is
there another way? Has anyone had to deal with this kind of problem before?
 
Any suggestions will be much appreciated.
 
Best regards, Arnoud van Heerde
 


More information about the SAP-WUG mailing list