PO Workflow Error : Agent determination for step '0000000093' failed

[Former Member]

Hi, I copied the standard PO workflow and assign 2 agents by position from organizational management. The agents are receiving the work item. (I set that in SWE2, the linkage is not changed even though there is error).

Everytime I create a new PO, either one of the messages below would appear:

1)

Error processing following event linkage:

BUS2012 RELEASESTEPCREATED WS90100016

Following error occurred:

SWF_RUN 594

Message text:

Import container contains errors (are any obligatory elements missing?)

Event container appended as attachment.

Event linkage not changed.

Event stored temporarily.

Events can be redelivered via event queue

administration (transaction SWEQADM).

2)

Please repair the suspended workflow

Context Information:

ID: 16101

Work Item Text: MM Workflow (PO Release)

User: WF-BATCH

Language: E

Press 'Execute' to display the workflow that has errors.

When I execute, the following errors are shown in the log:

Process Node:

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

Create:

Error when creating a component of type 'Step'

Create_WIM_Handle:

Error when creating a work item

Create_VIA_WFM:

Agent determination for step '0000000093' failed

EVALUATE_AGENT_VIA_RULE:

Error in resolution of rule 'AC20000027' for step '0000000093'

AC20000027:

Element REQUISITION is not available in the container

Does anyone have any idea how to solve the problem?

It seems to me that, even though the agents are assigned, the release codes are not passed over to the container. But, I already checked that in the binding, in the task TS20000166, &RELEASECODE& from workflow is passed to the Step's &RELEASECODE&.

Thank you in all advances...

[martin_nooteboom · Accepted solution]

Also check the event binding, is the release code passed from the event to the workflow? You can check the container also to see if that is populated correctly.

Regards,

Martin

[Former Member · Accepted solution]

Hi,

Nope, in the container, the release code is not there (not passed over).

The weird thing is, the binding is there, but I noticed this situation happens:

In the container, the release code and purchase order are two import parameters and when the workflow is first created, the initial value is <No Instance>, but after I run the workflow, the release code's initial value become empty. It seems to me that, the release code field is ignored totally (it will not be called/passed during workflow processing).

Does anyone face this situation before?

Thank you very much.

[martin_nooteboom · Accepted solution]

Did you check the event binding? The object and the release code should be passed from the event to the workflow.

Regards,

Martin

[Former Member · Accepted solution]

Hi Martin,

Do you mean the binding between the triggering event and the workflow?

Yes, there is the binding :

Event 'Release Step Created' -> Workflow

&_EVT_OBJECT& -> &PURCHASEORDER&

&RELEASECODE& -> &RELEASECODE&

&_EVT_CREATOR& -> &_WF_INITIATOR&

Thank you very much.

[martin_nooteboom · Accepted solution]

Ok, that looks good. You don't have the problem that two events are created? This could happen because of an entry in SWEC. But that is for the standard workflow.

Regarding your second error, the binding to the rule is also ok?

Regards,

Martin

[Former Member · Accepted solution]

Hi Martin,

What do you mean by two events are created?

Anyway, I checked out the SWEC.

I saw that for the BOR BUS2012, the event RELEASESTEPCREATED is only appearing once.

As for the second error, the binding to the rule AC20000027 is ok:

&_WI_OBJECT_ID& -> &PURCHASEORDER&

&RELEASECODE& -> &RELEASECODE&

I wondered why these two errors always occur...

Thanks a lot...

[martin_nooteboom · Accepted solution]

Turn on the event queue and check how many events are raised when a PO is created. The entry in SWEC (Change documents) is usually a problem which deactivates event linkage. But Normally this problem only arises when you use the standard workflow.

The binding to the rule should be different I think:

&_WI_OBJECT_ID& -> &PURCHASEORDER&

should be

&PURCHASEORDER& -> &PURCHASEORDER&

Regards,

Martin

[Former Member · Accepted solution]

Hi Please check the binding from Event to Workflow. The PurchaseOrder BO and the Release Code needs to be binded. Also check the binding of your Workflow explicitly. Also checvk whether the Wflow is properly ac=tivated.

Thanks

Arghadip

[Former Member · Accepted solution]

Hi Martin,

May I know how do I turn on the event to check for the events occurred when the PO is created?

Inside the SWEC, there are these events which I think related to the business object 2012:

Change Doc. Obj. : EINKBELEG

ObjectCategory : BO BOR Obj

Business Obj. Type : BUS2012

Event : CHANGED

ON : ON CHANGE

Change Doc. Obj. : EINKBELEG

ObjectCategory : BO BOR Obj

Business Obj. Type : QCYBUS2012

Event : CREATED

ON : ON CREATE

Change Doc. Obj. : EINKBELEG

ObjectCategory : BO BOR Obj

Business Obj. Type : BUS2012

Event : RELEASEDSTEPCREATED

ON : ON CREATE

Change Doc. Obj. : EINKBELEG

ObjectCategory : BO BOR Obj

Business Obj. Type : FREBUS2012

Event : CREATED

ON : ON CREATE

Change Doc. Obj. : EINKBELEG

ObjectCategory : BO BOR Obj

Business Obj. Type : FREBUS2012

Event : CHANGED

ON : ON CHANGE

Regarding the binding to the rule, I couldn't find the object purchase order, unless what you mean is the purchase order number which is in the &_WI_OBJECT_ID&. Just a piece of information, the binding to the rule AC20000027 is copied together from the standard workflow and I didn't change anything there.

Thank you very much for your advices.

[Former Member · Accepted solution]

Hi Arghadip,

-> The binding from event to workflow is ok by this event :

BUS 2012 RELEASESTEPCREATED

-> The workflow is also activated properly.

But what do you mean by PurchaseOrder BO and the Release Code need to be binded? Where do I check for this?

I think there is one information I should inform all fellow experts here, when I tested the Workflow in the SWDD, I need to enter the PO no and the release code, here, it is working properly without any errors. But, when I made it automatic (through real PO creation), these errors occurred, apparently, the release code is not passed over, but I already configured and set everything I knew. Hmmm, I have no idea which part went wrong, I even recopied the standard workflow and set the agents, but the same errors still happened.

Thanks a lot for your advices....

[martin_nooteboom · Accepted solution]

You can activate the event trace with transaction SWELS. You can examine it with transaction SWEL. Here you can see all the events raised in the system, and what happend with them (is a workflow started, or an error occured).

Normally when the standard workflow is used this entry in SWEC gives trouble:

Change Doc. Obj. : EINKBELEG

ObjectCategory : BO BOR Obj

Business Obj. Type : BUS2012

Event : RELEASEDSTEPCREATED

ON : ON CREATE

And should be deleted.

If it is only the PO number which is in &_WI_OBJECT_ID& then that is strange, because the system I checked (Release 4.7 I must add) the import parameters for the rule where the releasecode and the object for the PO (Bus2012) and not just the PO number. That's why I suggested to bind the object to the rule. Maybe it changed in later versions.

Regards,

Martin

[Former Member · Accepted solution]

Hi, Martin,

Sorry, I am new to workflow and is not quite familiar with the debugging of workflow. I followed your advice, switch on the event trace and now when a PO is created, the event trace list displayed two lines of the ReleaseStepCreated, both receivers are the same workflow I created. However, when I viewed the workitem of these two objects, one is actually processing, while another one showed an error. I guess this is why the workflow is working properly and yet sending an error message, because they are from these events.

But, how do I solve this? I only have one activation on the event ReleaseStepCreated for object BUS2012 in the SWE2. How come there will be two same events generated each time?

Thanks for your help a lot, at least, now I am clearer of the problem. Thanks in all advances.

[martin_nooteboom · Accepted solution]

I take it you found the solution in my previous post and deleted the entry in SWEC?

Regards,

Martin

[Former Member · Accepted solution]

Hi Martin,

Yes, deleting the entry apparently solved the problem, although I don't quite understand how this links to the problem and I am actually using a duplicate of the standard workflow. Anyway, thanks a lot for your help.

Thanks,

Yen Li

[martin_nooteboom · Accepted solution]

Well this solves the problem for that two events are raised and so two workflows are started. The problem with the entry in SWEC is it doesn't pass the releasecode this gives the problems and deactivates the event linkage.

I hope this gives a bit more insight.

Regards,

Martin