|
Written by Kevin Wilson
|
|
Tuesday, 22 July 2008 |
This function module takes an IDoc number as input and displays the workflow logs associated with it. Modify as you see fit...
|
|
Read more...
|
|
|
Written by Kevin Wilson
|
|
Thursday, 30 August 2007 |
|
7 ways to generate events for business objects.... |
|
Read more...
|
|
|
Written by Kevin Wilson
|
|
Monday, 06 August 2007 |
- Transaction SWETYPV - Check "Enable Event Queue" for your business object event
- Use Transaction SWEAD – Event Queue Administration to view the queue and activate it. Schedule the job here as well
- Report to process events in the queue: RSWEQSRV
|
|
|
Written by Kevin Wilson
|
|
Tuesday, 10 July 2007 |
|
We used to be able to start a workflow using the transaction SWUG but that is no longer available. To do the procedure in the NetWeaver environment do the following: |
|
Read more...
|
|
|
Written by Anon.
|
|
Tuesday, 01 May 2007 |
Firstly: DON'T. OK, if you're in a development/QA system, there is a deletion report RSWWWIDE. NDon't use this in production. Use archiving object WORKITEM instead. RSWWWIDE does exactly what you tell it to without question and will happily delete WI's out of the middle of a log and create other inconsistencies if you don't know EXACTLY what you're doing. There's also the potential legal aspect: In these days of Sarbanes-Oxley and massive corporate scandals, finding such reports in the ABAP log will not make make any auditors happy.
|
|
|
Written by Anon.
|
|
Monday, 30 April 2007 |
This usually occurs if the set of 'possible agents' is very large - usually because the task has been classified as a 'General Task'. In general, if no 'responsible' agents can be found, the workitem is automatically sent to all 'possible' agents.
To solve this problem, reconsider whether using the 'General Task' classificiation is a good idea. Try to restrict the set of 'possible' agents to a sensible subset for all tasks. |
|
|
Written by Kevin Wilson
|
|
Monday, 30 April 2007 |
|
Event linkage is a transportable object, thus there is no way to simply 'switch off' a workflow. Simply switching off a Workflow may even have legal implications since Workflow provides an important audit function, and being able to disable it defeats that purpose. All is not lost however: If you have a workflow that requires this feature, you could include a start condition that always fails and only enable it when you want to disable the workflow. We developed a Z transaction that updates SWETYPV. Let me know if you are interested in this tool and I'll post it here too. |
|
|
Written by Anon.
|
|
Tuesday, 24 April 2007 |
|
As a user: The user who has the item in the inbox has to set up a substitute. The substitute can then process the other user's work items. You have a choice of two different substitute rulings: - Active substitute ruling (for example, for absence due to vacations): In this case, the items belonging to the absent person are automatically assigned to the substitutes inbox (in addition to his own work items).
- Passive substitution (for example, for absence due to illness): the substitute must explicitly assume the substitution and can only view the items of the absent person in this mode.
As an administrator: Transaction SWIA
Programatically: Function module SAP_WAPI_EXECUTE_WORKITEM
|
|
Last Updated ( Monday, 23 April 2007 )
|
|
|
Written by Anon.
|
|
Monday, 23 April 2007 |
|
Yes, apply note 864516 - Secondary methods for UWL |
|
|
Written by Anon.
|
|
Monday, 23 April 2007 |
Whilst the UWL is a powerful tool for collating alerts, work items, guided procedures and more from different systems, it has some limitations compared to the SAP Business Workplace (SBWP).
These are fully described in note 794439 "Universal Worklist support for SAP Business Workflow" |
|
|
Written by Anon.
|
|
Monday, 23 April 2007 |
The organization buffers must be refreshed. This occurs daily at midnight by default - and you can't change that time. Transaction SWU_OBUF lets you refresh the buffers immediately.
Also, check and make sure that the agents you have assigned are possible agents of the task. |
|
|
Written by Anon.
|
|
Thursday, 19 April 2007 |
|
Why should I not assign org units to steps in the workflow builder? |
|
Read more...
|
|
|
Written by Anon.
|
|
Thursday, 19 April 2007 |
This is unfortunately not possible as the very nature of asynchronous tasks contradicts the idea of 'advance in dialog', also known as synchronous dialog chains. The two main reasons for using asynch tasks are either that the termination can happen outside of WF, or to ensure that all database updates are complete. Both of these imply that there is an action happening outside of workflow (database updates can happen outside the user session after the transaction is completed). Since these happen outside the current dialog session, one would have to 'continue' another user's session in the current dialog, which is not possible.
How it works on a more technical level... |
|
Last Updated ( Thursday, 19 April 2007 )
|
|
Read more...
|
|
|
Written by Anon.
|
|
Thursday, 19 April 2007 |
|
Help! Why am I getting the error 'No Administrator found'? |
|
Last Updated ( Thursday, 19 April 2007 )
|
|
Read more...
|
|
|
Written by Anon.
|
|
Tuesday, 17 April 2007 |
How do I know I'm ready for this? Easy ... did you read the first 3 blogs and create the examples mentioned in blogs 2 and 3? If not, here are the links... 1. Why use ABAP OO with Workflow?
2. Getting started with ABAP OO for Workflow ... using the IF_WORKFLOW interface
3. Using ABAP OO with Workflow Tasks If you want to try the exercise in this blog in your own system, you will need an ABAP Class with the IF_WORKFLOW interface, and a system/client (SAPNetWeaver 6.20 minimum) with the workflow environment activated. You also need to have created the "Display Plant" workflow task mentioned in blog number 3. Note: As mentioned in the last blog, this blog won't teach you ABAP OO. It won't teach you workflow either, but it should give you enough to get going even if you've never touched workflow before. Read the entire blog at SDN by clicking <here> |
|
Last Updated ( Tuesday, 01 May 2007 )
|
|
