Transaction/Report to process background work items which r in READY state

HI,
Can somebody kindly tell me the transaction/report program to process background work items which are in ready state. SM59 configuration was missing and hence, workflows failed to execute after being started successfully. Now, I want to comeplete these operations.
Thanks a lot,
Max

Hi Max,
Did you check transaction SWPC? If the workflows are in there you can start them through in a proper way.
Regards,
Martin

Similar Messages

Execute Background Work Item using Deadline Monitoring

Hi All,
I want to execute a Background Task using Requested Start. The status of Work Item is Waiting. But it is not executing after Deadline reaches and in graphic log it displays no agent. As per my knowledge Background work item is executed by Workflow system itself.

Hi Bikash
check if the deadline monitoring job is running or not. SM37-> Check for job SWWDHEX
if not then schedule it from SWU3.
This is the job which actually picks up the waiting items (waiting for deadlines).
regards,
Modak

Don't want Background Work Item as run as a tRFC

I have a purchase requisition approval workflow. My problem is that the purchase requisition is showing WF-BATCH as the user-id that did the release of the PR.
My workflow has a sync dialog user-decision step for the approve or reject. If the user approves the PR then it calls a background synchronous release step. I have the "Advance with dialog" check box on the background task.
When I look at the workflow log the background task starts with the dialog user-id, however it then creates a tRFC entry so the work item actually finishes under the WF-BATCH user-id.
What setting(s) do I have to change so that the background work item doesn't execute as a tRFC?
Thanks,
Jeff

Hi Jeff,
I presume you are using the custom workflow and not the std one.
If so, in your workflow, is the user who is approving the PR is supposed to release he PR or it is different authority who will release PR ?
If it the same authority who acts on user decision and who should release the PR, I could not get the purpose of not using the step Overall Release similar to std PR release workflow as against using the decision and background release step.
Because, in this step of std workflow, user will have to act and release the PR and then you will have his name under workflow log.
As Glauco indicated, for background steps, you will always have name of WF-BATCH.
Regards,
Akshay Bhagwat

Can I just add a state to bug work item and not set the state to the workflow

Hi,
Based on my team, we need to add a state/states to the bug work item, just add the bug state, and let it displayed in the state dropdown list. We don't want to add the state to the workflow. Can I do that?
Thanks,
shmily

Hi shmily,
If you add a state for the bug in your work item definition file, you have to define the transition for the state. If not, when you change the state, the backlog page or task board will not display the work item correctly.
Please check the links below for more information about workflow design guidelines and customization for work item type:
http://msdn.microsoft.com/en-us/library/ms194981.aspx
http://msdn.microsoft.com/en-us/library/hh409273.aspx
Best regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

SWI1 work items execute at a time...

Hello workflow gurus,
I need help in the workflow regarding the mass execution of different work items hanging in the SWI1 queue.
We are using the workflow in our project. & we have lots of work items are hanging in the SWI1.Some of them are related to wait step, which means they are waiting for deadline monitoring & some of them related to executing a method in the background.
Now my first question is how can we execute all the waiting work items at a time? Because there lot of them are there. & my second question is how can I execute the background step work items at a time, because this does not involve any waiting period. For ex: changing the sales order.
Pls help.
Thanks,
Pandu

Agree it is not a queue, let me explain you what is happening, we have a single step task which will just execute the method of the business object. It is single step. So when we raise the event in the code this work item gets created & the method will be executed.
But if it is one time, then it's perfectly ok. But the code will raise the event lot of times. So lot of background work items are getting creating in SWI1. The status of these work items are 'READY', & I see lot of entries in SM58 too.
SAP help says: The background work item status 'READY' means
Interim status, in which a background work item only remains temporarily.
As soon as a background work item can be processed, the system automatically calls the corresponding object method. The background work item immediately changes to status in process.
"The object method is called using a tRFC call. If a background work item remains in status ready for a long time, you should check whether the tRFC calls are processed without errors.".
That means with 'READY' status, the work item has already executed the method using tRFC call & it failed in SM58? or
it is waiting to execute to that method but waiting fro any resource? or something else?
If it is just like a single method why it is taking time & hanging in SWI1. Pls clarify.
Also I want to ask one more question, to execute/process this background work item which std program/job is responsible? For ex: SWWCOND. So that we can schedule more frequently.
Pls help.
Thanks,
Pandu

Forwarding 'Wait Step'work items using SWIA

Hi,
I need to forward work items of one user A to another user B urgently, using SWIA.
The work items are in executed state. This is after a fork step in the workflow, where the executed work item is one branch of the fork.
As these items are executed, we will have to forward the work items that are in ready state.
The work item for the other branch of the fork is in ready state. However this is a wait step, and hence I am not able to forward this item.
Kindly advise as to how should I forward these items.
Best Regards,
Smruthi.

Hi Smruthi,
Dont confuse with the wait for events and dialog work item. There is no direct link between the wait for events and the work item.
Only dialog work items needs the user action and dialog work item's only can be forwarded to other user's.
For this, the work item should have the status of 'Ready'. If the work item has the status 'In process' that means, the user opened the work item and still he didnt take ant action on it.
In this case, using SWIA you can manually change the status as 'Ready' and then you can forward the work item to the other user's.
To forward the work item use the function module 'SAP_WAPI_FORWARD_WORKITEM' or use the SWIA transaction.
Thanks,
Viji.

Generate a Work Item from a report

Hi,
I'm writing a report that needs a Work Item to be generated. It just has to be kinda notification that goes to agent's inbox.
Could you please let me know the FM that can be used to do this?
Thanks..

Hi,
Try using the function module SWW_WI_START..
Thanks,
Naren

Need to call sap transaction when the work item got rejected.

Hi all,
I need to call the ME22n transaction once i reject the Work item. Once i press the rejection button on the work item it should direct to the sap transaction. how can i make this functionality in the decision task. Do i need to implement an ext for this.
Thanks.
Neslin.

You simply create a task for executing the SAP transaction (business object TSTC)
you use this task as a dialog step at the rejected outcome of the user decision with the same agent as the user decision and in the details of the workflow step you tick the advance with dialog box.
And... you're done.
Kind regards, Rob Dielemans
Edit: Instead of using BO TSTC it would be better to check the BO normally related to Me22n and see if a dialog maintain method exists
Edited by: Rob Dielemans on Jul 16, 2009 9:55 AM

IDoc - Work item processing documentation

Is there some basic documentation available (i.e. *.ppt or *.doc) on processing IDoc work items that I can make available to a customer as procedures for IDoc error resolution?

This question is down as answered? Can you past the link please.

How to Edit work item in Workflow

Hi all,
I have a requirement like this .....
I have to process the Error Idoc to the respective Sap Business workplace based on the Position assgigned.
Now my question is...I am able to send the IDOC to the Business workplace as work item. But the USER wants to Edit the Idoc and process it further...Please guide me how to approch it.
Thanks in advance
Chakri

Hi,
I am after processing the Idoc to Work item...
Double click on the work item which in turn takes to the "Display Record"...in the screen itself..Menu bar
we have EDIT --> Foreground Processing   ---> Visible
                             Foreground from Error    ---> Visible
                             Background Processing ---> Visible
                             Set delete Indicator          ---> Visible
                             End process                                    ---> Disable
                             Continue Despite syntax error        ---> Disable(Want this to show in Visible )
Please help me on this case.
Thanks in advance
Chakri

Terminating Event to Event Queue due to Work Item Lock

I have a dialog workflow task based on an asynchronous method defined with a terminating event. When the user executes the work item, the method generates the terminating event (via a V2 change document) but the work item is enqueued (locked) by the same user (locked when they execute the work item from SBWP) and therefore the terminating event goes into error and is placed in the event queue. The background job which processes the event queue does not redeliver the event so it stays in the event queue and the work item fails to complete. Other than dequeing the work item lock myself with a function call how do I get around this catch 22?

Hello Martin,
Actually, the locking happens whether I have the task as asynchronous or synchronous. The problem is the timing. If the user does not release the lock (by backing out of the dialog which is executed) prior to the terminating event attempting to enqueue and complete the work item then the event goes into error and is inserted into the event queue (and lingers there indefinitely, almost). Another issue with the asynchronous approach is that even if the user backs out of the dialog before the event actually attempts to complete the work item they will still see the work item in the inbox unless they click the refresh button when they get back to the inbox.
I have changed the task to synchronous but here is my scenario and another question.
The process being workflowed is the approval of service entrysheets (similar to an invoice if you are not familiar with External Services). In our process, there are a large number of documents being created and requiring approval by particular approvers. It is a normal scenario for an approver to have, lets say 25 documents in his inbox awaiting approval. It was not practical for him to have to navigate back and forth between his inbox and the approval task screen. Therefore, I give the users the option of (when executing a work item) having all the documents in his in-box (for this particular task) be presented in an approval list screen. They can then do a mass approval of the 25 documents with 1 click and 1 navigation. This list screen is also available to be executed outside workflow via a tcode. So, when the user executes the mass approval (either from the inbox or outside workflow) the work items are terminated via the terminating event assigned to the approval task.
A couple of issues remaining:
1) Given my example of 25 work items (user executes 1 work item from in-box
and I displayed all 25) being approved, when the user returns to the in-box, the 24
items remain in his inbox until he clicks the refresh button since these were not actually "executed" from the workflow engines point of view. However, these were terminated successfully because they were not "locked".
Question: Is there a way (user exit?) to trigger the inbox refresh automatically.
2) Now, the issue with the actual work item which the user executes from the inbox. As I mentioned, the work item is locked as soon as the user executes it and is not released until they back out of the dialog or logoff. So, here is what happens: If the terminating event is sent before the lock is released the event is sent to the event queue. If they then back out back to the in-box, its OK since I put some code in the SWO1 object type program (rememeber, its now synchronous) which will determine if they did the approval/rejection and the work item will complete and the event in the event queue will be deleted the next time the Event Queue Background job runs (it deletes any events for work items already in COMPLETED status). However, lets say they simply log off rather than backing up to the in-box or they don't do anything and are eventually logged off by timeout. In this case the code in the object type program to determine if the approval/rejection was done does not get executed (control does not return to the object type program) and the work item remains in "STARTED" status and remains in the users inbox and the event is in the event queue. So, now we have a work item that should be completed still sitting in the users in-box and the terminating event in the event queue. So the next time the user goes to their inbox the work item is still there. The interesting thing is that though this may be confusing to the user, if they then attempt to execute the work item, they will get a message: "Work item currently being completed by event" (Message SWF_RUN 644) and the event sitting in the event queue gets redelivered and completes the work item. To alleviate this problem I was thinking of adding a call to SAP_WAPI_WORKITEM_COMPLETE in the approval list screen after they do the approval but I'm guessing it wont work since it probably will try to enqueue the work item and it will still be locked.
Hopefully you haven't nodded off reading this rambling note...
Thank you,
Bob

Mass approval functionality for SRM work items

Hi,
We want to implement mass approval functionality for SRM workflow, so that any user is able to approve/reject multiple requests at one go through UWL.
Please guide if it is possible to implement this functinality for task id TS40007952.
Regards,
Avantika

Hi Avantika,
The mass approval functionality can be implemented for simple workflow items which have decisions to complete the work item. (User Decision Type)
In SAP Business Workflow, user can define a task as a decision task by assigning DECISION as the underlying business object type. The task definition allows user to create two or more decision options to complete the task.
The idea is to simply create a custom view/subview for the UWL item and configure it according to your needs.
Have a look at this blog:
Mass/Batch Processing of Work items in UWL
and also check the documentation:
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/4e/72112bc9ea484196f2a5fdc68f5f5f/frameset.htm
Let me know if you have any questions.
Thanks,
Shanti

Enqueue for work item n deleted by called application

Hi All
We upgraded from 4.6C till ECC6.0 and from then we receive occasionaly messages in SM21: Enqueue for work item 000001198539 deleted by called application.
This results in problems when 2 dialog task are executes after each other. Somethimes the second taks is not executed. I find in the log the following errors:
- Temporary error in result processing of work item 000001199739
- Error when loading component: Work item 000001198388 locked
- Work item 000001198388 locked by user WF-BATCH (enqueue error)
This is the head of the WF that's locked..
We implemented all relevant OSS notes regarding the message, but still we receive those messages (notes 1040693 - 1050793 etc) We are on support package SAPKB70012.
I have checked the code in our custom WF and in some background task we use a DEQUEUE_ALL. Can this be the problem? The WF worked perfectly in 4.6C.
CALL FUNCTION 'ENQUEUE_EFBKPF'
 EXPORTING
* MODE_BKPF = 'E'
* MANDT = SY-MANDT
 bukrs = i_bukrs
 belnr = i_belnr
 gjahr = i_gjahr
* X_BUKRS = ' '
* X_BELNR = ' '
* X_GJAHR = ' '
* _SCOPE = '2'
 _wait = 'X'
* _COLLECT = ' '
 EXCEPTIONS
 foreign_lock = 1
 system_failure = 2
 OTHERS = 3
IF sy-subrc <> 0.
 RAISE locked.
ENDIF.
UPDATE vbsegk SET zlspr = i_zlspr
 WHERE ausbk = i_bukrs
 AND belnr = i_belnr
 AND gjahr = i_gjahr.
* and ( zlspr = 'A' or zlspr = 'Y' ) .
COMMIT WORK AND WAIT.
CALL FUNCTION 'DEQUEUE_ALL'
 EXPORTING
 _synchron = 'X'.
Any help appriciated
Kristof

The entries we have solved by removing the DEQUEUE_ALL function in a method.
Still we receive somethimes errors in the workflow log
Temporary error in result processing of work item <n>
Message no. SWP030
Error when loading component: Work item <n> locked
Message no. SWP034
Work item <n> locked by user WF-BATCH (enqueue error)
Message no. WL605

Need to remove work item.

Hi Experts,
I am getting a work item in SBWP Transaction.Now If I check the workflow for this ITem Through Transaction PFTC.
I got in Rules there in responsibility tabs have no position which consists our user.
But still the Our user is getting that message.
And that message is for diaproval.
I want to remove or hide that message. How it can be done?
Thanks,
Jassi

You might be getting those workflow messages, since someone might have kept you as their substitution. Hence the work items which should actually appear in their inboxes gets forwarded to your mailbox since you are the substitute for them.
Regards,
Rinkesh Doshi

RSWUWFML2 - Ready status of work item??

Hi - Here is the story...
R/3 Enterprise, SAP_BASIS = 620, SAPKB62038
SAP_ABA = 620, SAPKA62038
My workflow sends out a user-decision step to an agent. This work item is in "In-Process" status. My requirement made me decide to schedule RSWUWFML2 & send a notification mail to the internet address of this agent.
Problem : When I debugged RSWUWFML2, found it selects work items only with status = "READY". Hence my work items of the above workflow never get picked up. Has any one faced this? And what was the solution you adopted or you recommend here?
Thanks! Shireesh M.
Message was edited by: Shireesh M
Shireesh Mitragotri

Hi
Sorry - but it's working as designed
The reason for this is, whenever a workitem is in status in-process the agent has opened the workitem, so he should know that he has received it Thats why the report won't send a notification to this agent.
If you won't accept this limitation you need to create your own copy of the report.
Regards
Morten Nielsen

Transaction/Report to process background work items which r in READY state

Similar Messages

Maybe you are looking for