Idocs stuck in workflow at status 51

Hi all,
There are lot of Idocs stuck in status 51 in workflow. Work flow error message reads as "Document OvershipCl does not exist". Can someone explain what does this mean and how do we clear these items.
Regards,
Santosh

Hi Santosh
You could also use transaction BD87 for further analysis and processing. This is more interactive. Please select the IDOC and on the left screen the the status record with entry 51 will have the details as to why the IDOC failed. Please correct as required in order that the IDOC will get processed.
Hope it helps. Please do assign points if found useful.
Regards,
Karthik

Similar Messages

Inbound idoc processing by workflow

Hello,
How can I find if an inbound IDoc has been processed via workflow ?
following are details -
1)status records 50 and 64 for the idoc show RFC user ID whereas 62 and 53 show WORKFLOW_020 user ID.
2)manual re process in test system using WE19 has all four status records by login user ID.
3)BD67 values for this process code was checked for the start events.
4)I checked standard task 30200090 following oss note 325361
5)The invoice document posted via this idoc has created by user ID as WORKFLOW_020
I do not have full knowledge of inbound idoc processing via workflow and I am in the process of learning the same. Kindly help.
thank you very much in advance,
Bhakti

Hello,
How can I find if an inbound IDoc has been processed via workflow ?
following are details -
1)status records 50 and 64 for the idoc show RFC user ID whereas 62 and 53 show WORKFLOW_020 user ID.
2)manual re process in test system using WE19 has all four status records by login user ID.
3)BD67 values for this process code was checked for the start events.
4)I checked standard task 30200090 following oss note 325361
5)The invoice document posted via this idoc has created by user ID as WORKFLOW_020
I do not have full knowledge of inbound idoc processing via workflow and I am in the process of learning the same. Kindly help.
thank you very much in advance,
Bhakti

IDoc Error Processing workflow

Invoices are posted from SRM to ECC as IDocs whose message type is BBPIV. When there is an error in the IDoc input such as invalid IO and GL, invalid company code etc., these IDocs will be moved to status 51.
When IDoc is moved to status 51, work item need to be sent to approvers saying this IDoc has an error and need to be corrected. For this a workflow task needs to be developed.
In our system, there are two types of IDoc invoices sent to ECC. One is of type INVOIC01 and another is of type BBPIV01. There already exists a standard task TS00008057 which is activated for the event INPUTERROROCCURREDMM for IDOCINVOIC object type.
I shouldn't use the same event (INPUTERROROCCURREDMM) and IDoc object type(IDOCINVOIC) for BBPIV01, because responsible agents for both type of invoices are different in our company.
Please help us in getting this resolved. Also let me know if my approach is wrong towards this problem.
Thanks,
Rajesh

Hi Rajesh,
Using the same BOR object and event for two different idoc types is not necessarily wrong. There are ways to differentiate the responsible agents based on the idoc type if needed.
Here is how I would solve this:
Prerequisite: you need to make sure that event IDOCINVOIC.INPUTERROROCCURREDMM is triggered when your BBPIV01 iDoc is in error. To check that, you can activate the event trace and test your idoc (activate with tx SWELS, display with tx SWEL).
If the event does not trigger then you need to find out which event is getting triggered (using the event trace as well).
Now the serious business:
1. Create a copy of standard task TS00008057 that will be used for when BBPIV01 iDocs are in error.
2. Link this task to your event IDOCINVOIC.INPUTERROROCCURREDMM in transaction SWETYPV
3. Check in SWO1 if you have an attribute that gives the idoc type (or anything else which you can use to determine wich workflow should start in each case).
If not you need to create a subtype of IDOCINVOIC and in the subtype create an attribute that returns the iDoc type. Then you would need to delegate IDOCINVOIC to your subtype.
4. Create start conditions (tx SWB_COND) in which you check that TS00008057 starts only when idoctype is INVOIC01 and your new task starts only when idoc type is BBPIV01.
Cheers,
Patrick

ORDERS idoc processing in workflow

I have a situation when processing ORDERS idocs thru workflow. The unit of measure is inadvertently switching from what is on the idoc (EA) to the base (CA) after correcting the "qty not in valid multiples" error and saving the order. the standard VA01 logic handles this situation correctly. Has anyone ever seen this 'switch' in any of their work. Any help would be greatly appreciated.

Hi,
The no of IDocs processed at a time is based on the Packet Size that is specified in the configuration of the Partner Profile(WE20). Likewise the specification of the Output Mode is given as either Transfer IDocs Immediately or Collect IDocs in which case the IDoc would go to 30 status and it would have to be processed using RSEOUT00.
Thanks
Krithika

Po Requisition workflow pending status issue

Hi
We have updated some quantity from 200 to 250 for a requisition line and sent for approval,at this time the user who updated the qty did not have the email address in oracle user name.So requistion status is always showing as pending.We have updated the oracle User with email address and ran Sync WF local tables concurrent program.
But we still could see requisition line in pending status.
Could anyone please tell me how to restart the requistion or any other solution to solve the issue.
Our apps version is 11.5.10.2
Thanks

Hi user;
please follow below and see its helpful:
Stuck POAPPRV Workflow Records At The Email PO Process Activity [ID 417722.1]
View Approval Workflow Hangs With No Error for Approved Purchase Orders and Requisitions [ID 413272.1]
APPROVE PO, WORKFLOW PROCESS, PROCESS HANGS [ID 1056081.6]
Workflow Is Not Completing For PO Supplier Change [ID 554024.1]
Regard
Helios

IDoc Delays: 64 to 62 status

Hello - We have been seeing some intermittent delays on some of our ORDERS idocs. They are configured to process immeadiately, but we have been seeing some delays when they are going from status 64 (Ready to be Transferred) to status 62 (IDoc passed to application). These delays are sporatic and ranging from 2 minutes to 20 minutes.
Any thoughts?
Thanks - Kyle Winters

Hi,
Are these idocs processed using workflows or ??
Please have a look at following SAP notes.
» SAP Note Number: 160670 Idocs remain in inbound with status 62
» SAP Note Number: 836022 ALE: Link to application log in status 62
» SAP Note Number: 92552 IDocs-Status 62 cannot be processed
» SAP Note Number: 631039 IDoc: Problems with inbound processing using workflow
» SAP Note Number: 194640 IDoc: Workflow is not started in RSEINB00
» SAP Note Number: 181729 ALE: IDocs remain in status 64 / 3.X inbound
» SAP Note Number: 168276 IDocs remain in status 64
KR Jaideep,

Idocs stuck in sm58

Hi All,
When I triggered Idocs in R3 ,they were stuck in sm58 with status : :000. I'm not able to release it.
I checked with port information, everything is correct.
When I checked with threads in SDN it says to check with authorization of userId in sm59 of R3. if this is
the case then I ll not be able to send any Idocs from R3. But in my case other Idocs are getting triggered,
only the newly created ones are stuck. Kindly suggest sollution to resolve this issue.

Hi,
for checking the metadata you could also have a look here:
http://help.sap.com/saphelp_nw04/helpdata/en/8a/b8b13bb3ace769e10000000a11402f/frameset.htm
Regards
Patrick

Workflow Internal Status: Cancelled

Dear All,
We have a SharePoint/Project Server 2013 Enterprise Edition and Sharepoint Designer deployment in HYPER V virtual environment. We are using it for Project Management. We are facing an issue while designing a workflows in SharePoint
designer 2013.
PROBLEM DESCRIPTION:
“Workflow Internal Status: Cancelled
" ERROR:
RequestorId: 7b51f972-22ad-faa7-a60a-20f365bff1e3. Details: System.ApplicationException: HTTP 500 {"SPRequestGuid":["7b51f972-22ad-faa7-a60a-20f365bff1e3"],"request-id":["7b51f972-22ad-faa7-a60a-20f365bff1e3"],"X-FRAME-OPTIONS":["SAMEORIGIN"],"SPRequestDuration":["116"],"SPIisLatency":["0"],"MicrosoftSharePointTeamServices":["15.0.0.4481"],"X-Content-Type-Options":["nosniff"],"X-MS-InvokeApp":["1;
RequireReadOnly"],"Date":["Tue, 24 Dec 2013 19:28:11 GMT"],"Server":["Microsoft-IIS\/7.5"],"X-Powered-By":["ASP.NET"]} at Microsoft.Activities.Hosting.Runtime.Subroutine.SubroutineChild.Execute(CodeActivityContext
context) at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager
bookmarkManager, Location resultLocation) "
Workflow stage status: Workflow is still in processing please refresh the page and try again
After configuring the workflow in SharePoint designer followed below mentioned TechNet blog to go through the workflow designing
URL: http://msdn.microsoft.com/en-us/library/office/jj163494.aspx
As in the blog project Event is set to when project is submitted, we tried a lot to submit the project but submit button was grayed out and unable to do this, then we changed to event
when project is committed from that above mentioned errors are occurred. Moreover we have tried to make simpler workflow but same result.
Detailed Description:
Installation of Workflow Manager 1.0
Installation of Service Bus and CU1
Start App Management Service (Also Configured in Managed Service App)
Start User Profile Service (Also Configured in Managed Service App)
Run the full user profile sync and Completed
Created the workflow using domain user account and assigned him proper permission
Thanks in Advance
REGARDS DANISH DANIE

If the workflow initiator does not have write access to the hidden Workflow History List, the same error happens.
To solve the issue, simply open the hidden list permission (through SharePoint Designer>All Files>Lists, for example) and make sure to have your potential initiators contribute rights. The list defaultly inherits the site's permissions.
kirtesh

Workflow Error status in checking In records (Records still getting syndicated to Port)

Hi Experts,
I have syndication strencil step before stop (check in) step.
After successfully syndication of records to respective ports when i see status of workflow it is going in Error state.
When i checked history of workflow then in last check in step it is giving error "insufficient right to checkin".
Owner for workflow is defined as "WFOWNER", which is specialy defined which do not have modify access to record and can see all workflow's status in workflow tab.
Below are the permissions this role is having which include checkin owned and no-owned records also.
Appreciate your comments!!
Thanks

Hi Ravi,
Thanks for promp reply.
I already have tried this option, but no luck... :-( .
Its still showing "insufficient right to checkin" in last stop check in step.
I did 1 testing that i want to share. I tried with only 3 steps, start -> syndication step -> stop and kept same owner of this workflow " WFOWNER". I got completed status with no error.
I was thinking that problem is with WFOWNER id or syndication step, but after this testing i am not sure where is the problem.
Thanks
Nitish Sharma

Send Commit to message stuck in "Message Scheduled" status

Hello,
I generated some messages using ABAP Proxy. However, the commit work never happened in the program that created the message. Now these messages are stuck in "Message Scheduled" status. How can I push the message forward. Can I trigger a commit? If so, how?
Regards
Cerish

Hi Cerish,
Are you getting this status in the XI ? If so, go to Queue Monitor and try to activate the same.
/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
Also check the SXMB_MONI of Application System(R/3) if you have a access about is proxy message is executed or not .
If the status is restart not possible, then you need to reprocess that.
Hope this helps,
regards,
moorthy

PO workflow showing status as APPROVED.. but in Oracle status is"IN PROCESS

In Our 11i , one of the PO workflow showing status as APPROVED.. but in Oracle Still showing the status as "IN PROCESS".. could you Please suggest solution...?

Hi,
What is the application release?
Please see if these docs help.
Troubleshooting Purchasing Approval for Documents in "IN PROCESS" or "Pre-Approved" Status [ID 225017.1]
How To Diagnose An Issue In Requester Change Order Processing [ID 453551.1]
How To Reset a Document From In Process or Pre-Approved To Incomplete/Requires Reapproval For Isolated Cases [ID 390023.1]
Thanks,
Hussein

In 4.6C, How to delete IDoc stuck?

Hi, experts
after I load more than 20000000 records data from R/3 side, I found out there are too many IDoc stuck in R/3 side use SM58.
How can I delete these IDoc in one time? the T-CODE 'WE11' and the program 'RSETESTD' can not use in my 4.6C system.RSETESTD.

try BD87

How can a Workflow get status CANCELLED

Hello,
We have the following situation.
A workflow shows status CANCELLED in the BBP_PD. All other information of the Workflow is gone in this trx!
Via the trx. SCOT we can see the workitem mail were send to the approval agents.
The question we have is:
1. Under what circumstances a Workflow can get status CANCELLED?2.
2. How can we analize, using the Workflow tools, what happened in the Workflow BEFORE it got cancelled? Did it reach the for instance the agents to get approved?
Thanks for any clue.
Aart

Hi,
Please go to transaction BBP_PD, open the document and find the workitem ID.
Display the workitem in SWI1 transaction. You see the worklfow log.
Regards,
Masa

How do we identify SC that are stuck in awaiting approval status?

All,
Extended Classic Scenario   7.01
We have Shopping Carts set up for auto approval.    From time to time some Shopping Carts get stuck in awaiting approval status and we need to manually force them to go.   We have not been able to identify a root cause for this so we would like to create an abap that would identify those SCs that are stuck then submit   BBP_REQREQ_TRANSFER   to transfer those SCs.
The problem we are having is finding the correct combination of status's that will capture those SCs that are truly awaiting approval.
We first find all those SC with status = I1015 (awaiting approval)
Then we exclude those with status i1040 (deleted) and i1129 (followon document created)
It seems in our testing that sometimes the status i1129 has an "X" in the inactive column.   Should those then be reprocessed and therefore not excluded?
Thoughts...
Sandra

Hi Sandra,
For your code logic, I1129 with inactive X should be included to get the list of SC which are in awaiting approval or may be approved but without follow on doc.
But could you check if you get any message in RZ20 after the follow on doc is created and it becomes inactive ?
may be you can check the SAP note: 1499352 - SRM Transfer: Redesign, bug fixes
Best Regards,
Anil

IDoc, EI and Workflow

Please give me a brief idea about IDoc, EI and Workflow.
Where I can find the useful documents?
Can anyone give me any PPT or documents regarding the same topics?

HI,
Check the links below:
ALE:
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217e1c51ce11d189570000e829fbbd/frameset.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
Please check this online document for ALE and IDoc.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
Also check this links for additional information.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
IDOCS
http://idocs.de/www5/books/IDocBook/IDOCS_CHAP09-11.pdf
http://idocs.de/cookbooks/idoc/cb12_idoc_20_outbound/idoc_outbound_45_rsnast00/docu.htm
IDOC / ALE Blogs
/people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
/people/kevin.wilson2/blog/2006/11/13/ale-scenario-development-guide
EDI:
Advanced guide to EDI configuration
http://www.erpgenie.com/sapgenie/docs/advanced_guide_to_edi_configuration.doc
EDI Architecture
http://www.cs.jyu.fi/el/tjtl63/Antin_esitys/sld003.htm
Overview of EDI and the IDoc Interface in SAP
http://sap-idoc2edi-consulting.com/pdfFiles/EDI_IDoc_Overview.pdf
How to Build a Basic EDI Interface Using an Imported Schema and Map
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/818a20be-0601-0010-e3b8-ac3d5f975319
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d98675ca-0d01-0010-c5a0-c70389f1a314
EDI Functional Design
http://www.erpgenie.com/sapgenie/docs/interface_function_specification.doc
Thoughts on EDI in an SAP XI Environment
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/135b0b94-0701-0010-f6a9-86a14057544a
Workflow is a more basis related component. This component allows you to configure SAP system to trigger the mail straight to the Inbox of the manager. It can be related to approval of PR or PO or it can be of anyother purpose. The main purpose is the manager need not to login GUI screen for approval. He could select the approval button in his outlook mail(This mail will contain complete details of purchase order), it will automaticall update in SAP back end.
Workflow will be per Business object. BO can be PR, PO etc.It is possible to set the event by when the workflow should trigger. For example it should trigger when the purchaser creates a PO and saves it . The saving action is called event. After the event is triggerred system will check for the starting conditions. It is possible to define starting condition per workflow. It is like your release strategy. If the value of PO is less than 1000 then it should be approved by one manager, if values >1000 then it should undergo approval from 2 managers.
There are plenty of predefined workflows which could be used straigt according to the purpose expected.However workflow is delicate and has to be configured with utmost care in proper sequence to avoid in consistencies.
Please follow the links,
http://help.sap.com/saphelp_nw04s/helpdata/en/04/926f8546f311d189470000e829fbbd/content.htm
http://help.sap.com/saphelp_46c/helpdata/en/c5/e4a930453d11d189430000e829fbbd/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/a1/172437130e0d09e10000009b38f839/frameset.htm
A good tutorial
http://www.thespot4sap.com/articles/Invoice_Verification_Automation_Using_SAP_Workflow.asp
http://www.sap-basis-abap.com/wf/sap-business-workflow.htm
http://www.sap-img.com/workflow/sap-workflow.htm
/people/alan.rickayzen/blog
/people/jocelyn.dart/blog/2006/06/19/why-use-abap-oo-with-workflow
a good book
http://www.sap-press.com/product.cfm?account=&product=H950
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
http://help.sap.com/saphelp_47x200/helpdata/en/4a/dac507002f11d295340000e82dec10/frameset.htm
http://www.workflowing.com/id18.htm
http://www.e-workflow.org/
http://web.mit.edu/sapr3/dev/newdevstand.html
Check the following PDF
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMSTART/BCBMTWFMSTART.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMDEMO/BCBMTWFMDEMO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCBMTWFMPM/BCBMTWFMPM.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
Regards,
Raj.

Idocs stuck in workflow at status 51

Similar Messages

Maybe you are looking for