<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello Stepahne,<br>
<br>
The workaround for the process controlled BRF workflows is, either
find a BAdI or create an implicit enhancement if that is possible.<br>
There is a BAdI for deadlines. I have done a simple implementation
of the BAdI. You will need to come up with the logic to figure out
the current process step and set your deadlines accordingly.<br>
I once had to create an implicit enhancement even in ECC for a some
complex substitution rules. So that is an option.<br>
A while ago I posed the BRF+ question to Carlsten Ziegler of SAP and
was told that BRF+ is indeed replacing BRF. I don't remember the the
enhancement pack number that it was supposed to become effective.<br>
<br>
Regards,<br>
Ramki.<br>
<br>
<br>
You can <br>
<div class="moz-cite-prefix">On 7/3/12 4:08 AM, stephane wrote:<br>
</div>
<blockquote cite="mid:1341302884.3685.10.camel@aris" type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="GENERATOR" content="GtkHTML/3.30.3">
Yes Mike good questions, I have developped a lot of workflow in
SRM mainly wit the N step Badi and it was good time, I do prefer
the SRM workflow than working with the MM release strategy
workflow...<br>
<br>
However from my point of view the BRF workflow in SRM provides
issues with <br>
- Deadline monitoring (you can not set different deadlines for
the different step of your workflow). => they are all using the
same task<br>
- Substitution profile, as mentionned before the same tasks is
being used and therefore you can not use different profile<br>
BRF seems to be an effort from SAP to make the rule more easy but
BRF + has already made the BRF obsolete so my question to know if
there is a plan to replace the BRF workflow in SRM by BRF+.<br>
<br>
I am pretty sure that we can change the task ID and therefore
being able to add substitution profile and but I am not 100% sure
that I can do it ...<br>
<br>
Cheers<br>
Stephane<br>
<br>
Le mardi 03 juillet 2012 à 01:51 -0400, <a class="moz-txt-link-abbreviated" href="mailto:sap-wug-request@mit.edu">sap-wug-request@mit.edu</a> a
écrit :
<blockquote type="CITE">
<pre>Send SAP-WUG mailing list submissions to
<a moz-do-not-send="true" href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>
To subscribe or unsubscribe via the World Wide Web, visit
<a moz-do-not-send="true" href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a>
or, via email, send a message with subject or body 'help' to
<a moz-do-not-send="true" href="mailto:sap-wug-request@mit.edu">sap-wug-request@mit.edu</a>
You can reach the person managing the list at
<a moz-do-not-send="true" href="mailto:sap-wug-owner@mit.edu">sap-wug-owner@mit.edu</a>
When replying, please edit your Subject line so it is more specific
than "Re: Contents of SAP-WUG digest..."
Today's Topics:
1. Re: SRM BRF workflow (Ikhan)
----------------------------------------------------------------------
Message: 1
Date: Tue, 3 Jul 2012 09:51:08 +0400
From: Ikhan <<a moz-do-not-send="true" href="mailto:ikhansap@gmail.com">ikhansap@gmail.com</a>>
Subject: Re: SRM BRF workflow
To: "SAP Workflow Users' Group" <<a moz-do-not-send="true" href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>>
Message-ID:
<<a moz-do-not-send="true" href="mailto:CADb5asoJbxyOCuoaQZ3Zf11MoKfiaBKyJszMtZtLrtNa9AuwKw@mail.gmail.com">CADb5asoJbxyOCuoaQZ3Zf11MoKfiaBKyJszMtZtLrtNa9AuwKw@mail.gmail.com</a>>
Content-Type: text/plain; charset="iso-8859-1"
Hi Mike,
Why did you avoid SRM Workflows. Any Particular reason for it.
On Fri, Jun 29, 2012 at 12:27 PM, Mike Pokraka
<<a moz-do-not-send="true" href="mailto:wug@workflowconnections.com">wug@workflowconnections.com</a>>wrote:
> Sorry can't help much with SRM details, worked hard to avoid it most of my
> workflow career.
> If it helps, I once did an enhancement to integrate the BADI into the
> regular sapgui substitution dialog, so if the BADI doesn't work for you
> something similar may also an option for you.
>
> Regards,
> Mike
>
> On Fri, June 29, 2012 8:24 am, stephane wrote:
> > Hi all,
> >
> > Thanks, Mike, for your answer, I know this Badi however I am not 100%
> > sure that it will work in my case.
> > SRM one client with a Business All in One CLient without the EC
> > portal ....
> > No other solution wihtout UWL ?
> >
> > I am not yet 100% sure to know how the architecture of this solution
> > works.
> >
> > Some more questions :
> > - SRM the Processed controled workflow (BRF) how does it work for
> > different substitution profile ? It seems to be the same tasks behing
> > every approval step
> > - Same question but for deadline monitoriing can we have different
> > time and 'escalation process' depending of the steps ?
> > - Do you know if those BRF workflow will be replaced by BRFPlus
> > workflow soon ?
> >
> > Cheers
> > Stephane
> >
> >
> >
> > Le jeudi 28 juin 2012 ? 12:16 -0400, <a moz-do-not-send="true" href="mailto:sap-wug-request@mit.edu">sap-wug-request@mit.edu</a> a ??crit :
> >
> >> Send SAP-WUG mailing list submissions to
> >> <a moz-do-not-send="true" href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>
> >>
> >> To subscribe or unsubscribe via the World Wide Web, visit
> >> <a moz-do-not-send="true" href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a>
> >> or, via email, send a message with subject or body 'help' to
> >> <a moz-do-not-send="true" href="mailto:sap-wug-request@mit.edu">sap-wug-request@mit.edu</a>
> >>
> >> You can reach the person managing the list at
> >> <a moz-do-not-send="true" href="mailto:sap-wug-owner@mit.edu">sap-wug-owner@mit.edu</a>
> >>
> >> When replying, please edit your Subject line so it is more specific
> >> than "Re: Contents of SAP-WUG digest..."
> >>
> >>
> >> Today's Topics:
> >>
> >> 1. Re: Substitution restriction list (Mike Pokraka)
> >>
> >>
> >> ----------------------------------------------------------------------
> >>
> >> Message: 1
> >> Date: Thu, 28 Jun 2012 10:35:08 +0100 (BST)
> >> From: "Mike Pokraka" <<a moz-do-not-send="true" href="mailto:wug@workflowconnections.com">wug@workflowconnections.com</a>>
> >> Subject: Re: Substitution restriction list
> >> To: "SAP Workflow Users' Group" <<a moz-do-not-send="true" href="mailto:sap-wug@MIT.EDU">sap-wug@MIT.EDU</a>>
> >> Message-ID:
> >> <<a moz-do-not-send="true" href="mailto:efe2f511b736d57fb880f8fe2a85582c.squirrel@h.mail.aaisp.net.uk">efe2f511b736d57fb880f8fe2a85582c.squirrel@h.mail.aaisp.net.uk</a>>
> >> Content-Type: text/plain;charset=iso-8859-1
> >>
> >> G'Day,
> >>
> >> The BADI is WF_SUBSTITUTE but it's only for the UWL substitution dialog.
> >> Given that you're on SRM this will probably work for you.
> >>
> >> Regards,
> >> Mike
> >>
> >>
> >> On Thu, June 28, 2012 9:53 am, stephane wrote:
> >> > Hello,
> >> >
> >> > General question around the substitute, is there a BADI to control the
> >> > list of possible sustitute available to someone ?
> >> > I am not talking about a specific task but for instance I want someone
> >> > to provide the susbtitution to only someone within the hierarchy which
> >> > is at the same level or above ?
> >> >
> >> > I would like to apply this in SRM one client (RDS - SRM 7)
> >> > My main goal would be to use the BRF workflow but due to the
> >> complexity
> >> > I could go back to the old n step badi workflow
> >> >
> >> > Cheers
> >> > Stephane
> >> >
> >> >
> >> > Le mardi 26 juin 2012 ?? 00:28 -0400, <a moz-do-not-send="true" href="mailto:sap-wug-request@mit.edu">sap-wug-request@mit.edu</a> a
> ??crit
> >> :
> >> >
> >> >> Send SAP-WUG mailing list submissions to
> >> >> <a moz-do-not-send="true" href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>
> >> >>
> >> >> To subscribe or unsubscribe via the World Wide Web, visit
> >> >> <a moz-do-not-send="true" href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a>
> >> >> or, via email, send a message with subject or body 'help' to
> >> >> <a moz-do-not-send="true" href="mailto:sap-wug-request@mit.edu">sap-wug-request@mit.edu</a>
> >> >>
> >> >> You can reach the person managing the list at
> >> >> <a moz-do-not-send="true" href="mailto:sap-wug-owner@mit.edu">sap-wug-owner@mit.edu</a>
> >> >>
> >> >> When replying, please edit your Subject line so it is more specific
> >> >> than "Re: Contents of SAP-WUG digest..."
> >> >>
> >> >>
> >> >> Today's Topics:
> >> >>
> >> >> 1. Re: tRFC Errors in SWU2 (Mike Pokraka)
> >> >> 2. Re: tRFC Errors in SWU2 (Shaurya Jain)
> >> >> 3. Re: tRFC Errors in SWU2 (Mike Pokraka)
> >> >> 4. Re: tRFC Errors in SWU2 (Shaurya Jain)
> >> >>
> >> >>
> >> >>
> ----------------------------------------------------------------------
> >> >>
> >> >> Message: 1
> >> >> Date: Mon, 25 Jun 2012 19:29:03 +0100
> >> >> From: Mike Pokraka <<a moz-do-not-send="true" href="mailto:wug@workflowconnections.com">wug@workflowconnections.com</a>>
> >> >> Subject: Re: tRFC Errors in SWU2
> >> >> To: "SAP Workflow Users' Group" <<a moz-do-not-send="true" href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>>
> >> >> Message-ID:
> >> >> <<a moz-do-not-send="true" href="mailto:AF6F988D-C6B6-4410-9DD7-71FCB762DB1F@workflowconnections.com">AF6F988D-C6B6-4410-9DD7-71FCB762DB1F@workflowconnections.com</a>>
> >> >> Content-Type: text/plain; charset="us-ascii"
> >> >>
> >> >> Error message?
> >> >>
> >> >> On 25 Jun 2012, at 06:36, Shaurya Jain <<a moz-do-not-send="true" href="mailto:jain.shaurya@gmail.com">jain.shaurya@gmail.com</a>>
> >> wrote:
> >> >>
> >> >> Dear Experts,
> >> >>
> >> >> We are facing a problem with tRFC errors related to workflows.
> >> >>
> >> >> Many times in a day we receive users complaint in following areas:
> >> >>
> >> >> They have actioned the work item from their inbox but work item is
> >> not
> >> >> getting removed from their inbox.
> >> >> PM Notification created by user but workflow did not get triggered
> >> for
> >> >> the CREATE event.
> >> >> PO/PR release happened for a particular release code but workitem not
> >> >> delievered to next responsible agent.
> >> >> and many more like this.......
> >> >> Such cases are not happening always & most of the times things go
> >> fine.
> >> >>
> >> >> When I investigated in this issue more I found that tRFCs are in
> >> error
> >> >> in SWU2 log for TCodes ME54N, ME29N, IW21, etc. If I manually execute
> >> >> these LUWs then the respective problem gets resolved as the activity
> >> for
> >> >> database update happens & things move as they have to. So I have a
> >> >> workaround to resolve the problem temporarily.
> >> >>
> >> >> But I am still not able to find the root cause for this problem. Even
> >> my
> >> >> Basis team is not able to help me out in this case. On checking the
> >> >> System Setting from Information menu in SWU2/SM58 I found that values
> >> >> for parameters Connection Attempt [No.] is set to 30 & Attempt
> >> Interval
> >> >> [Mins] is set to 15.
> >> >>
> >> >> If anyone of you can provide any sort of help it would be really
> >> great.
> >> >>
> >> >> Regards,
> >> >> Shaurya Jain
> >> >> _______________________________________________
> >> >> SAP-WUG mailing list
> >> >> <a moz-do-not-send="true" href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a>
> >> >> <a moz-do-not-send="true" href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a>
> >> >> -------------- next part --------------
> >> >> An HTML attachment was scrubbed...
> >> >> URL:
> >> >>
> <a moz-do-not-send="true" href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20120625/74da4b73/attachment-0001.htm">http://mailman.mit.edu/pipermail/sap-wug/attachments/20120625/74da4b73/attachment-0001.htm</a>
> >> >>
> >> >> ------------------------------
> >> >>
> >> >> Message: 2
> >> >> Date: Mon, 25 Jun 2012 21:59:48 +0300
> >> >> From: Shaurya Jain <<a moz-do-not-send="true" href="mailto:jain.shaurya@gmail.com">jain.shaurya@gmail.com</a>>
> >> >> Subject: Re: tRFC Errors in SWU2
> >> >> To: "SAP Workflow Users' Group" <<a moz-do-not-send="true" href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>>
> >> >> Message-ID:
> >> >> <
> <a moz-do-not-send="true" href="mailto:CAFALVOOfFi7dxNu7Q5eumOFeA+ECP2Aq_pL0+wvBx6Z_aLaUpg@mail.gmail.com">CAFALVOOfFi7dxNu7Q5eumOFeA+ECP2Aq_pL0+wvBx6Z_aLaUpg@mail.gmail.com</a>>
> >> >> Content-Type: text/plain; charset="iso-8859-1"
> >> >>
> >> >> DB Error -9999
> >> >>
> >> >> Regards,
> >> >> Shaurya
> >> >>
> >> >> On Jun 25, 2012 9:39 PM, "Mike Pokraka" <<a moz-do-not-send="true" href="mailto:wug@workflowconnections.com">wug@workflowconnections.com</a>
> >
> >> >> wrote:
> >> >> >
> >> >> > Error message?
> >> >> >
> >> >> >
> >> >> > On 25 Jun 2012, at 06:36, Shaurya Jain <<a moz-do-not-send="true" href="mailto:jain.shaurya@gmail.com">jain.shaurya@gmail.com</a>>
> >> wrote:
> >> >> >
> >> >> > Dear Experts,
> >> >> >
> >> >> > We are facing a problem with tRFC errors related to workflows.
> >> >> >
> >> >> > Many times in a day we receive users complaint in following areas:
> >> >> >
> >> >> > They have actioned the work item from their inbox but work item is
> >> not
> >> >> getting removed from their inbox.
> >> >> > PM Notification created by user but workflow did not get triggered
> >> for
> >> >> the CREATE event.
> >> >> > PO/PR release happened for a particular release code but workitem
> >> not
> >> >> delievered to next responsible agent.
> >> >> > and many more like this.......
> >> >> > Such cases are not happening always & most of the times things go
> >> >> fine.
> >> >> >
> >> >> > When I investigated in this issue more I found that tRFCs are in
> >> error
> >> >> in
> >> >> SWU2 log for TCodes ME54N, ME29N, IW21, etc. If I manually execute
> >> these
> >> >> LUWs then the respective problem gets resolved as the activity for
> >> >> database
> >> >> update happens & things move as they have to. So I have a workaround
> >> to
> >> >> resolve the problem temporarily.
> >> >> >
> >> >> > But I am still not able to find the root cause for this problem.
> >> Even
> >> >> my
> >> >> Basis team is not able to help me out in this case. On checking the
> >> >> System
> >> >> Setting from Information menu in SWU2/SM58 I found that values for
> >> >> parameters Connection Attempt [No.] is set to 30 & Attempt Interval
> >> >> [Mins]
> >> >> is set to 15.
> >> >> >
> >> >> > If anyone of you can provide any sort of help it would be really
> >> >> great.
> >> >> >
> >> >> > Regards,
> >> >> > Shaurya Jain
> >> >> > _______________________________________________
> >> >> > SAP-WUG mailing list
> >> >> > <a moz-do-not-send="true" href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a>
> >> >> > <a moz-do-not-send="true" href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a>
> >> >> >
> >> >> > _______________________________________________
> >> >> > SAP-WUG mailing list
> >> >> > <a moz-do-not-send="true" href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a>
> >> >> > <a moz-do-not-send="true" href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a>
> >> >> >
> >> >> -------------- next part --------------
> >> >> An HTML attachment was scrubbed...
> >> >> URL:
> >> >>
> <a moz-do-not-send="true" href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20120625/4a435e09/attachment-0001.htm">http://mailman.mit.edu/pipermail/sap-wug/attachments/20120625/4a435e09/attachment-0001.htm</a>
> >> >>
> >> >> ------------------------------
> >> >>
> >> >> Message: 3
> >> >> Date: Mon, 25 Jun 2012 22:49:53 +0100
> >> >> From: Mike Pokraka <<a moz-do-not-send="true" href="mailto:wug@workflowconnections.com">wug@workflowconnections.com</a>>
> >> >> Subject: Re: tRFC Errors in SWU2
> >> >> To: "SAP Workflow Users' Group" <<a moz-do-not-send="true" href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>>
> >> >> Message-ID:
> >> >> <<a moz-do-not-send="true" href="mailto:7A53075A-C7F1-4AF1-A86C-0EB85E10DB54@workflowconnections.com">7A53075A-C7F1-4AF1-A86C-0EB85E10DB54@workflowconnections.com</a>>
> >> >> Content-Type: text/plain; charset="us-ascii"
> >> >>
> >> >> That sounds very much like a basis problem. Same error, different
> >> >> transactions...
> >> >>
> >> >> Check the system log around the time of the transaction (SM21), also
> >> >> maybe have a look for update errors (SM13). Very surprised basis
> >> can't
> >> >> help you further, might be worth another chat.
> >> >>
> >> >> Regards,
> >> >> Mike
> >> >>
> >> >>
> >> >>
> >> >> On 25 Jun 2012, at 19:59, Shaurya Jain <<a moz-do-not-send="true" href="mailto:jain.shaurya@gmail.com">jain.shaurya@gmail.com</a>>
> >> wrote:
> >> >>
> >> >> DB Error -9999
> >> >>
> >> >> Regards,
> >> >> Shaurya
> >> >>
> >> >> On Jun 25, 2012 9:39 PM, "Mike Pokraka" <<a moz-do-not-send="true" href="mailto:wug@workflowconnections.com">wug@workflowconnections.com</a>
> >
> >> >> wrote:
> >> >> >
> >> >> > Error message?
> >> >> >
> >> >> >
> >> >> > On 25 Jun 2012, at 06:36, Shaurya Jain <<a moz-do-not-send="true" href="mailto:jain.shaurya@gmail.com">jain.shaurya@gmail.com</a>>
> >> wrote:
> >> >> >
> >> >> > Dear Experts,
> >> >> >
> >> >> > We are facing a problem with tRFC errors related to workflows.
> >> >> >
> >> >> > Many times in a day we receive users complaint in following areas:
> >> >> >
> >> >> > They have actioned the work item from their inbox but work item is
> >> not
> >> >> getting removed from their inbox.
> >> >> > PM Notification created by user but workflow did not get triggered
> >> for
> >> >> the CREATE event.
> >> >> > PO/PR release happened for a particular release code but workitem
> >> not
> >> >> delievered to next responsible agent.
> >> >> > and many more like this.......
> >> >> > Such cases are not happening always & most of the times things go
> >> >> fine.
> >> >> >
> >> >> > When I investigated in this issue more I found that tRFCs are in
> >> error
> >> >> in SWU2 log for TCodes ME54N, ME29N, IW21, etc. If I manually execute
> >> >> these LUWs then the respective problem gets resolved as the activity
> >> >> for database update happens & things move as they have to. So I have
> >> a
> >> >> workaround to resolve the problem temporarily.
> >> >> >
> >> >> > But I am still not able to find the root cause for this problem.
> >> Even
> >> >> my Basis team is not able to help me out in this case. On checking
> >> the
> >> >> System Setting from Information menu in SWU2/SM58 I found that values
> >> >> for parameters Connection Attempt [No.] is set to 30 & Attempt
> >> >> Interval [Mins] is set to 15.
> >> >> >
> >> >> > If anyone of you can provide any sort of help it would be really
> >> >> great.
> >> >> >
> >> >> > Regards,
> >> >> > Shaurya Jain
> >> >> > _______________________________________________
> >> >> > SAP-WUG mailing list
> >> >> > <a moz-do-not-send="true" href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a>
> >> >> > <a moz-do-not-send="true" href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a>
> >> >> >
> >> >> > _______________________________________________
> >> >> > SAP-WUG mailing list
> >> >> > <a moz-do-not-send="true" href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a>
> >> >> > <a moz-do-not-send="true" href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a>
> >> >> >
> >> >>
> >> >> _______________________________________________
> >> >> SAP-WUG mailing list
> >> >> <a moz-do-not-send="true" href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a>
> >> >> <a moz-do-not-send="true" href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a>
> >> >> -------------- next part --------------
> >> >> An HTML attachment was scrubbed...
> >> >> URL:
> >> >>
> <a moz-do-not-send="true" href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20120625/f9c95eef/attachment-0001.htm">http://mailman.mit.edu/pipermail/sap-wug/attachments/20120625/f9c95eef/attachment-0001.htm</a>
> >> >>
> >> >> ------------------------------
> >> >>
> >> >> Message: 4
> >> >> Date: Tue, 26 Jun 2012 07:28:07 +0300
> >> >> From: Shaurya Jain <<a moz-do-not-send="true" href="mailto:jain.shaurya@gmail.com">jain.shaurya@gmail.com</a>>
> >> >> Subject: Re: tRFC Errors in SWU2
> >> >> To: "SAP Workflow Users' Group" <<a moz-do-not-send="true" href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>>
> >> >> Message-ID:
> >> >> <CAFALVONy_J17YHEVHk=ZPsaK4yKqGYWge1AeVPO6By34BY_C=
> <a moz-do-not-send="true" href="mailto:Q@mail.gmail.com">Q@mail.gmail.com</a>>
> >> >> Content-Type: text/plain; charset="iso-8859-1"
> >> >>
> >> >> Thanks Susan & Mike for responding.
> >> >>
> >> >> I will get in touch with the Basis team again & will update the forum
> >> >> with
> >> >> solution.
> >> >>
> >> >> Regards,
> >> >> Shaurya Jain
> >> >>
> >> >>
> >> >> On Tue, Jun 26, 2012 at 12:49 AM, Mike Pokraka
> >> >> <<a moz-do-not-send="true" href="mailto:wug@workflowconnections.com">wug@workflowconnections.com</a>>wrote:
> >> >>
> >> >> > That sounds very much like a basis problem. Same error, different
> >> >> > transactions...
> >> >> >
> >> >> > Check the system log around the time of the transaction (SM21),
> >> also
> >> >> maybe
> >> >> > have a look for update errors (SM13). Very surprised basis can't
> >> help
> >> >> you
> >> >> > further, might be worth another chat.
> >> >> >
> >> >> > Regards,
> >> >> > Mike
> >> >> >
> >> >> >
> >> >> >
> >> >> > On 25 Jun 2012, at 19:59, Shaurya Jain <<a moz-do-not-send="true" href="mailto:jain.shaurya@gmail.com">jain.shaurya@gmail.com</a>>
> >> wrote:
> >> >> >
> >> >> > DB Error -9999
> >> >> >
> >> >> > Regards,
> >> >> > Shaurya
> >> >> >
> >> >> > On Jun 25, 2012 9:39 PM, "Mike Pokraka"
> >> <<a moz-do-not-send="true" href="mailto:wug@workflowconnections.com">wug@workflowconnections.com</a>>
> >> >> > wrote:
> >> >> > >
> >> >> > > Error message?
> >> >> > >
> >> >> > >
> >> >> > > On 25 Jun 2012, at 06:36, Shaurya Jain <<a moz-do-not-send="true" href="mailto:jain.shaurya@gmail.com">jain.shaurya@gmail.com</a>>
> >> >> wrote:
> >> >> > >
> >> >> > > Dear Experts,
> >> >> > >
> >> >> > > We are facing a problem with tRFC errors related to workflows.
> >> >> > >
> >> >> > > Many times in a day we receive users complaint in following
> >> areas:
> >> >> > >
> >> >> > > They have actioned the work item from their inbox but work item
> >> is
> >> >> not
> >> >> > getting removed from their inbox.
> >> >> > > PM Notification created by user but workflow did not get
> >> triggered
> >> >> for
> >> >> > the CREATE event.
> >> >> > > PO/PR release happened for a particular release code but workitem
> >> >> not
> >> >> > delievered to next responsible agent.
> >> >> > > and many more like this.......
> >> >> > > Such cases are not happening always & most of the times things go
> >> >> fine.
> >> >> > >
> >> >> > > When I investigated in this issue more I found that tRFCs are in
> >> >> error
> >> >> > in SWU2 log for TCodes ME54N, ME29N, IW21, etc. If I manually
> >> execute
> >> >> these
> >> >> > LUWs then the respective problem gets resolved as the activity for
> >> >> database
> >> >> > update happens & things move as they have to. So I have a
> >> workaround
> >> >> to
> >> >> > resolve the problem temporarily.
> >> >> > >
> >> >> > > But I am still not able to find the root cause for this problem.
> >> >> Even my
> >> >> > Basis team is not able to help me out in this case. On checking the
> >> >> System
> >> >> > Setting from Information menu in SWU2/SM58 I found that values for
> >> >> > parameters Connection Attempt [No.] is set to 30 & Attempt Interval
> >> >> [Mins]
> >> >> > is set to 15.
> >> >> > >
> >> >> > > If anyone of you can provide any sort of help it would be really
> >> >> great.
> >> >> > >
> >> >> > > Regards,
> >> >> > > Shaurya Jain
> >> >> > > _______________________________________________
> >> >> > > SAP-WUG mailing list
> >> >> > > <a moz-do-not-send="true" href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a>
> >> >> > > <a moz-do-not-send="true" href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a>
> >> >> > >
> >> >> > > _______________________________________________
> >> >> > > SAP-WUG mailing list
> >> >> > > <a moz-do-not-send="true" href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a>
> >> >> > > <a moz-do-not-send="true" href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a>
> >> >> > >
> >> >> > _______________________________________________
> >> >> > SAP-WUG mailing list
> >> >> > <a moz-do-not-send="true" href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a>
> >> >> > <a moz-do-not-send="true" href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a>
> >> >> >
> >> >> > _______________________________________________
> >> >> > SAP-WUG mailing list
> >> >> > <a moz-do-not-send="true" href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a>
> >> >> > <a moz-do-not-send="true" href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a>
> >> >> >
> >> >> >
> >> >> -------------- next part --------------
> >> >> An HTML attachment was scrubbed...
> >> >> URL:
> >> >>
> <a moz-do-not-send="true" href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20120626/0667fc97/attachment.htm">http://mailman.mit.edu/pipermail/sap-wug/attachments/20120626/0667fc97/attachment.htm</a>
> >> >>
> >> >> ------------------------------
> >> >>
> >> >> _______________________________________________
> >> >> SAP-WUG mailing list
> >> >> <a moz-do-not-send="true" href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a>
> >> >> <a moz-do-not-send="true" href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a>
> >> >>
> >> >>
> >> >> End of SAP-WUG Digest, Vol 91, Issue 26
> >> >> ***************************************
> >> > _______________________________________________
> >> > SAP-WUG mailing list
> >> > <a moz-do-not-send="true" href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a>
> >> > <a moz-do-not-send="true" href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a>
> >> >
> >>
> >>
> >>
> >>
> >> ------------------------------
> >>
> >> _______________________________________________
> >> SAP-WUG mailing list
> >> <a moz-do-not-send="true" href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a>
> >> <a moz-do-not-send="true" href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a>
> >>
> >>
> >> End of SAP-WUG Digest, Vol 91, Issue 28
> >> ***************************************
> >
> >
> > _______________________________________________
> > SAP-WUG mailing list
> > <a moz-do-not-send="true" href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a>
> > <a moz-do-not-send="true" href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a>
> >
>
>
> _______________________________________________
> SAP-WUG mailing list
> <a moz-do-not-send="true" href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a>
> <a moz-do-not-send="true" href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a>
>
</pre>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
SAP-WUG mailing list
<a class="moz-txt-link-abbreviated" href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a>
<a class="moz-txt-link-freetext" href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</a>
</pre>
</blockquote>
<br>
<br>
</body>
</html>