WF Error: Object FLOWITEM method EXECUTE cannot be executed

[Former Member]

Folks;

  I'm at my wits end.  For teh past 7 hours I have not be able to resolve a Workflow error on a WF that worked fine just 20 hours ago!!!!

WF is an Email to originator of a Purchase Requisition when ever there is a Goods Receipt of the materials from the PO that is created from the Purchase Req.

The full error messages are:

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

Work item 000000553431: Object FLOWITEM method EXECUTE cannot be executed

Unable to determine the value of component ''

Error in the evaluation of expression '<???>&GOODSRECPTDATA.MATDOCUMENTYEAR&' for item '1'

Unable to determine the value of component ''

Error in the evaluation of expression '<???>&GOODSRECPTDATA.MATERIALDOCUMENT&' for item '1'

Source (expression '&GOODSRECPTDATA.MATERIALDOCUMENT&') of binding assignment is not available

Source (expression '&GOODSRECPTDATA.MATDOCUMENTYEAR&') of binding assignment is not available

Just yesterday I had this very simple 3 step WF working fine and sending out emails.

Come to work this morning to generate a few more emails to review with my customer and BOOM, nothing works any more.  I made NO changes between the last time this new WF worked and today and yet it is failing.

I made a copy of the MKPF Business Object and the key for this object is the Material Doc Nbr and Material Doc Year.  I added 3 new methods to the object to read Purch. Req. and PO data and do the email.

The GOODSRECPTDATA container element is of BOR type ZMKPF.

Right at the start of the WF is where the error is occuring.

When I look at the Container data in the WF Log, I can see the Material Doc and Matl Doc Year right in the GOODSRECPTDATA object.  Everything looks good in the Container.

Now I am throwing everything but the kitchen sink at the WF and nothing is working.  Reactivations, changing a character in the email message and then saving and then reactivating, etc. ... nothing is working.

Any help in pointing me in the right direction would be greatly appreaciated.

Scott.

[former_member185167 · Accepted solution]

Hello,

Buffers get reset at midnight so it's not a complete mystery when these things happen without an apparent change.

You may be able to see GOODSRECPTDATA with a value in the workflow now, but it could be that it was not the case when the workflow started - and you did say this was at the beginning of the workflow.

For a quick workaround, I would put a 1-minute dummy wait step as the first step of the workflow.

For testing purposes, you could put another step before that where you copy GOODSRECPTDATA.MATDOCUMENTYEAR to a workflow container element, so you can see if it had a value then.

regards

Rick Bakker / hanabi technology

[Former Member · Accepted solution]

Rick, thanks for the insight.

The WF is now working.  It was a delay issue.  I was doing a lot of Update Debugging of the BADI that I wrote to call the Event, so I removed all the stops and turned off Update Debugging and it worked.

I didn't have to put in the delay, but it seems that the debugging was holding off on posting the Material document long enought till the WF started.

Thanks again.

[former_member185167 · Accepted solution]

Good! Thanks for the follow-up.

[Former Member · Accepted solution]

I actually did put in an Activity step at the start of the WF with the WAIT command for 20 seconds to allow the system to fully post the Material Document (never know when you might have a 50+ line MIGO Goods Receipt posting).  Just to be on the safe side.

Thanks again.

[Former Member]

Hi there,

Is the SMTP Server still running in your system (check transaction SCOT)? Is the email still valid or has someone remove your email address from IT0105 (if your are getting it from HR) or email address attached to your userid?

Hope it helps.

What task are you using btw?

Best regadrs,

Brian