<P>
Hello Jocelyn...<BR>
<BR>
Thanks for your reply.<BR>
<BR>
We have already checked for the user who is responsible for release step - 'wf-batch'. Also we have provided Sap All autho for the same.<BR>
<BR>
Check after the release step goes into error<BR>
1. Was the bid actually changed to released status? Use txn BBP_PD and also use fm BBP_CHANGE_DOC_GENERAL to check what is happening.<BR>
Reply: Bid status not changed to release. It says SETRELEASE can not be executed. BBP_CHANGE_DOC_GENERAL is not available in our system.<BR>
<BR>
2. Were any changes made to the bid invitiations?<BR>
Reply: No..There are no changes made in Bid Invitation.<BR>
<BR>
3. Was the follow on document created? - problem may be not with the<BR>
>bid but with creating the follow-on doc in response to released status.<BR>
Reply: Since the bid status is not changed to 'released' subworkflow is not triggered but we can create followon doc PO or Contract. There is only problem of completion of WF.<BR>
<BR>
No related notes are available for this. Also I am suprise to see that this scenario is working fine with Development client.<BR>
<BR>
Regards,<BR>
Shreeram.<BR>
<BR>
<BR>
On Thu, 28 Jul 2005 Dart,Jocelyn wrote :<BR>
>Suggestions:<BR>
><BR>
>Don't worry about the applet! It often gets confused when unexpected<BR>
>things occur. Get the workflow right and the applet will be right.<BR>
><BR>
>Check which user is being used for the Release step in the workflow log.<BR>
><BR>
>Check after the release step goes into error<BR>
> 1. Was the bid actually changed to released status? Use txn BBP_PD and<BR>
>also use fm BBP_CHANGE_DOC_GENERAL to check what is happening.<BR>
> 2. Were any changes made to the bid invitiations?<BR>
> 3. Was the follow on document created? - problem may be not with the<BR>
>bid but with creating the follow-on doc in response to released status.<BR>
><BR>
>Check for any SAP notes on the "release" of bids and the bid workflows<BR>
>in general.<BR>
><BR>
>Check for notes re deadlocking or time out of release.<BR>
><BR>
>Regards,<BR>
>Jocelyn Dart<BR>
>Senior Consultant<BR>
>SAP Australia Pty Ltd.<BR>
>Level 1/168 Walker St.<BR>
>North Sydney<BR>
>NSW, 2060<BR>
>Australia<BR>
>T +61 412 390 267<BR>
>M + 61 412 390 267<BR>
>E jocelyn.dart@sap.com<BR>
>http://www.sap.com <http://www.sap.com/><BR>
><BR>
>The information contained in or attached to this electronic transmission<BR>
>is confidential and may be legally privileged. It is intended only for<BR>
>the person or entity to which it is addressed. If you are not the<BR>
>intended recipient, you are hereby notified that any distribution,<BR>
>copying, review, retransmission, dissemination or other use of this<BR>
>electronic transmission or the information contained in it is strictly<BR>
>prohibited. If you have received this electronic transmission in error,<BR>
>please immediately contact the sender to arrange for the return of the<BR>
>original documents.<BR>
><BR>
>Electronic transmission cannot be guaranteed to be secure and<BR>
>accordingly, the sender does not accept liability for any such data<BR>
>corruption, interception, unauthorized amendment, viruses, delays or the<BR>
>consequences thereof.<BR>
><BR>
>Any views expressed in this electronic transmission are those of the<BR>
>individual sender, except where the message states otherwise and the<BR>
>sender is authorized to state them to be the views of SAP AG or any of<BR>
>its subsidiaries. SAP AG, its subsidiaries, and their directors,<BR>
>officers and employees make no representation nor accept any liability<BR>
>for the accuracy or completeness of the views or information contained<BR>
>herein. Please be aware that the furnishing of any pricing information/<BR>
>business proposal herein is indicative only, is subject to change and<BR>
>shall not be construed as an offer or as constituting a binding<BR>
>agreement on the part of SAP AG or any of its subsidiaries to enter into<BR>
>any relationship, unless otherwise expressly stated.<BR>
><BR>
><BR>
><BR>
>________________________________<BR>
><BR>
> From: sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On Behalf<BR>
>Of shreeram K<BR>
>Sent: Thursday, 28 July 2005 12:49 AM<BR>
>To: sap-wug@mit.edu<BR>
>Subject: SRM 4.0 -EBP- 2 step bid approval WF<BR>
><BR>
><BR>
><BR>
>Hello,<BR>
><BR>
>SAP team has developed '2 stage bid approval workflow' as per our<BR>
>client's requirement. This workflow is working fine in development<BR>
>system but facing following problem in production system.<BR>
><BR>
>After 2nd stage approval is processed, workflow in going into error and<BR>
>hence bid status remains unchanged. However it is not<BR>
>hampering further process and allows us to create PO or Contract.<BR>
>Please find below steps we are following...<BR>
>1. Bid invitation creation by initiator.<BR>
>2. Bid acceptance and submission by Vendor<BR>
>3. Purchaser/initiator accepts the bid. - Workflow gets triggered.<BR>
>4. First Level Approval is done.<BR>
>5. Second level approval is done. After this Workflow gets triggeres in<BR>
>background and follows below sequence...<BR>
>a. Update Bid During Approval/Rejection - Here workflow is going into<BR>
>error.<BR>
>b. Set status of bid to 'Released' - Workflow is going into error.<BR>
>c. Sub Workflow gets triggered to send automatic mail to initiator.<BR>
>- Here Sub workflow cannot get triggered since earlier event is not<BR>
>completed.<BR>
>6. Purchaser/Initiator can create Po or Contract.-<BR>
>No problem in carrying out this activity but Workflow status is not<BR>
>changed to 'Completed'.<BR>
><BR>
>Till the 2nd approval is done applet is showing right status but after<BR>
>2nd approval, it is again showing again the intial status which is<BR>
>really strange.<BR>
><BR>
>Most important thing we have observed that if manually restart this<BR>
>workflow again, which is in error, with transaction SWPR, then it is<BR>
>going ahead with no errors.<BR>
>We have compared the status in Development and Production and found that<BR>
>it is the same.<BR>
><BR>
>Has anyone experinced such kind of problem?<BR>
>Awaiting for your reply... Thanks.<BR>
><BR>
>Regards,<BR>
>Shreeram<BR>
><BR>
><BR>
><BR>
><BR>
><BR>
><BR>
><BR>
> <http://clients.rediff.com/signature/track_sig.asp><BR>
>_______________________________________________<BR>
>SAP-WUG mailing list<BR>
>SAP-WUG@mit.edu<BR>
>http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>
</P>
<br><br>
<A target="_blank" HREF="http://clients.rediff.com/signature/track_sig.asp"><IMG SRC="http://ads.rediff.com/RealMedia/ads/adstream_nx.cgi/www.rediffmail.com/inbox.htm@Bottom" BORDER=0 VSPACE=0 HSPACE=0></a>