BUS2105.SiginificantlyChanged, Released, Rejected

[jimmy sun]

Ananth,
  thanks fro your quick reply. 
   
  Based on OSS Note 597784 and some research, I believe we are limited to use BUS2105.Released,  BUS2105.Rejected, BUS2105.SiginificantlyChanged, events. And these events are published through Application Update Task. See function Group EBNF. I'll try to make some change to the workflow and see.
   
  Regards,
  Jimmy

Ananth <write2ananth at gmail.com> wrote:
  Hi Jimmy,

Even I had encountered same problem with this sometime time.

>From the workflow, if the PR is rejected, then it is fine. But when
the PR is rejected by some other means outside the purview of the
workflow, then the released event is not triggered.

So had to communicate the end user to release/reject the PR only via
the workflow and not by different means.

Dont know whether this is the answer you had expected !!!

Regards
Ananth




On 8/3/07, jimmy sun wrote:
> Hi All Expert,
>
> Evaluating a customer Workflow for PR process in a ECC 6.0 system, which was
> upgraded from a 4.6C.
>
> The customer workflow looks like a modified copy of WS20000077 with
> additional deadline handling steps. This is not my problem. The first step
> of the workflow is notify receiver for Approval, outcome can be 'Release of
> Purchase Requisition Refused', 'Release Purchase Requisition', 'Requisition
> Changed Significantly', 'Latest end' and 'Processing obsolete'
>
> When approer go through Workflow inbox to ''Release of Purchase Requisition
> Refused' (Reject) which is the desired method, everything works fine. It
> takes the 'Rejected' branch. But when user use ME54N and Rejected the PR it
> always take the 'Requisition Changed Significantly' Branch.
>
> There are some additional code in the method before it calles ME54N. I have
> verified they are not raising any event.
>
> I have read Oss Note 597784, but have no access to SWE2 nor SWE3. Used SE38
> and executed the program RSWEINST made the change accordingly. Moved to the
> test client. End result is all ME54N fails with WL 803 error notification in
> the test client now.
> Reset the setting in the development client, transport to the test client
> and the 'Linkage Activated' flag stayed as checked in the test client.
>
> any help is appriciated.
>
> Best Regards,
> Jimmy
>
> ________________________________
> Choose the right car based on your needs. Check out Yahoo! Autos new Car
> Finder tool.
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug



"Whether you think you can or whether you think you can't, you're right!"     --Henry Ford
       
---------------------------------
Looking for a deal? Find great prices on flights and hotels with Yahoo! FareChase.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20070803/999df8f9/attachment.htm