Rejection_Start w/BUS2009 - Pur Req Line Item Release

[Fairless, Hal]

I am working a custom Requisition Release workflow using Item-wise
releasing.  The w/f uses the standard method 'singlerelease' with
terminating events when the item is any of the following: Released,
SignificantlyChanged, Reset or Rejection_Start.  When the item is
'Rejected', (standard 'reject' icon available on ME54N, the
'SignificantlyChanged' and 'Rejection_Start' events are triggered
(confirmed by reviewing the event log), However the
'SignificantlyChanged' outcome from the singlerelease task is only one
showing, as an outcome (based on the Graphic display within the workflow
log.  Have others of you experienced this? Why is the 'Rejection_Start'
outcome is not being used, even though the event is being raised?  Any
help is urgently requested and very much appreciated.

Regards,

Hal Fairless

Workflow Consultant