Regarding workflow to get manager rule 168

Hello HR Gurus,
Well I am an abaper .
while testing the rule 168 (to get the superior of person in workflow ) I can get the superior of person by passing
Extended object id = Position
and
object type = S
but when I try to find the superior by passing
Extended object id = SAP log on name
and
object type as US
I am unable to get the superior ..
Please advice what could be the cause of it . as it is giving me supervisor when entering the details with position and employee id but not when entering sap logon id .
in another client(IDES) it working fine with saplogon id ie US but not with position i.e. S
details in info type 105(communication ) is maintained .
does it has some thing to do with evaluation path ..?
please advice what could be the cause of it .. u r all advice will be appreciated

Hi brijesh,
The main thing is that the relationships between the objects were not maintained based on the sap logon id, are maintained only by employee id(OBJID), Though u r giving the SAP Logon id , u should get the corresponding Employee id then proceed furthur to get the supervisor , it would resolve your problem.
Regards,
Narendra Kumar Katuri.

Similar Messages

Rule 168 to work with org structure and not relationships

Hi,
I would like to use rule 168 to work with the organizartional structure and not the relationships maintained in PO10 organizational unit.
this is because i want the agent to be the person with the red hat and not the a002 relationship maintained in organizational unit. i tried using rule 157 but it does the same thing and determines agent based on relationships maintained in org unit.
basically i dont want the agent to be any of the line mangers which may have been set up, i want it to be the red hat of the org structure
does anyone know how i can do this, or will i need to delete the relationships between staffing?
Thanks
Forhad

Here is a code example to read from the tables in base to the personnel number emulating the SWE_GET_MANAGER function, I hope this helps. Regards.
Z GET MANAGER *******************
***Gets the position for the creator of the requisition
clear V_OBJID.
select single objid into V_OBJID from HRP1001
 where otype = 'S' and
 plvar = '01' and
 rsign = 'A' and
 relat = '008' and
 begda <= sy-datum and
 endda >= sy-datum and
 infty = '1001' and
 sclas = 'US' and
 sobid = pt_cont-VALUE+2.
if sy-subrc = 0.
 valid if the user has personnel number don't proceed to look for the chief
 clear V_OBJID2.
 select single objid into V_OBJID2 from HRP1001
 where otype = 'S' and
 objid = V_OBJID and
 plvar = '01' and
 rsign = 'A' and
 relat = '008' and
 begda <= sy-datum and
 endda >= sy-datum and
 infty = '1001' and
 sclas = 'P'.
 if sy-subrc <> 0.
 if the user exist in the correspondant date gets the chief position
 clear V_POS_SOBID_CH.
 select single sobid into V_POS_SOBID_CH from HRP1001
 where otype = 'S' and
 objid = V_OBJID and
 plvar = '01' and
 rsign = 'A' and
 relat = '002' and
 begda <= sy-datum and
 endda >= sy-datum and
 infty = '1001' and
 sclas = 'S'.
 if sy-subrc = 0.
 if the relationship with a chief position exist gets the chief user id
 clear V_US_SOBID_CH.
 select single sobid into V_US_SOBID_CH from HRP1001
 where otype = 'S' and
 objid = V_POS_SOBID_CH and
 plvar = '01' and
 rsign = 'A' and
 relat = '008' and
 begda <= sy-datum and
 endda >= sy-datum and
 infty = '1001' and
 sclas = 'US'.
 IF sy-subrc = 0.
 clear pt_actor.
 refresh pt_actor.
 pt_actor-otype = 'US'.
 pt_actor-objid = V_US_SOBID_CH.
 append pt_actor.
 endif.
 endif.
 endif.
endif.
***************End of Z GET MANAGER.*****************************

Rule 168 unable to get superior

I am trying to activate a workflow but getting error . The technical log details shows that the superior(manager) cannot be resolved in rule 168 . while testing the rule 168 I can get the superior of person by passing
Extended object id = Position
and
object type = S
but when I try to find the superior by passing
Extended object id = SAP log on name
and
object type as US
I am unable to get the superior ..
Please advice what could be the cause of it . do we need to change some HR setting ie saving relation in some info type or some thing can be done in workflow to resolve it .

while testing the rule 168 I can get the superior of person by passing
Extended object id = Position
and
object type = S
but when I try to find the superior by passing
Extended object id = SAP log on name
and
object type as US
I am unable to get the superior ..
actally when we use position or empid whith respective id type the testing of rule seems to be working fine but when we use object type 'US' and provide sap id it does not find it superior .. the all cases are in testing of rule using pfac_dis and whith the same empids .
as these all cases are in pfac_dis by default the rule uses type US ? or we have some setting for it

Agent Not Found for rule 168 in Travel Management WF WS20000040

Hi,
I got a strange error occurring that I can not quite figure out. I am using a copy of a standard delivered SAP Work flow for Trip Approval (WS20000040) that is identical to the SAP delivered workflow except without the expense department tasks (we only need manager approval). I also updated the agent assignment for tasks TS20000131, TS20000139, and TS20000189 to be General Tasks. When an employee creates a trip, the workflow is started properly and goes to the first workflow step which is user decision step 416. It uses rule 168 to determine the manager of the workflow initiator. This works properly. The manager goes to their inbox and executes this workflow step. The trip changed and trip approved buttons work fine, but if the manager chooses the reject button, the form is closed and the workflow stops with an error. The next step down the reject path is an activity step 476 - enter and send message. This runs task TS20000139. The agent assignment also uses rule 168 to determine the manager of the workflow initiator. The same agent should be choosen for both this step and the previous step since the workflow initiator is the same for both and the same rule is being used. The advance with dialog check box is checked in both steps. Both step refer to tasks that are both marked as synchronus object methods and object method with dialog.
For testing purposes, I changed the agent determination in both workflow steps to be the workflow initiator and ran it. The workflow stopped at the approve trip facts step as expected and when I choose reject trip, I was taken immediately to the create mail task that task TS20000139 runs as it should. I tried creating a trip as the employee and the manager and it work properly in both occasions regardless of which user the trip was created under when just workflow initiator is used for agent determination.
I ran SWI2_DIAG to look at the errors that occurred when it stopped in error when I used rule 168. According to the error message, the approve trip fact step completed successfully, but the enter and send message step failed with no agent found. Following is the error message:
Workflow WS90000048 no. 000000277688 activity 0000000476 role 'AC00000168': No agent found
What I don't understand is that the agent determination for the approve trip facts step which works perfectly uses the same agent determination as the enter and send message step which is terminating with an error. Also when I change both steps to use workflow initiator as the agent, then they both work perfectly.
Help, Please
Gregg
Edited by: Gregg Hinkle on Feb 12, 2008 4:48 PM

Thanks Martin,
I used your suggestion and passed the actual agent from the prior task to the container and then used this value as an expression to determine the agent for the step that was causing me pain. Now the workflow step is continuing properly and automatically bringing up the create message step as expected.
Arghadip,
I tried your idea about creating a copy of the standard delivered workflow and even set it as a general task and I got the same result as with the standard SAP (error with no agent found).
Thanks again for everyone's assistance

3000 Assignment manager rules and 3000 workflows

Our business have given 3000 Business rules for the routing purpose. To implement this we need to create 3000 assignement manager rules and 3000 workflows. I know that there is no limitation in SOD for creating Rules and workflows.
What i need to know , has anyone created so many Rules and workflows? If Yes , then was it all done manually?
Thanks.
S

What are the performance implications of Workflow Rules? ** Workflow Rules are evaluated in sequence and synchronously. Therefore, unless all the rules are evaluated, the overall update is not completed. This will add a certain amount of latency. For example, each task creation can add as much as 20% latency to an update and emails about 5%. Expressions take less time to evaluate. To minimize latency, add restrictive conditions and use workflows judiciously.

Using Rule 168, SWX_GET_MANAGER and Chief Position

We have enabled standard SAP Travel Workflow WS20000040 - Approve Trip. We are not currently using OM relationships A002 (Reports Line to) or B002 (Is Line Supervisor of). We currently identify the Line Manager of the employee using the Chief Position designation A 012 and would like to use this for Trip approvals in lieu of building all of these additional relationships.
Rule 168 is bound to the workflow. According to the documentation associated with the rule, it seems that the rule should work with either the A002 or A012 relationship. However, we only seem to be getting a superior identified when relationship A002/B002 exists.
Are there additional configuration or parameter settings that we might need to consider to make the manager (agent) determined properly exclusively with the Chief Position assignment?
Thanks for any guidance you can provide.
Regards,
Edited by: Bruce Hull on Jul 24, 2008 5:37 PM
Edited by: Bruce Hull on Jul 24, 2008 5:37 PM
Edited by: Bruce Hull on Jul 24, 2008 7:29 PM

What I found through trial and error is that rule 168 does indeed evaluate the A012 relationship by default with no change in the standard evaluation path. In our testing system, the "Chief" postion was not properly assigned. Once this was resolved, the workflow works properly.
As a side note, I also learned that you must have the parameter WFLOW VAPOS set for the rule to properly look up the organizational structure when a position (and chief) are vacant.

Can we create a workflow in Solution Manager ?

Hi Friends,
Actually I have a requirement to create a workflow in solution manager.
The requirement is to create a wf for issue log. As soon as a new issue (support message) is created then the wf should get triggered and send out a mail to the resp. person. It just a sending a mail between issue created and responsible person. Can anyone please let me know if we create a wf in Solman or not ? If so please provide me some related buss. obj for that. thanks
Grateful to your help.
Srithan

If you want to Place certain actions after status change of a transaction, it's better to do this with an action profile and a condition for that action:
In Solman check SPRO path:
CRM>Transactions>Basic settings-->Define transaction types
In this activity double click the transaction type to find out what the action profile is:
Now go to:
CRM>Basic functions>Actions>Actions in transactions>Change actions and conditions-->Define action profiles and actions
Here you can add an action definition on the action profile, this can be methods, workflow or in your case a smartform mail.
If the action profile is a SAP standard (doesn't begin with Z) it is advisable to copy the standard. Also, this is more of a CRM/Solman consultant issue, so you may have to involve such a consultant
Now go to
CRM>Basic functions>Actions>Actions in transactions>Change actions and conditions-->Define Conditions
Here you can add conditions which will cause the action to be executed.
Kind regards, Rob Dielemans

Can we create a workflow in Solution Manager for Tester Worklist ?

Hi Friends,
Actually I have a requirement to create a workflow in solution manager.
The requirement is to create a workflow for issue log(tester worklist). As soon as a new issue (support message) is created then the wf should get triggered and send out a mail to the resp. person. It just a sending a mail between issue creater and responsible person.
Can anyone please let me know if we create a wf in Solman or not ? If so please provide me some related buss. obj for that. thanks
Is there any standard workflow (or similar to that) to make it automatic ? Once the message is created then a mail to the responsible person should go.
Grateful to your help.
Srithan

Sorry Raguraman,
I am unable to check those tcodes as I havenot got the authorizations for those. after several mails I got some basic wf developer tcode access. I am not sure whether I have to create a new workflow for this or I can go with some built-in technology to send mail when a new message (tcode: stwb_work) is created.
can raguraman or anyone please help me on doing this ?
if the solman has provided the standard for sending mails when a new message is created/changed to the responsible person.
grateful for your help
Regards,
srithan

Workflow for Treasury management

Hi ,
Can anybody tell me how should i configure the workflow for Treasury management ? . Once the below t codes change the mail should go to the Treasurer ? And here the Treasurer needs to pick up on Roles assigned ..
For the t codes TI10 , TI11, TI37 should get triggeted ? .
Thnaks&regards
Srinivas

Hi,
I hope you know the process of modeling a workflow. If not follow the tutorial in the help document:
http://help.sap.com/saphelp_nw2004s/helpdata/en/fb/135962457311d189440000e829fbbd/frameset.htm
If you have already done some workflow modeling then you can proceed as follows:
1. Check for any standard events. Go to transaction SWEL and see if there are any events triggered by the standard transaction. If yes then you can build your own workflow for that event.
If there are no standard events then you can raise them from either of the following based on the availability of the same:
2. Are change documents active? Once you perform the transaction go to transaction SE11 and view the contents of the table CDHDR for the entries with your name as the creator. If the transaction writes a change document then you can trigger off a workflow through an event which is linked to the change document object. For more details go here:
http://help.sap.com/saphelp_nw2004s/helpdata/en/c5/e4aeef453d11d189430000e829fbbd/frameset.htm
3. If the transaction has a status management built in then you can raise through this as well. For more information see this:
http://help.sap.com/saphelp_nw2004s/helpdata/en/c5/e4aed5453d11d189430000e829fbbd/frameset.htm
4. If you are not lucky in either of the steps below then you need to implements a User Exit or a BADI and raise an event through the function module: SWE_EVENT_CREATE.
Hope this helps,
Sudhi

Agent not resolved for rule 168(US Manger)

I am activating Travel request approval WF 20000050 in the event linkage is working properly ie the workflow is getting triggered and end in error . the technical logs shows that rule resolution to 00000168 to get the manager is not resolved (agent not resolved ) .
The task is general so there should be no conflicts in finding manager .
The HR consultants has created the org structure and it should work fine .
Please advice what could be the cause of it and does it has some thing to do with SWU3 some steps in classify task as general were red ( now I have have executed it and is so green now )
Please throw some lights also on how can I test the rule .. 00000168 (if there is some error in HR config ) or do I need to some thing in PFAC

Hi Arghadip,
any ways i found that there is some thing wrong in HR setting because agent resolution is working fine in IDES OR do we need to do some thing in that rule some thing like activation or it's some problem with HR configuration ..
Thanks in tons u r answers are very helpful ..
well i will need lot of u r help )-: .. hope u will enjoy helping me (-:

Getting WLI Workflow Instance getting NULL.

Hi All WLI Users,
I am getting following problem while executing WLI workflow. After work
flow gets triggered by an XML event and instantiated, after some time workflow
instance becomes null.
and the execution is aborted. Kindly give me a solution to this problem.
Thanks
Kiran

Hi tony
It won't be possible for us to send us the workflow, beacuse it has
lots of interfaces
like MQ series and TCP/IP adpater.
But I can explain u in brief the workflow.
Workflow sends message to HOST1 after getting successfull response
from HOST1 it sends
another request to HOST2 and waits for the response.
Now this can iterate for say 200-500 times (depends on response
from HOST1).
Each message length is aroung 5000 bytes.During this iteration the
instance somehow sets to NULL.
I hope you can simulate the same at your end.
Also note we also do XML transformation before sending the request.
Thanks
"tony lodge" <[email protected]> wrote in message
news:[email protected]...
Hi
I recommend given this level of detail you open a case, what I amseeing
looks like a valid bug. Please provide the sample workflow if possible
Tony
"Saurabh" <[email protected]> wrote in message
news:[email protected]...
Hi,
The Versio ni am using is wlisp2.1 (service pack 2.1)
and Exception Stack trace is as follows,
<Mar 30, 2002 1:53:55 AM GMT-05:00> <Error> <T3Services> <Workflowtrace:Template=28003
Template Definition=31003
Instance=null>
Workflow warning: com.bea.wlpi.common.WorkflowException: The system
could
not
find the specified workflow instance: null.
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.getWorkflowInsta
nce(WorkflowProcessorBean.java:537)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.getWorkflowInsta
nceData(WorkflowProcessorBean.java:551
atcom.bea.wlpi.server.workflow.Variable.setValue(Variable.java:92)
atcom.bea.wlpi.server.workflow.Workflow.setVariable(Workflow.java:833)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.setVariableValue
(WorkflowProcessorBean.java:1017)
at
com.bea.wlaiplugin.server.WLAIServiceImpl.execute(WLAIServiceImpl.java:211)
atcom.bea.wlpi.server.workflow.action.ActionPlugin.execute(ActionPlugin.java:1
23)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
atcom.bea.wlpi.server.workflow.Decision.activate(Decision.java:72)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Task.markDone(Task.java:164)
at
com.bea.wlpi.server.workflow.action.ActionTaskDone.execute(ActionTaskDone.ja
va:50)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.executeActions(W
orkflowProcessorBean.java:1194)
at
com.bea.wlpi.server.workflow.Task.executeActions(Task.java:90)
at com.bea.wlpi.server.workflow.Task.activate(Task.java:119)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.activateSuccesso
rs(WorkflowProcessorBean.java:1344)
at com.bea.wlpi.server.workflow.Start.activate(Start.java:168)
at
com.bea.wlpi.server.workflow.Workflow.start(Workflow.java:657)
atcom.bea.wlpi.server.workflow.Workflow.instantiate(Workflow.java:617)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean$1.invoke(Workflo
wProcessorBean.java:713)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.performWithError
Handling(WorkflowProcessorBean.java:11
32)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean.instantiate(Work
flowProcessorBean.java:709)
at
com.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean_h7kt4j_EOImpl.in
stantiate(WorkflowProcessorBean_h7kt4j
_EOImpl.java:78)
at
com.bea.wlpi.server.eventprocessor.EventProcessor.checkTrigger(EventProcesso
r.java:358)
at
com.bea.wlpi.server.eventprocessor.EventProcessor.onEvent(EventProcessor.jav
a:244)
at
com.bea.wlpi.server.eventlistener.EventListenerBean.onMessage(EventListenerB
ean.java:130)
at
weblogic.ejb20.internal.MDListener.execute(MDListener.java:254)
atweblogic.ejb20.internal.MDListener.onMessage(MDListener.java:206)
at
weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1864)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:1819)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
<Mar 30, 2002 1:53:55 AM GMT-05:00> <Notice> <EJB> <Error markingtransaction
for rollback: java.lang.IllegalStateException:
Cannot mark the transaction for rollback. xid=4883:97fdb06e981bb8b8,status=Rolled
back. [Reason=weblogic.transaction.interna
l.TimedOutException: Transaction timed out after 89 seconds
Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie
sOwedOthers=0,seconds
since begin=89,seconds left
=60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread
Group> > for Queue: 'default',ServerResourceInfo[weblo
gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
er]=(state=active),properties=({weblogic.jdbc=t3:
>
file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)]
java.lang.IllegalStateException: Cannot mark the transaction for
rollback.
xid=4883:97fdb06e981bb8b8,
status=Rolled back. [Re
ason=weblogic.transaction.internal.TimedOutException: Transaction timedout after
89 seconds
Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie
sOwedOthers=0,seconds
since begin=89,seconds left
=60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread
Group> > for Queue: 'default',ServerResourceInfo[weblo
gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
er]=(state=active),properties=({weblogic.jdbc=t3:
>
file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)]
at
weblogic.transaction.internal.TransactionImpl.throwIllegalStateException(Tra
nsactionImpl.java:1486)
at
weblogic.transaction.internal.TransactionImpl.setRollbackOnly(TransactionImp
l.java:466)
at
weblogic.ejb20.manager.BaseEJBManager.handleSystemException(BaseEJBManager.j
ava:255)
at
weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:21
5)
at
weblogic.ejb20.manager.StatefulSessionManager.preInvoke(StatefulSessionManag
er.java:371)
at
weblogic.ejb20.manager.StatefulSessionManager.remove(StatefulSessionManager.
java:756)
at
weblogic.ejb20.internal.StatefulEJBObject.remove(StatefulEJBObject.java:87)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean_h7kt4j_EOImpl.re
move(WorkflowProcessorBean_h7kt4j_EOIm
pl.java:856)
at
com.bea.wlpi.server.eventprocessor.EventProcessor.clearSessionBeans(EventPro
cessor.java:510)
at
com.bea.wlpi.server.eventprocessor.EventProcessor.onEvent(EventProcessor.jav
a:284)
at
com.bea.wlpi.server.eventlistener.EventListenerBean.onMessage(EventListenerB
ean.java:130)
at
weblogic.ejb20.internal.MDListener.execute(MDListener.java:254)
atweblogic.ejb20.internal.MDListener.onMessage(MDListener.java:206)
at
weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1864)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:1819)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
javax.transaction.TransactionRolledbackException: EJB Exception: :weblogic.transaction.internal.TimedOutException:
Transacti
on timed out after 89 seconds
Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie
sOwedOthers=0,seconds
since begin=89,seconds left
=60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread
Group> > for Queue: 'default',ServerResourceInfo[weblo
gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
er]=(state=active),properties=({weblogic.jdbc=t3:
>
file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)
at
weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransaction
Impl.java:1122)
at
weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTr
ansactions(ServerTransactionManagerImp
l.java:441)
at
weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManag
erImpl.java:1581)
at
weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTran
sactionManagerImpl.java:404)
at
weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManage
rImpl.java:1547)
at java.lang.Thread.run(Thread.java:484)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Transaction timed out after 89seconds
>
Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie
sOwedOthers=0,seconds
since begin=89,seconds left
=60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread
Group> > for Queue: 'default',ServerResourceInfo[weblo
gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
er]=(state=active),properties=({weblogic.jdbc=t3:
>
file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)
- with nested exception:
[weblogic.transaction.internal.TimedOutException: Transaction timed out
after> > 89 seconds> >>Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie> sOwedOthers=0,seconds> > since begin=89,seconds left> > =60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread> Group> > for Queue: 'default',ServerResourceInfo[weblo
gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
er]=(state=active),properties=({weblogic.jdbc=t3:
>
file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)]
at
weblogic.transaction.internal.TransactionImpl.throwRollbackException(Transac
tionImpl.java:1475)
at
weblogic.transaction.internal.ServerTransactionImpl.registerSynchronization(
ServerTransactionImpl.java:435)
at
weblogic.ejb20.internal.TxManager.registerSynchronization(TxManager.java:157
at
weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:21
0)
at
weblogic.ejb20.manager.StatefulSessionManager.preInvoke(StatefulSessionManag
er.java:371)
at
weblogic.ejb20.manager.StatefulSessionManager.remove(StatefulSessionManager.
java:756)
at
weblogic.ejb20.internal.StatefulEJBObject.remove(StatefulEJBObject.java:87)
atcom.bea.wlpi.server.workflowprocessor.WorkflowProcessorBean_h7kt4j_EOImpl.re
move(WorkflowProcessorBean_h7kt4j_EOIm
pl.java:856)
at
com.bea.wlpi.server.eventprocessor.EventProcessor.clearSessionBeans(EventPro
cessor.java:510)
at
com.bea.wlpi.server.eventprocessor.EventProcessor.onEvent(EventProcessor.jav
a:284)
at
com.bea.wlpi.server.eventlistener.EventListenerBean.onMessage(EventListenerB
ean.java:130)
at
weblogic.ejb20.internal.MDListener.execute(MDListener.java:254)
atweblogic.ejb20.internal.MDListener.onMessage(MDListener.java:206)
at
weblogic.jms.client.JMSSession.onMessage(JMSSession.java:1864)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:1819)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
; nested exception is:
weblogic.transaction.RollbackException: Transaction timed outafter 89
seconds
Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie
sOwedOthers=0,seconds
since begin=89,seconds left
=60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread
Group> > for Queue: 'default',ServerResourceInfo[weblo
gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
er]=(state=active),properties=({weblogic.jdbc=t3:
>
file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)
- with nested exception:
[weblogic.transaction.internal.TimedOutException: Transaction timed out
after> > 89 seconds> >>Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie> sOwedOthers=0,seconds> > since begin=89,seconds left> > =60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread> Group> > for Queue: 'default',ServerResourceInfo[weblo
gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
er]=(state=active),properties=({weblogic.jdbc=t3:
>
file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)]
weblogic.transaction.internal.TimedOutException: Transaction timed outafter 89
seconds
Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie
sOwedOthers=0,seconds
since begin=89,seconds left
=60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread
Group> > for Queue: 'default',ServerResourceInfo[weblo
gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
er]=(state=active),properties=({weblogic.jdbc=t3:
>
file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)
at
weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransaction
Impl.java:1122)
at
weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTr
ansactions(ServerTransactionManagerImp
l.java:441)
at
weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManag
erImpl.java:1581)
at
weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTran
sactionManagerImpl.java:404)
at
weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManage
rImpl.java:1547)
at java.lang.Thread.run(Thread.java:484)
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Transaction timed out after 89seconds
>
Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie
sOwedOthers=0,seconds
since begin=89,seconds left
=60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread
Group> > for Queue: 'default',ServerResourceInfo[weblo
gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
er]=(state=active),properties=({weblogic.jdbc=t3:
>
file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)
- with nested exception:
[weblogic.transaction.internal.TimedOutException: Transaction timed out
after> > 89 seconds> >>Xid=4883:97fdb06e981bb8b8(510078),Status=Active,numRepliesOwedMe=0,numReplie> sOwedOthers=0,seconds> > since begin=89,seconds left> > =60,activeThread=Thread[ExecuteThread: '4' for queue: 'default',5,Thread> Group> > for Queue: 'default',ServerResourceInfo[weblo
gic.jdbc.jts.Connection]=(state=ended,assigned=none),SCInfo[wlidomain+myserv
er]=(state=active),properties=({weblogic.jdbc=t3:
>
file://192.193.249.82:7220}),OwnerTransactionManager=ServerTM[ServerCoordina
torDescriptor=(CoordinatorURL=myserver+192.193.249.82:
7220+wlidomain+,Resources={})],CoordinatorURL=myserver+192.193.249.82:7220+wlidomain+)]
at
weblogic.transaction.internal.TransactionImpl.throwRollbackException(Transac
tionImpl.java:1475)
at
weblogic.transaction.internal.ServerTransactionImpl.registerSynchronization(
ServerTransactionImpl.java:435)
at
weblogic.ejb20.internal.TxManager.registerSynchronization(TxManager.java:157
at
weblogic.ejb20.manager.BaseEJBManager.setupTxListener(BaseEJBManager.java:21
0)
at
weblogic.ejb20.manager.StatefulSessionManager.preInvoke(StatefulSessionManag
er.java:371)
at
weblogic.ejb20.manager.StatefulSessionManager.remove(StatefulSessionManager.
java:756)
at
weblo

Few questions regarding Training and event management

Dear All,
Can you please help me with the following queries regarding Training and Event Management:
1. How to freeze a completed business event so that no changes to its record (like delete/update attendee details or event detail) is possible?
2. How to get feedback from attendee/faculty with a predefined format with rating (1-4 scale)
3. How to maintain department and category wise training man/hrs or training man/days?
Any help will be appreciated.
Regards,
Toa

Hi Toa,
1. Run report RHHISTO0 via SA38. Once the business event is flagged as "historical" no further changes can be done.
3. SM30 - T77S0 - Make the following swtiches active:
SEMIN AINST
SEMIN APART
Then when events are followed up, these training data is recorded to employee 2002 infotype. You can report on it via PT90 (for department-based selection use "Further selections")
Regards,
Dilek

Regarding Workflow condition

Hello,
i need help regarding workflow condition..
When the Owner of the record gets changed to a specific user i want to create a set of tasks automatically created,.. is it possible using workflows, if possible what is the trigger event i have to use and what is the workflow condition.. please help me out its very urgent

Hi again,
i have used the following:
Trigger Event : when modified record saved
Condition : FieldValue('<Owner>') = "Jenny Adams"
and created list of actions for creating tasks.. but i think there is problem with condition.. please help me with condition.. i also tried
[<Owner>]='Jenny Adams'
[<Owner>]="Jenny Adams"
FieldValue('<Owner>') = 'Jenny Adams'

Regarding workflow suspension(entry in table SWP_SUSPEN)

Hi Experts,
I have a workflow whose one of the workitem goes into enqueue error during it's processing when user tries to perform some parallel activity , now when user stops the parallel activity & come back to his inbox, it allows him to process the workitem properly. (That is workitem is successfully processed.....status is completed). But after this workitem execution, the workflow hangs / gets suspended. Step histroy of this workitem shows there was an error when processing this workitem (Enqueue error) even though finally user was able to continuue & process the workitem successfully & status is completed too. It creates an entry in table SWP_SUSPEN With workflow Workitem ID & workitem id of the workitem under this workflow & error type as "0001" i.e:- Enqueue error callback to workflow) & status of the workflow as "1" ...i.e: - "In Process " & not in error.
I also analyzed that once the entry in the table SWP_SUSPEN is removed or gets deleted, the workflow continues from the point where it stucked.
So what i wanted to know is, what this entry in SWP_SUSPEN means by indicating "Error type" as 0001 & Status as "1" . & how this entry gets deleted, i thought there is some background JOB RSSWERRE that does this but when i checked i found RSSWERRE only checks for items in SWP_SUSPEN with workflow statuses as "02" i.e:- In error. where as my workflow has status "1" in SWP_SUSPEN under status field (as mentioned above)which means "In Process" I also found that this entry is getting deleted after sometime, so there must be some background job that is doing it, so i wanted to know what is that background Job if not RSSWERRE.
Regards,
Chetan.

Hi,
This is what i got from one of the Notes:
ou use parallel processing where you have a fork with 2 branches (1
Branch necessary for completion). In one branch is a dialog activity
step and in the other is a 'Wait for Event' step. While the dialog
step is being executed by a user the Wait for Event step receives its
event and continues along the branch and completes the fork (Remember
only 1 branch needed for completion). Once the end of fork is reached
the dialog work item should be set to status Logically Deleted but
this does not occur due to the lock/enqueue on the work item while the
user is executing it. Since a callback is essential for a workflow to
continue running, this callback is suspended (stored in the SWP_SUSPEN
table). These callbacks are started again via the RSWWERRE report. If
you have not scheduled report RSWWERRE then the work items will remain
in table SWP_SUSPEN and the work items will not receive their callback
and will therefor will not continue.
If there are examples of work items hanging then check table SWP_SUSPEN to
see if the callback work item ID is there. If it is then make sure you have
the RSWWERRE job running in order to redeliver it. If RSWWERRE is running
and the entry is not being delivered then please check for notes using the
search term "RSWWERRE" and "SWP_SUSPEN". If there is no entry in
SWP_SUSPEN, then check the workflow definition to see if the work item is
asynchronous i.e. needs a terminating event as in Example 1 above. Check
the event queue via transaction SWEQADM to see if the terminating event is
being buffered there. If it is then it should automatically be redelivered
so do a notes search in relation to the event queue.
Regards
Gautam
Edited by: gautam maini on Aug 3, 2011 4:16 PM

Best way to manage rules?

I have just maxed out the rules for iCloud (99 rules allowed). On the Mac you can have more complex rules so you can have one rule that says basically if I get an e-mail from (Lands End, L.L. Bean, Amazon, etc) file the e-mail into my "Stores" folder. However on iCloud rules you need one rule for each store. I prefer using iCloud for the rules so they are sorted before they get to my Mac. This way they are sorted if I check my mail from an iPad or another Mac or on the Web. However, I didn't know until this morning that iCloud has a limit of 99 rules. So now I need to decide what is the best way to adjust.
So my question here is how do you manage rules to sort e-mail?
Thanks,
Scott

Winston,
This is true if your main computer is always on and connected to the internet. However where I live currently we have frequent power outages and internet connectivity issues. Some of these problems require my to restart routers in order to fix the problem. However, if I am traveling away from home I am not able to do this. In a case like this if my rules are on my main Mac at home and I am checking e-mail from an iPad of Macbook Pro on the road no rules will run.
Thanks.
Anyone else have thoughts on this?

Regarding workflow to get manager rule 168

Similar Messages

Maybe you are looking for