Change Approval Agent in Workflow WS10400002 (SRM)

[Former Member]

Hi All,

I am working with a copy of Workflow WS10400002 in SRM and I need to change the First Approval Step for a Custom Step where I check a Z Table to obtain the Confirmation Approver. If The agent is a single User ID this works fine but If I set a Rule to get the Agent, this is not working. The Rules contains a call to a Z Function Module. The Rule works fine when I simulate a run but then, as part of the Workflow Execution is returning the following error:

EVALUATE_AGENT_VIA_RULE

AC99900001 -> Element CONFAMOUNT is not available in the container.

CONFAMOUNT is one of the Parameters from the Rule Container but it is not on the Workflow Container. Does this have to be on the Workflow Container as well? If so, why?

The Binding I am using for the rule is:

Agent:

Rule: 99900001

Importing:

Binding: &PROCCONFIRMATION.CREATEDBY& --> &CREATEDBY&

&PROCCONFIRMATION.GROSSAMOUNT& --> &CONFAMOUNT&

Exporting:

&APPROVALAGENTS& <-- &_RULE_RESULT.AGENTS&

Any help would be much appreciated.

Thanks & Regards,

Ernesto.

[former_member185167]

Hello,

No, it doesn't have to be in the Workflow container.

The binding is:

&PROCCONFIRMATION.GROSSAMOUNT& --> &CONFAMOUNT&

so you have to make sure that PROCCONFIRMATION.GROSSAMOUNT has a value.

regards

Rick Bakker

hanabi technology

[Former Member]

Hi Rick,

Thanks for your answer. I was writing my last answer while yours arrived. Please check what I've written.

Thanks

Ernesto.

[former_member185167]

Hi Ernesto,

That is strange! Could you remove CONFAMOUNT (from the workflow container) and see if it still works?

regards

Rick Bakker

hanabi technology

[Former Member]

Hi Ernesto,

CREATEDBY & CONFAMOUNT are Importing on the Rule but they aren't returned to the WF Container so I do not understand why I need to create them at WF Container Level.

It is not required to create it on the WF Container level as it becomes redundant. What i meant in my earlier post is if ur BOR do not have CONFAMOUNT field. then create it and populate the field in workflow before using it for agent determination. if ur BOR already has CONFAMOUNT then check in workflow log if it is populating correctly.

Regards,

Devananda A J

[Former Member]

Hi All,

Ok, this is strange. I removed both parameters CREATEDBY & CONFAMOUNT from the Workflow Container and the workflow is working fine. I really do not understand what happened. Anyway, I believe the error could have been a matter of wrong activation of the workflow.

Thanks for your help.

Regards,

Ernesto.

[former_member185167]

I am relieved!

[Former Member]

Hi Ernesto,

Check if you have made the import parameter "CONFAMOUNT" as mandatory parameter in the rule. If you have made it mandatory and your approver determination logic is based on the confirmation amount, then it is obvious that in your workflow you should have "CONFAMOUNT" (probably in a BOR). if your mapping of rule parameters and workflow container is proper then check the workflow log and see whether the workflow conatiner is populated. use the same values in workflow conatiner and simulate the rule to check if it is giving u the agents.

Regards,

Devananda A J

[Former Member]

Hi Devananda A J,

Thanks for your reply. The CONFAMOUNT field is not Mandatory on the Rule, nor it is the CREATEDBY parameter either. I created both parameters in the Workflow container now and the Workflow worked fine. If I am not using them (at container level), why do I have to create them as well?

Parameters From Workflow Container to Rule:

Binding:

Importing:

&PROCCONFIRMATION.CREATEDBY& --> &CREATEDBY&

&PROCCONFIRMATION.GROSSAMOUNT& --> &CONFAMOUNT&

Exporting:

&APPROVALAGENTS& <-- &_RULE_RESULT.AGENTS&

CREATEDBY & CONFAMOUNT are Importing on the Rule but they aren't returned to the WF Container so I do not understand why I need to create them at WF Container Level.

Thanks

Ernesto.