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

[mangesh_sonawane]

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.

[Former Member]

Is this issue got solved? I have the same problem here with the object FIPP

[former_member185167]

Please create a new thread for a new question.

Check your bindings, it looks like an object isn't being passed.

[mangesh_sonawane]

Dear All,

My concern is if it is an error then it should come to all PO's.

Why it is coming for few PO's and after change of PO and save it is flowing properly.

[anjan_paul]

HI,

  Check the Release Code , why it is not instatiated, it might cause the error.

[I042439]

Hi Mangesh

Since it is a custom event, you got to debug and see the triggering code is passing the necessary data correctly or not. See if it happens for POs which do not have a release strategy assigned to it. There can be N reasons for this intermittent behavior..... so the first point is to check WHY the full key is not being passed to the Workflow .

Can you share the event triggering code.... the full enhancement code and which BADI have you used?

I hope you are not using an explicit commit work while triggering the event (or calling the SAP WAPI function with a DO_COMMIT = 'X' ) in your BADI. It is quite possible that the explicit commit is interfering with the LUW of the whole PO save process and event gets triggered before the PO number is actually saved! ... just check this aspect too.

regards,

Modak

[I042439]

Hi Mangesh

What is the triggering event used here?

Regards,

Modak

[mangesh_sonawane]

It is a custom event we had created for business object.

And we are triggering it through and enhancement on saving of PO.

Event is custom event.

[former_member185167]

"And we are triggering it through and enhancement on saving of PO."

You had better make sure that the PO is saved before creating that event.

I would check that (in the code) before creating the event - read an attribute for example.

[Former Member]

Hi Magesh,

Check the container values for BO BUS2012 . It should have the PO number and release code as well.

Also since it is happening for only some PO's, check the authorization of the PO creator.

Thanks,

Vijay.

[mangesh_sonawane]

Hi ,

Authorization is proper if user is creating 10 PO's 1 or 2 will give above error.

Container values are fetching the same.I am triggering my custom event though that it is populating properly.

Earlier it was working fine

[SandySingh]

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]

Hi Sandy ,

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

[SandySingh]

Share the detailed WF log and WF container snapshot.

Regards

Sandy

[mangesh_sonawane]

Hi Sandy,

Please find the attached screenshots

[SandySingh]

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]

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]

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]

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]

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