Agent assignment when using Rule on Standard workflow raise and error

[Former Member]

Hi all,

We are struggling with a standard absence approval (leave requests) using a copy of the standard workflow template WS12300111.

On the "approval process" step as agent we select a rule 00000168 = Superior (as user) for...

On the binding area and we have an error:

"Container element 'ORG_AGENT' does not exist".

This is valid for both source and target container.

Binding Workflow -> Rule 'Superior (as user) for...' we have:

&_WF_INITIATOR& -> &ORG_AGENT&

My questions are: this is normal behavior since this is a copy from the standard workflow?

How we can resolve it?

Any hints are welcome!

Thanks in advance,

Eugen

[former_member182468]

Hi eugen,

If you facing problems in binding ,follow the belowmentioned steps -

1) asign rule = 000000168 for task.

2) select red and white button of define binding automatically and select continue.

This would generate the right binding.

Thanks,

sahiba

[Former Member]

Hi Sahiba,

The automatic binding feature is not working. The system display the message:

"The binding automatically cannot be defined".

I was doing also individual for both importing and exporting binding and got the same message.

[former_member182468]

Hi,

alright.

can you check you are facing this problem with every workflow ie any time u copy a workflow

and generate binding in any of task or it is specific to this workflow only .

this will help in debugging further.

thanks,

sahiba

[vijy_mukunthan]

Hi Eugen

If automatic binding is not working then drag and drop and the attributes you want to bind with the task. As i mention plz bind those binding with the task it will work.

Regards

vijay

[Former Member]

Hi,

Yes, it seems to happen to all workflow which we copied...

[Former Member]

Hi Vijay,

Yes, I already tried that.But we don't have all the elements on that specific rule 168...

However, the elements you mentioned i did find them but within rule 157.

We tried to use the rule 157, but the result is not good: the workflow is unable to find the approver and is stuck within approval process...

[Former Member]

Hi Vijay,

Well I follow your advice.

So I made a simple workflow (another one) with one decision point with 2 branches: approve or reject.

On agent assignment, I assigned a SAP user (hardcoded). The Leave request (hence the workflow) is working very fine.

Then come back and changed the settings to agent assignment, to a rule: 157 Manager - Superior (chief position).

The binding operation was successfully completed with parameters you mentioned already. Auto function was working fine but i double check. So far, so good.

Then when trying to send the leave request the system displays the error message:

"Unable to send the request".

At this moment I'm out of any options/ideas ...

Eugen

[vijy_mukunthan]

Hi Eugen

Go to SWIA t-code check the log and find y the error is occurring.

Regards

vijay

[vijy_mukunthan]

Hi Eugen

For the leave workflow u should not bind WF_INITIATOR U should bind

&REQ.INITIATOR.PERNR& -

---

> objid

otype ( P ) -

---

> otype

Create a workflow container element as otype and put initial value has 'P'.

Now it will work.

Regards

vijay

[Former Member]

Hi,

Can you be more specific, please?

I mean how to create the container element?

Thanks in advance,

Eugen

[vijy_mukunthan]

Hi Eugen

In the left hand side you would be having workflow container under the element you have

<Double-Click to Create>. click and create it.

Regards

vijay

[surjith_kumar]

Hi,

Can you assign this

&_WF_INITIATOR&  --> &ORG_OBJECT&

in the Rule Binding, instead of &_WF_INITIATOR& -> &ORG_AGENT&

Regards,

Surjith

[former_member185167]

Hello,

What version are you using? In 46C the 168 rule has ORG_OBJECT as a parameter.

regards

Rick Bakker

Hanabi Technology

[Former Member]

We're using ECC 5.0 and Enterprise Portal 7.0, if this helps.

I'm trying to put in place the other suggestions from thread!