Workflow decision

In workflow decision step, in the details tab under 'adhoc specification determination' the field 'interfaces compatible with' is taking TS20000004 - pm order created and hence when the test taskflow option is used system by default is taking to the notification order. How to change this default

Please help

Similar Messages

GRC 10.0 CUP - Function Approval Workflow - Decision pending?

Hi, i am customizing the Function Approval Workflow (SAP_GRAC_FUNC_APPR).
I have one stage with only one agent authorization. The agent approved the request but in Search Request:
Instance Status: Running
Instance Approval Status: Decision Pending
Audit Log:
+ Request XXXX submitted..
+ Request is pending for approval at path GRAC_DEFAULT_PATH stage GRAC_DEFAULT_STAGE
Approve ID: zzzz
+Approved by ZZZZ at path GRAC_DEFAULT_PATH stage GRAC_DEFAULT_STAGE
I don´t see the function in GRC. I´m in SP07
Regards
Ignacio

Hi, my workflow Function Approval (default) have a wait event and i can´t delete this step succesfully.
Here are more images about the workflow configuration of Function Approval.
http://es.zimagez.com/zimage/wf10.php
http://es.zimagez.com/zimage/wf20.php
http://es.zimagez.com/zimage/wf30.php
http://es.zimagez.com/zimage/wf40.php
http://es.zimagez.com/zimage/wf5.php
http://es.zimagez.com/zimage/wf6.php
http://es.zimagez.com/zimage/wf7.php
http://es.zimagez.com/zimage/wf8.php
Thanks,
Regards,
Ignacio Barrionuevo.

Need Help: Workflow Decision Task not visible in NWBC for customer Task

Hello All,
I am new to NWBC configuration , need ur expert knowledge for the below issue. I have checked the treat . Approve/Reject button for SRM Approval for RFx response ,but not able to get the exact steps for the configurations in NWBC.
Requirement.
     We are working on SLM/SRM module, where we have requirement to create a custom workflow with custom Task for which we have executed below actions.
Created the Custom Workflow.
Created the custom Task with custom ZCLASS and ZEVET.
Created   Event linkages in SWE2.
After doing this we are getting the workitem in the NWBC, currently we don’t have the Portal system in place, so we are using the NWBC for all our testing.
What is the issue?
     When we select the workitem in the NWBC (UML) inbox , the Decision Task ie “Approve” or “Reject” button are not visible , where as for SAP standard Task buttons are visible.
What help we need?
When we cross check the SCN/IBM portal, found that we need to do the XML file configurations. Can you any one kindly let us know the steps we need to follow to achieve our functionality.
Thanks a lot in advance.
Thanks and Regards
Channa

You need to share the details of what Inbox you are using, configuration steps depend on it. If you aren't using portal, you aren't using UWL and there is no UML inbox. You need to get your facts straight. Most likely you are using the Business Workflow Inbox (SWF_WORKPLACE) or the Lean Inbox (IBO_WDA_INBOX). Both are based on Web Dynpro ABAP and POWL but the configuration is different. Regardless, you posted this in the wrong space. Correct space is either SAP NetWeaver Business Client or Web Dynpro ABAP.

Why cant I bebug BO Method from Workflow decision step

I have been trying for a while to find a solution. I have activated BO Debugging. I have set BO method as advance with dialog. all my efforts in vein. I could debug directly from SW01 but not from SBWP.
Is there any trick to debug a BO method. I have a task to execute a custom BO method "approve" after user decides to approve workitem. I am sure this method is getting executed but but not stopping there because I have put a error message which is being displayed.
your earliest response is much appreciated.
Regards
Kasi

Murthy,
You have little wrong perception about your workflow logic (As I understood from your description, may be I have not understood it proper).
You said that you put the break point on your BO method.
well user decision is always based on BO DECISION method PROCESS (unless you have created your own screen), Now you might have different buttons on your user decision (say approve/reject/cancel and keep etc), so if you wish to debug this (BO decision method Process) you can,
but the task which got executed once you click on this buttons might be bacground task (based on your BO's method) and you can not debug the background task. Ofcourse there are several indirect ways to debug this, pls search forum for that.
Hope it will help.
Cheers
Jai

Maint. Order as Attachment in workflow decision step!!!!

Hi All,
I am making a workflow in which i want to attach the Maintenance Order in the Decision Step , is it possible or not.
How can i do attachment in Send Mail Step is there any provision.
Basically my requirement is like:-
When the User create the Maintenance Order a workflow should trigger which will go the SAP Inbox of the recipient now he has to see the maint. Order created and should approve if it can be Released or not .
When he does the approval the application should go for the another approval and when he approves the application is sent back to the workflow initiator.
Please suggest me what is the best way to do this scenerio. As i m very new to workflow so have only basic knowledge
Please help me out!!!!!
Thanks

Hi Rachit,
Have a look at std WF like WS20000014, WS20000021 etc..
It will give idea about maintenace order processing
Regarding your question about attaching objet to User decision, yes, its possible. Just Bind the Maintenance Order Object related container element to AdhocObjects elemnet of user decision.
Your overall process can be there will be 2 user decision steps.
Once these two steps approve, then you can use a third step with background task which will actually release the maintenace order. e.g. For this step you can use BAPI.
Hope this helps.
Regds,
Akshay

Workflow decision steps

Hi,
I have a decision step. When the user executes it a workflow log and a create attachment buttons appear on the top. Is there a way to suppress these buttons?
Thanks,
Scott

Hi Janos,
Thank You for your quick response.
I am able to see the link attachment in the Objects and Attachments section but when i click it on the link the invoice image it should get open in SAP Document Viewer it's not opening just doing nothing .
"ArchiveLink Image in workflow screen doesn't work , the image does not open. No error message at all ,just doing nothing when clicking on that link"
But when logged into SAP Portal the same link is opening and able to see the image in SAP document viewer. But from SAP GUI it's not working.

Workflow Decision suppress "Objects and attachments "

Hi all,
Is there a way to suppress the "Objects and attachments " message or change the text that reads "No attachments or objects"?
Thanks in advance,
Scott

hi,
first post workflow questions in the SAP Business Workflow
Executing transactions is done by first finding the business object related to the transaction and then see if a method exists for changin in dialog
for instance, BUS1001 methods display, edit, delete
executing transactions who don't belong to a business object from workflow can be done with a task which uses method execute of business object TRDIR, you have to pass the progrm name .
kind regards, Rob dielemans

How can i execute a workflow using a bapi/wapi??

Hi All,
How can i execute a workflow using a bapi/wapi??
pls advice
thanks

Hi Hrus,
it's not as simple as a single BAPI to approve a workflow.
Workflow comes with a Workflow API (WAPI) that you can use to programmatically interact with the workflow system. The WAPI is implemented as a group of RFC-enabled function modules that are prefixed with "SAP_WAPI_".
Approving a workflow is simply taking a decision path for a workflow item. It is logically no different to rejecting the same workflow item or any other workflow decision.
As part of NetWeaver workflow is tightly coupled to the WAS platform you are running on so you may need to perform WAPI operations slightly differently on older releases.
Some of the WAPI calls you might need to use include: -
SAP_WAPI_GET_HEADER to get the workitem header
SAP_WAPI_READ_CONTAINER to get the workitem container
SAP_WAPI_GET_OBJECTS to get the attached objects
SAP_WAPI_DECISION_READ to get a list of possible decisions
SAP_WAPI_SET_WORKITEM_STATUS to set the workitem status
SAP_WAPI_WRITE_CONTAINER to write to the workitem container
SAP_WAPI_EXECUTE_WORKITEM to execute the workitem
I usually do what you are trying to do by adding the decision to the workflow container and then executing the workflow.
Be warned, you can really stuff things up if you get this wrong! Make sure you know what you are doing.
Quoting from Practical Workflow for SAP by Alan Rickayzen, et al from SAP Press...
Writing directly to the workflow container is dangerous because it can compromise the integrity of the process.
...be careful that you do not waste time duplicating existing ad hoc features of SAP's Workflow Engine.
For example you can use events (combined with wait steps), instead of container modifications to force the workflow to restart.
Cheers
Graham Robbo

SAP workflow not published / not reaching default outbound handler

Hi,
At Velocity event (october) we had a SAP ERP workflow configured for publishing to SharePoint; after triggering workflow instances, an XML payload document was successfully published to SharePoint.
Now, in the same environment; without changes on Duet Enterprise config level, publishing of task changes of that same workflow no longer publishes into SharePoint.
We executed the report jobs OSP_DELTA and OSP_FULL to make sure that the sync from SAP to SharePoint would be done / task changes are notified. The SAP workflows are delivered into the SAP inbox; but not published to SharePoint.
We added a breakpoint (internal + external) in the default outbound handler S_OSP_WF_PAT_DEFAULT_CH_OB; it is not invoked when we reach the workflow decision step that is published.
We inspected the SCL Logs, but didn't find any relevant log entries.
Any clue what can be wrong here; where to start with the problem analysis?
Best regards, William.

Hi Holger,
The error 'Users not maintained...' appears to be caused due lack of SAP permissions of the SAP account that is executing the report S_OSP_WF_ITEM_SELECTION; with another account we succesfully pass the 'GetNotifications' calls within that report; and actually now do get into the default outbound handler.
But still no task document published into SharePoint; the default outboundhandler faults on Send Action item; error details:
ERROR_CONTEXT>
<ERROR_INFO>ICF Error when sending the request: HTTPIO_ERROR_SEND_STATE-Fehlermeldung beim Senden der Daten.</ERROR_INFO>
- <CONSUMER_INFO>
<CONSUMER_PROXY>CO_OSPWACTION_ITEM_VI_DOCUMENT</CONSUMER_PROXY>
<LOGICAL_PORT>CO_OSPWACTION_ITEM_VI_DOCUMENT</LOGICAL_PORT>
<OPERATION_NAME>maintainActionItem</OPERATION_NAME>
<OPERATION_NAMESPACE>urn:ActionItemWsd/ActionItemVi/document</OPERATION_NAMESPACE>
<PROCESSING_UNIT>Sector 1: WS-Consumer</PROCESSING_UNIT>
<PROCESSING_MODE>Synchronous</PROCESSING_MODE>
<COMMUNICATION_TYPE>Remote</COMMUNICATION_TYPE>
<WORK_PROCESS_NUMBER>1</WORK_PROCESS_NUMBER>
<WORK_PROCESS_PID>25034814</WORK_PROCESS_PID>
<TERMINAL_NAME>C0269450</TERMINAL_NAME>
</CONSUMER_INFO>
- <TRANSPORT_INFO>
<PROTOCOL>HTTP/1.1</PROTOCOL>
<AUTHENTICATION_METHOD>BasicAuth</AUTHENTICATION_METHOD>
</TRANSPORT_INFO>
</ERROR_CONTEXT>
We want to check the settings of Consumer Proxy for Workflow (page 76 in deployment guide); however we don't see 'Connection Settings' entry in the SCL server.
--> 4. Select Connection Settings > SCL to Consumer > Configure Service Endpoint.
Regards, William.

Call a Webdynpro ABAP from a workflow step

Hi,
I have to develop a workflow where we have a step for decision, this decision have to open a webdynpro and retrieve info to workflow again.
This is possible ?
Thank you in advance.
Miguel Silva

Hi Miguel Silva,
This is possible, the T code SWFVISU is used to integrate the Workflow decision task with Webdynpro.
In Webdynpro you will receive the WorkitemID as parameter. Then based on Workitem id you need to fetch the data.
Use the below function modules to fetch the data in webdynpro based on workitem ID.
1) 'SAP_WAPI_READ_CONTAINER'
2) 'SAP_WAPI_GET_OBJECTS'
Regards,
Chandra,

Adding Validator step in MDG Customer workflow

Hello All,
I need to add validator step in MDG - Customer workflow - WS54300003 and process is, requestor will create CR and it should go to Validator. Once he approves then it should go to final approval team. Currently it is going to final approval stage at first step itself.
I added that additional step(Validator) to workflow templete(WS54300003) under processing modeling->workfloe->other MDG workflow->Define Change Request Step Numbers. Also, assigned process at ...-->Assign processor to Change Request Step Number (Simple Workflow).
Seems i am still missing some thing. Could you please guide me what else need to be done? we are on MDG 6.1

step numbers are hard-coded in this workflow template (WS54300003). if you open any task container, you will see the value of the step in the container of that task.
any way, you should not modify workflow WS54300003 as that is considered modification to standard objects. you can copy it to a custom workflow template and then add any new step as you like. you can assign whatever number you like to any step as long as the numbers in the workflow template are consistent with the numbers assigned in the MDGIMG configuration node.
A recommended solution is to use the rule-based workflow template. your MDG process will be much more dynamic and a lot easier to modify/enhance going forward.
this document can help you understand how you can use the rule-based workflow template: How to Fill MDG Rule-Based Workflow Decision Tables

Synchronise Workflow Inbox cross systems

Hello,
The SAP environment is growing and more systems are added to the SAP environment. Some of the Business processes goes over different systems so also the Workflow processes. In each system it is possible that a workflow item is created for a certain user. Is it possible to forward the decision task to the inbox on a central ERP system from where the user executes the workflow item?
Or are there better solutions to handle the workflow decisions tasks from the different SAP systems?
Kind regards,
Richard Meijn

Hi Richard,
It sounds as though what you really need is to implement the Universal Worklist (UWL). Certainly, you could make workflow in System 1 create a decision task for the users in System 2, but that seems like making the tail wag the puppy.
The UWL is designed to accomplish just this scenario - consolidate the many tasks into a unified inbox.
Regards,
Sue

Triggering Workflow

Hi experts,
I have a pdf form in portal UWL inbox. When i open that form there is a approve button in it. When the user clicks the approve button i need to trigger a workflow. How should i do this. Also when approve button is clicked by user1 it should go to Portal UWL inbox of user2 for his approval. How should i handle this in workflow.

Hi,
You need to trigger a custom event that would act as start event to the workflow when a button is clicked.
Check the code that you need to write to trigger Workflow based on event in the below link.
Re: Workflow Decision Task
To get the Workitem to portal you need to configure workitem task in SWFVISU transaction with the application.
Good luck
Narin

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

UWL refresh problem for ABAP BOR custom attributes

Hi all,
we are facing an issue with an UWL iView. We wanted to display custom attributes from an ABAP Business Object (ABAP_BOR).
The feature is working but when an end-user receives a new task in his UWL view, he needs to click on the refresh button in order to have all the custom attributes correctly displayed.
We have only the problem with custom attributes, for the columns containing standard workflow decision task attributes, the data are displayed directly without the need to push the refresh button.
We are on EP 7 SPS11 and the back-end is an ECC6 version.
We have followed the methodology described in the How to configure and customize the Universal Worklist pdf document:
ABAP BOR
<CustomAttributeSource id="ABAP_BOR"
objectIdHolder="externalObjectId"
objectType="FORMABSENC"
cacheValidity="final">
<Attribute name="COSTCENTER" type="string"
displayName="Cost Center"></Attribute>
<Attribute name="FIRSTDAYOFABSENCE" type="date"
displayName="First day of absence"></Attribute>
<Attribute name="LASTDAYOFABSENCE" type="date"
displayName="Last day of absence"></Attribute>
</CustomAttributeSource>
Do you have an idea where this problem come from and how it could be solved?
Thanks in advance and regards,
Sébastien BODSON

Hi Chintan,
This parameter has no impact on the problem we face. I found an exact description of our problem on SAP Help portal, in the UWL pages:
CustomAttributes, CustomAttributeSource and Attribute
Extract from SAP Help portal:
Every item type can have custom attributes defined, which can be filled from Business Object or Provider Data Containers like the Business Workflow Container or the Alert Container. These attribute sources are defined within the CustomAttributeSourcetag, which contains information on which attribute connector brings the custom attributes, how to identify these custom attributes in the provider system and how long the cache is valid.
Note that once an item arrives, these custom attributes are retrieved in additional calls to the backend. For performance reasons, in order to minimize responses times to the end user, this may happen while the item is displayed to the end user - causing such attributes to be empty initially and only to appear in subsequent requests.
The display names of the attributes for column headers and labels are defined in the display attributes of the default view of the item type.
Does anyone know a workaround in order to have directly the complete information displayed?
Sébastien BODSON

Workflow decision

Similar Messages

Maybe you are looking for