Error when processing node '0000000004' (ParForEach index 000000)

Mon Dec 14 17:27:21 EST 2009

David,

 This could also be an authorization issue (with the dialog user of the
previous step!).  See note 755767.

cheers
Paul Bakker

             "Bibby, David"                                                
             <david.bibby at link                                             
             laters.com>                                                To 
             Sent by:                  "'SAP Workflow Users' Group'"       
             sap-wug-bounces at m         <sap-wug at mit.edu>                   
             it.edu                                                     cc 

                                                                   Subject 
             14/12/2009 09:34          RE: Error when processing node      
             PM                        '0000000004' (ParForEach index      
                                       000000)                             

             Please respond to                                             
               "SAP Workflow                                               
               Users' Group"                                               
             <sap-wug at mit.edu>                                             

Rick,
When I display all errors I get:

Work item 000000170644: Object FLOWITEM method EXECUTE cannot be executed
Error when processing node '0000000004' (ParForEach index 000000)
Error when creating a work item
Error when creating a component of type 'Step'
Error when processing node '0000000004' (ParForEach index 000000)
Error during result processing of work item 000000170645
Agent determination for step '0000000004' failed
Workflow WS00200001 no. 000000170644 activity 0000000004 role 'AC00200136':
No agent found
Resolution of rule AC00200136 for task TS00207914: no agent found

It appears that rule 200136 is an agent determination function
(CRM_ERMS_AGENT_DETERM1) so I think that this is erroring because the
ACTIONS table is empty.
I just need to figure out now where this table gets populated from.

Thanks
David

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
Rick Bakker
Sent: 13 December 2009 20:08
To: SAP Workflow Users' Group
Subject: Re: Error when processing node '0000000004' (ParForEach index
000000)

Hello,

That's a very generic error, see if you can find more details, eg try
Extras > All Errors in the workflow log.

regards
Rick Bakker
Hanabi Technology

On Sun, Dec 13, 2009 at 5:47 AM, Bibby, David <david.bibby at linklaters.com>
wrote:
> Prakash,
> There are several multi-line elements, some a filled, the ad hoc ones
> are not but I the main workflow says it is in error yet the only step
> inside the workflow to have executed has executed successfully.
> Regards
> David
> ________________________________
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
> Behalf Of Prakashreddy Sabbu
> Sent: 11 December 2009 16:42
> To: SAP Workflow Users' Group
> Subject: RE: Error when processing node '0000000004' (ParForEach index
> 000000)
>
> Hi David,
>           Did you check the Multiline element has filled with values.
>
> Thanks,
> Prakash
> ________________________________
> From: sap-wug-bounces at mit.edu on behalf of Bibby, David
> Sent: Fri 12/11/2009 9:04 PM
> To: 'SAP Workflow Users' Group'
> Subject: Error when processing node '0000000004' (ParForEach index
> 000000)
>
>  Hi,
> I have set up an ERMS workflow (SAP Standard workflow) number 002000001.
> When the even in received I can see this in SWEL and the receiver
002000001.
> However when I look in the workflow log I get the message "Error when
> processing node '0000000004' (ParForEach index 000000)"
>
> This seems to be hapenning on a decision step.
> Has anyone seen this type of error before and know what is causing it?
> Many Thanks
> David
> _______________________________________________
> Any business communication, sent by or on behalf of Linklaters LLP or
> one of its affiliated firms or other entities (together "Linklaters"),
> is confidential and may be privileged or otherwise protected. If you
> receive it in error please inform us and then delete it from your
> system. You should not copy it or disclose its contents to anyone.
> Messages sent to and from Linklaters may be monitored to ensure
> compliance with internal policies and to protect our business. Emails
> are not secure and cannot be guaranteed to be error free. Anyone who
> communicates with us by email is taken to accept these risks.
> Linklaters LLP (www.linklaters.com) is a limited liability partnership
> registered in England and Wales with registered number OC326345. It is
> a law firm regulated by the Solicitors Regulation Authority
> (www.sra.org.uk). The term partner in relation to Linklaters LLP is
> used to refer to a member of Linklaters LLP or an employee or
> consultant of Linklaters LLP or any of its affiliated firms or entities
with equivalent standing and qualifications.
> A list of Linklaters LLP members together with a list of those
> non-members who are designated as partners and their professional
> qualifications, may be inspected at our registered office, One Silk
> Street, London EC2Y 8HQ and such persons are either solicitors,
> registered foreign lawyers or European lawyers.
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

******************************************************************************************************************************************************

Only an individual or entity who is intended to be a recipient of this e-mail may access or use the information contained in this e-mail or any of its attachments.  Opinions contained in this e-mail or any of its attachments do not necessarily reflect the opinions of Queensland Treasury.

The contents of this e-mail and any attachments are confidential and may be legally privileged and the subject of copyright.  If you have received this e-mail in error, please notify Queensland Treasury immediately and erase all copies of the e-mail and the attachments.  Queensland Treasury uses virus scanning software.  However, it is not liable for viruses present in this e-mail or in any attachment.  

******************************************************************************************************************************************************