cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Workflow goes in error

Former Member
0 Likes
562

hello ,

I have a weird problem. We have a BO - ZBUS2012 copied from BUS2012 in release po workflow.

I have 2 backgroubnd tasks at the begining of WF , one for getting Users list to whom an Email would be sent and another for emailing PO info to these users .When PO is created and saved WF is trigerred twice - and all steps are performed twice.One WF goes in error while another is fine .In error log - it shows many errors as follows:

CL_SWF_RUN_ALERT_ERROR

IF_SWF_UTL_MAIL~SEND

Callback executed from work item

Callback executed from work item

EVALUATE_AGENT_INTERNAL

EVALUATE_AGENT_VIA_RULE

AC90000003

But if I trigger same WF using SWUS it absolutely works fine .Can anyone help me resoving this ?

Edited by: Pravin Gavas on Jun 13, 2008 7:22 PM

View Entire Topic
Former Member
0 Likes

Which SAP version are you in?

Check this thread, applicable for ECC 6.0

Check this thread:

[Here|/message/5043234#5043234 [original link is broken]].

Cheers

Jai

Former Member
0 Likes

Version : SAP R/3 Enterprise

Former Member
0 Likes

The error that you are getting is due to either the user to whom you are sending mail or workitem does not exist or the agent determination is failing. Please try to debug and check. By the way what is the triggering point of wflow background program?

Thanks

Arghadip

Former Member
0 Likes

Trigerring point is EVENT RELEASESTEPCREATED of BO BUS2012.

Note that second workflow goes thru perfectly and also it works well thru SWUS. So even if I denug , it works well in DEBUG.

Edited by: Pravin Gavas on Jun 14, 2008 12:55 AM

Former Member
0 Likes

HI ,

Check the entries in the transaction SWEC for your object and standard object .

If the entry is there for both the object , delete the standard object entry .

Edited by: Manik Dhakate on Jun 16, 2008 8:31 AM

imthiaz_ahmed
Active Contributor
0 Likes

Check this Note 597784. JAI SR has already gave a hint in his post. The problem is due to the additional entry in SWEC but again there is a release strategy configured. Remove the entry from SWEC.

Regards, IA