cancel
Showing results for 
Search instead for 
Did you mean: 

Error Source (expression '&BUS2012.PURCHASEORDER&') of binding assignment is not available

mangesh_sonawane
Participant
0 Kudos
1,583

Hi Team,

I am getting this error for only one workflow and it is come frequently.

Error Source (expression '&BUS2012.PURCHASEORDER&') of binding assignment is not available

I had refreshed SWU_OBUF,checked SWU3 everything is fine.After upgrade is it the issue because i had only changed this workflow.

Binding is proper it was working earlier now also it is working but for few PO's it is giving error.

Kindly help.


View Entire Topic
SandySingh
Active Contributor
0 Kudos

Hello

Check if the BOR object BUS2012 has a value ( instantiated). Make sure that in workflow header under "Start Event" tab, bindings are correct. See below

&_EVT_OBJECT&<=> &BUS2012&

Ensure that event linkages are maintained for this WF in Transaction SWE2.

Regards

Sandy

mangesh_sonawane
Participant
0 Kudos

Hi Sandy ,

It is maintained properly.Binding is done same as u mentioned.

SandySingh
Active Contributor
0 Kudos

Share the detailed WF log and WF container snapshot.

Regards

Sandy

mangesh_sonawane
Participant
0 Kudos

Hi Sandy,

Please find the attached screenshots

SandySingh
Active Contributor
0 Kudos

Hello Mangesh,

I can see two BOR objects in Container - BUS2012 and ZBUS2012. If you have created a subtype of BUS2012 , then you dont need 2 BOR objects in container. Check if the delegation of BOR BUS2012  is correct.

Looks like binding error is happening at a task level. Check the bindings of all workflow tasks and do a "Where Used" in WF container for BUS2012 to verify the bindings. Refer link below

Provide screenshot of task container which is in error.

Regards

sandy

mangesh_sonawane
Participant
0 Kudos

But it should have came every time it is coming only for few PO's.

Is it related to any Upgrade issue recently we had upgraded a new patch.

former_member185167
Active Contributor
0 Kudos

Hello,

In which step do you get this problem? Please always show the Chronological view when showing the workflow log, the default Tree view is almost useless.

Could it be that the BUS2012 object instance hasn't been created yet when the event is created?

A short wait, though not recommended, might help resolve this.

regards

Rick

mangesh_sonawane
Participant
0 Kudos

Hi Rick,

Error is on generation of PO only at this first step.

But why it is generating for one PO and not for other,Value is generated for business object you can see that.

mangesh_sonawane
Participant
0 Kudos

It is for few PO's even i had put wait condition before start of workflow.