Error While Creating Workflow for Purchase Requisition Rejection

[Former Member]

HI Experts,

Purchase Requisition No is not Displaying in the Business Workplace Inbox after my Work flow got triggered.

In Work flow i am Using the Task 97600004 which i copied from the Standard Task 65400032. This Task i called in the Activity Step having Work Item Display Tab. In this Tab while i am checking at Work Item Text for Identification of Work item in work flow inbox level it is Giving Error "Container element '_WI_OBJECT_ID' does not exist and also Insert Expression is in Disable Mode.

In Business Workplace Inbox i am getting message as "Purchase requisition 00000 rejected".

Please Suggest where i am Committing Error.

Thanks in Advance

Srikanth Kumar

[former_member193382 · Accepted solution]

Hi,

Check is there any container WIOBJECT_ID. If no create one with the with data type as bo that you are using (BUS2009/BUS2105). Then do the binding between workflow to task container and then check again.

Let me know if you have any queries.

Regards,

Raj

[Former Member · Accepted solution]

HI.

I Have Checked the work flow as suggested Dheepak

In Start Event of Work flow i declared BUS2105 as BOR Object . The Task which i copied contains BUS2009 as default.

As Raj Suggested In Task i have Created a New Element BUS2105 at Container Tab and set binding in task and set the Binding between Work flow and Task. Now it is working fine and i am getting the PR No in the Message of SBWP inbox.

But i Having one more doubt regarding this issue only Why BUS2009 BOR object Type is not working which is the Task as default even though its binding is set between work flow and task?

Thanks Dheepak and Raj for Your Valuable Suggestions. My gmail id is srikanth537. Can u add me In your Friends list.

Thanks

Srikanth Kumar

09937876902

Edited by: Srikanth Kumar Talasu on Dec 23, 2008 11:59 AM

[Former Member]

Hi Srikanth Kumar,

Check your binding in forkflow starting from Event to workflow , workflow to task, Task to method and vice versa you would have copied the standard task but would have not done the binding proparly.

Regards,

Dheepak