Invoice Workflow : Dialog work item created

Hi,
I am not fully aware of workflow but can manage to check the logs and status.
My question is: My Invoice workflow status is 'READY' but i dont know how to find to whom the work item it currently held.
When i check the log it says:
WF-BATCH Dialog work item created
How can i check, which approver currently held work item so that i can chase them to approve the item.
There are no agents assigned to the workflow and it is General Task.
I would apprecaite if you could share me some information about this.
Thanks,
Macs.

Hi,
About Invoice Workflow :
WS10400016 Without approval,
WS10400017 One-step approval,
WS10400018 Two-step approval,
WS10400021 Administrator approval
The relevant approval workflow is started, depending on completion status, invoice category (credit memo or invoice), creator role, and total value of the invoice.
You should have maintained approver in your org structure (PPOMA_BBP)
Please have a look at :
http://help.sap.com/saphelp_srm50/helpdata/en/58/c14e3c59bfe747e10000000a11402f/frameset.htm
Kind regards,
Yann

Similar Messages

Binding from workflow to work item aborted

Hi,
In my workflow the first two steps are multi condition.
after my second condition i have created activity   step   - Task   and binding the bapi attribute value.
i checked binding no error.
I am getting error in this part.
The error is
Workflow 'TEST' step number 1039: work item could not be created
Source (expression '&PurchaseRequisition.Zvalue&') of binding assignment is not available
Error in the evaluation of expression '&PurchaseRequisition<???>.Zvalue&' for item '20'
Step 15 of WS23000111: Binding from workflow to work item aborted
Error when determining attribute 'Zvalue' of object instance '[BO.BUS2105.001039]'
Step 15 of WS23000111: Binding from workflow to work item aborted
Message no. WFEA031
Diagnosis
Serious errors have occurred in the binding from workflow to work item in step 15 of multistep task WS23000111. As a consequence, workflow 1039 has been forced into error status.
Procedure
"Change Workflow Container" then "Restart After Error" may suffice. It is probable, however, that the binding definition in WS23000111, step 15will have to be changed.
pl help me to proceed further.
Thnks in advance.
sharma

Hi,
Seems that your custom BOR is not delegated to the supertype, please do the same in SWO6 and
also check the binding from event to workflow.
Thanks and Regards,
Swaminathan

Workflow - passing work item automatically from one inbox to the next one

Hi,
We have a pretty customized work flow and SAP is configured to start the workflow after creation of PO. For some POs created by a user, we want the POs / work item to be sent automatically / by background job from that user's inbox to his /her manager's inbox for approval without manually executing the work item.
I looked at the FM SWU_PROCESS_MANUEL_DECISION, but could be called only by dialog. I checked the transaction SWIA, but need manual input.
We are in 4.6b, can anyone tell me how to do the same?
BTW, I tried to create a custom FM based on above, but lots of issues on that as well.
If I can change the workflow, all I want is, check the initiator and PO types then based on that either forward directly to next approver or just leave it in the inbox of the initiator so that the initiator can approve manually after verifying the PO.
Regards,
Sundar.

Moderator note: As per comments, IA's answer was accepted as correct, thus marked accordingly.
Please note that even if you found the answer before someone posted the same, it is still a good idea to mark an answer as correct:
Firstly they did make the effort to help you, and - more importantly - it shows someone else reading this thread later on what the correct answer is.

Workflow error " Work item could not be found"

Hi Experts,
I used transaction SWI2_DIAG to diagnose the error and tried to restart the workitem manually .The changes were made to Org chart and now everything is fine but I am still getting error message:
Work item could not be found
Workflow 'Post with Clearing Workflow' step number 4: work item could not be created
Agent determination for step '0000000004' failed
Workflow WS93000005 no. 000004806372 activity 0000000004 role 'AC00000168': No agent found
Resolution of rule AC00000168 for task TS93000019: no agent found
Can someone explain what this error message mean and why i cant restart the workitem manually?
Thanks.

This is my message from Production:
Resolution of rule AC00000168 for task TS93000019: no agent found
Workflow WS93000005 no. 000004806372 activity 0000000004 role 'AC00000168': No agent found
Agent determination for step '0000000004' failed
Workflow 'Post with Clearing Workflow' step number 4: _work item could not be created_
This is my message from development.. I recreted the scenario and getting different message.
Workflow 'Journal Entry Approval- Approval WF' step number 36: work item could not be created
Agent determination for step '0000000036' failed
Workflow WS93000001 no. 000000986124 activity 0000000036 role 'AC93000003': No agent found
Resolution of rule AC93000003 for task TS00007914: _no agent found_
Edited by: Sergey on Nov 2, 2010 5:05 PM

Delete credit memo work item created in VA01 when the user change value

Hi,
In T.code VA01 Credit memo request is creating, this document will automatically create work item. Based on Net value in credit memo request, the work item should go for 5 levels of approval. After 1st person is approved, the workflow initiator realized that the net value in created Credit Memo request is wrong; he is going to VA02 and correcting the net value. Again we have to create new work item for this and delete the already created work item. Client has clearly mentioned when ever there is change in 5 critical fields in VA02 then only create fresh work item otherwise no need to create SECOND TIME work item. Net value is one of the critical field in the list.
How to track already created credit memo request and how to delete the previously created work item. What is the feasibility of this requirement and how to handle this situation?
Regards
Vijay

Hi,
Just put a Fork and put 1 out of 2 outcomes and in the first alternative, you put your witem that goes to user B. In the 2nd alternative, put a Wait for event "CHANGED". And after this, put a process control step with "Set workitems to Obsolete" or "Cancel workflow" etc., depending on your requirement.
Pl note that this will only take out old witems, but you need to send a new witem for which you need to trigger another instance of the workflow as well. pl put CHANGED event also as one of the triggering events and use condition editor to restrict the fields that triggers the workflow.
Also, look into the IMG config of the following path. This might be a fitting solution.
In SPRO, go to Financial Accounting (New)---> Financial Accounting Global settings(New) -
>Tools --->Workflow ---> Workflow for Document Parking -->Reset Release Approvals(Customers).
Here, you can list down the fields, the workflow should restart. But, then you need to give the workflow details etc., in the relevant config settings.
We have used this in restarting workflows for General Ledger(GL) documents' workflow when some important fields are changed.
For this config settings, look into the following help link.
http://help.sap.com/erp2005_ehp_02/helpdata/en/01/a9cdd8455711d182b40000e829fbfe/frameset.htm
Hope this helps.
venu

Workflow - marking work items as obsolete

I'm working on a workflow that allows cost center managers to approve or reject purchase requisitions. I'm trying to create some logic that will trigger the workflow when the purchase req is significantly changed, in addition to just being created. When it gets changed, I want to be sure that it's not deleted. If it was deleted rather than being changed some other way, I want to mark all active work items for that particular req as obsolete so they're no longer out there for approval. I put in a "set obsolete" step for each piece of the workflow that creates a work item prior to terminating the workflow. When I try to test this, however, the workflow DOES recognize that the req was deleted, but it doesn't even show the "set obsolete" steps in the log, it just terminates. The "set obsolete" step doesn't seem to have much to it, but is it possible that I'm just doing something wrong?
Thanks,
Eric

Hi Eric
You shouldn't use "set obsolete" for this.
Depending on your version, you can either use a fork and a wait for the event "Deleted" in one of the branches or simply, in the new version, define a terminating event on the header level.
Check this thread, it explains how, the example is based on restart, but you can use the methodology to cancel you workflow instances as well.
Re: Restart Workflow ?
Regards
Morten Nielsen

SSRS Report for Incidents/Work Items Created or Closed over time

I'm curious if anyone has developed a custom report based off the DWDataMart that displays the count for creation of incidents or other work items over time or work items that are closed over time.

Hi Jon,
There is a blog, which talks about in detail regarding SCSM reporting,
http://scug.be/scsm/2012/04/10/working-with-scsm-reporting/
However related to your queries please refer to this,
http://blogs.technet.com/b/servicemanager/archive/2010/04/23/how-to-create-a-custom-report-and-display-it-in-the-console.aspx
Thanks,
Mohammad.
-Zakir, Let us know if the answer/post helps you :)

Work items creating for GoodsMovement IDOCS

Hi Friends,
We have IDOC to File and File to IDOC scenario, we are able to post GRN files into SAP successfully, but for some idocs , work items are creating for some line items where there is error . After analysis we have come to know that there is some error in article or price is missing.
what i would like to know is instead of creating idoc for some items success and some with work items ,can we restrict if there is error in any line item.
for example:
let us say if i have one GRN file with 10 line items.when i post this File into SAP .. It post 7 items as success and for 3 items it creates workitems.
1) Is there anyway i can restrict the entire idoc , instead of posting 7 items once and after re-processing 3 items in second one.?
2) how to avoid creating work items?
one more thing I have created a backgrounduser for PI while posting to SAP. Some articles are showing as article is locked by piuser.
can anyone suggest how to overcome this..
Regards,
Suman

Suman
What is the Message type / IDOC type your are using? You should be able to create one single IDOC with multiple line items instead of one IDOC for each item, provided the header information for the material document is the same for all the line items. In most cases this is possible.
Check your mapping in XI and see if you can club all the items in one single IDOC. Doing so will also prevent the material locked issue. But, point to note with this design is that you will be penalizing good records in your file just because one line item was in error.
KK

How can I specify an area path for the work item created on build failure?

In our department we are working with multiple build definitions for different parts of one Team project. We heavily use the Team Project feature. Teams are defined by area path nodes, so each team can only see it's area path. No one (except the admins)
can see the root project node.
When a build breaks, TFS generates a Bug. Unfortunately, this bug is assigned to the area path root node, so nobody can see the generated bug and act on it.
We would prefer to specify the area path for the generated work item in the build definition (not template, but property of a build definition), as every build belongs exclusively to one team.
I have found that you can populate fields of the generated work item by filling the "custom fields" of the "create work item" activity. But how do I set the area path as a parameter?
Guenter

Hi Cuenter,
Thanks for your post.
You should set the value like below in that activity:
New
Dictionary(Of
String,
String)
From {{"Area
Path",
"teamprojectname\areaname"}}
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.

Release Invoice - Workflow not working in Background - Need Help

Business Object : BUS2081.
The Requirement is : We need to release an Incomming Invoice.
For this we are using a FM : bapi_incominginvoice_release
and for Database updation : bapi_transaction_commit
Now we are setting the workflow in foreground and so a workitem is created in Inbox, when we execute that workitem, the Invoice is getting released.
But our client wants the release of the Invoice in background with our user intervention.
Now, when we r trying in background, commit is not working.
If we remove commit, Status is successful, but the Invoice is not getting released.
Please help me out on this issue. Its a imp req.
Thanks and Regards
Sowjanya Meegada.

Hi sowjanya,
I think you must have created the custom method to release the invoice, if not please create a custom method and write a zfunction module as below :
ZBAPI_INCOMINGINVOICE RELEASE( Inside this FM just call the standard FM)
BAPI_INCOMINGINVOICE RELEASE
COMMIT WORK.
ENDFUNCTION.
Then use the above FM to release the invoice.
It will work.
Thanks and Regards,
Swaminathan

Problem in Executing Dialog Work item

Dear all,
Iam presently working on SAP Enterprise Version (SAP 4.7). Suddenly after applying some service packs the workflow with dialog workitem's getting failed.
Through debugging i could able to identify that the function module "SWL_WI_SELECT" returs an error code 1 (i.e wi_reservation_failed).
Can someone help me to come out from the above problem...
Thanks and Regards,
K Vijayasekar.

Hi Vijayasekar,
I dont know the exact problem but what you could do is to run the Workflow Customizing through T-Code SWU3. It might be because some of the service packs might have changed the settings. Just run the Automatic customizing and the problem might get resolved.
Regards
Sudhi

Work Item - Step History - Message: Reserved work item replaced ??

Hello all,
I am currently trying to understand what went wrong with one of our WF. When I look at the "technical log" of the WF and I select one specific step, I see the following messages under the STEP HISTORY tab:
Dialog work item created - No Errors - JOHN - 06.05.2010 - 16:17:17
Execution started automatically - No Errors - JOHN - 06.05.2010 - 16:17:17
Reserved work item replaced - No Errors - JOHN - 06.05.2010 - 16:19:01
Agent determination for step '0000000001' failed - PAUL - 06.05.2010 - 16:19:11
I am trying to understand what caused the 3rd message (Reserved work item replaced) to be added the log.
Anyone knows the answer ?
PS: I know what caused the RED message about agent determination.
Thanks in advance.
José

Dear PAQUEJO
Could you let me know the root cause or solution for this.
I am also facing the same issue for the last 3 weeks.
Below is the work item step log:
       PI_MDM_ USR               Dialog work item created                 12.01.2011 08:16:53
       Olivia Ye                 Execution started                        12.01.2011 08:19:31
       Olivia Ye                 Reserved work item replaced              12.01.2011 08:20:31
       Olivia Ye                 Execution started                        12.01.2011 10:02:30
       Olivia Ye                 Reserved work item replaced              12.01.2011 10:03:12
       Olivia Ye                 Execution started                        12.01.2011 10:03:43
       Olivia Ye                 Reserved work item replaced              12.01.2011 10:03:50
       Olivia Ye                 Execution started                        12.01.2011 10:04:00
       Olivia Ye                 Reserved work item replaced              12.01.2011 10:12:16
Your help is highly appreciated.
Regards,
Raja Ram.

Calling Interactive Adobe Form from workflow work-item

Hi Experts,
Here is the requirement.
WE have Interactive Adobe Form developed and now the requirement is to call this form in our workflow as work-item.
When the work-item agent double-click on the work-item he must call the adboe form.
Please provide your inputs/suggestions/Solution/Tips.
Regards
Krishna

Hi Gurprit,
Thanks for answering my question , appreciated.
When I am in transaction SWFVISU in the drop-down for the Visualization type I dont see "Adobe Form" . Whether we need to create an ABAP Webdynpro to call Adobe form.
Please explain.
Regards
Krishna

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".
<b>Question:</b> 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

Please Help me with the Work Item agent to agent forwarding error

hi folks ,
This is the error I am getting when I am trying to forward the work item from agent to agent.
"Work item 000000017188: Method SAP_WAPI_FORWARD_WORKITEM not allowed for type F "
Please Help in this regards. its Urgent.
thanks in advance for your help
Krishna Chaitanya

The F type Workitem cannot be forwarded because it represents Workflow (Also Subworkflow) workitem Id.
You have to find out with workitem which has status W(Dialog Work Item; Represents a Single-Step Task) from SWWWIHEAD table and status should be in process and the TOP_WI_ID should be the value that you are trying to forward.
Thanks
Arghadip

Invoice Workflow : Dialog work item created

Similar Messages

Maybe you are looking for