1st Workflow task, problem binding triggering event

Former Member — Fri, 24 Feb 2006 19:37:10 GMT

Hello all,

I am working on my first single step task ever. What I initially thought would be a simple thing to do, has me pulling out my hair and saying they bad words out loud. Now that I'm done venting in this message, I will describe what I'm trying to do and the problem I'm running into. Hopefully some generous person who is familiar with this error can show me what I'm doing wrong and what needs to be changed.

I created a subtype, ZALE_EMAIL,

of the object IDOCGLMAST.

Object ZALE_EMAIL has a method ERROREMAIL

that I want executed when event INPUTERROROCCURRED

of object IDOCGLMAST is executed.

Method ERROREMAIL has a parameter Z_IDocNumber.

I created a new standard task. These are the parameters.

Object category: BOR Object Type

Object type: IDOCGLMAST

Event: INPUTERROROCCURRED

These are the elements of the binding that were created

when I clicked on the icon to generate the binding automatically:

EVENT >>>>>>>>>>>>>>>> TASK

&EXCEPTION&_____________&EXCEPTION&

&_EVT_OBJECT&___________&_WI_OBJECT_ID&

When I tried to bind the triggering event I get a warning error, but the bind completes successfully and the light turns green.

Conversion from '[BO.IDOCGLMAST]' to '[BO.ZALE_EMAIL]' can cause data-related errors

Message no. SWF_BND_001092

My question is, is this a warning that can be ignored?

If it can't be ignored, how do I get rid of it?

My workflow task starts, but it never completes. I think this is because the binding of the triggering event to the task is not working. I'm not sure how to verify my assumption. I have been looking at the different options within transaction SWUD.

I created this task so that I could send an e-mail when an IDOC, GLMAST01, is trying to update a nonexistent chart of accounts/General ledger account.

I am setting up ALE and document change management so that we can keep our production GL accounts in sync with development and QA.

We are on version 4.7.

Thanks

Bruce

Re: 1st Workflow task, problem binding triggering event

Former Member — Fri, 24 Feb 2006 23:25:06 GMT

Check the data types of the two items you are binding.

Make sure they both reference the same data objects.

Re: 1st Workflow task, problem binding triggering event

Former Member — Fri, 24 Feb 2006 23:59:42 GMT

Roger,

Thanks for your suggestion. The datatypes appear to be identical, although they are complex data types with many individual parts. The error is just a warning. But I think this warning is actually preventing the binding from completing successfully, even though the green light is on.

Bruce

topic Re: 1st Workflow task, problem binding triggering event in Application Development and Automation Discussions

1st Workflow task, problem binding triggering event

Re: 1st Workflow task, problem binding triggering event

Re: 1st Workflow task, problem binding triggering event