Business Object Instance Missing (Event -> Workflow Container )

Shaurya Jain jain.shaurya at gmail.com
Mon Mar 16 03:25:39 EDT 2015


Thanks all for your valuable inputs.

I found that problem was in binding of one of the task in the workflow
which was writing back the blank value of &wi_object_id& to workflow
container object element because of which the instance was going missing
from workflow container.

Regards,
Shaurya Jain

On Sun, Mar 15, 2015 at 3:52 PM, Goudham Vel <goudhamvel.88 at gmail.com>
wrote:

> Hi,
>
> Check in swel any work item is generated for your event.
> Check event binding and activation in workflow basic data and swetypv
> tcode.
>
>
> On Sunday, March 15, 2015, Mark Pyc <mark.pyc at gmail.com> wrote:
>
>> Also be aware of Logical Units of Work and update tasks. If the event is
>> raised before the object exists on the DB, existence checks will fail at
>> the start of the WF.
>>
>> Make sure the event is raised in the  update task.
>>
>> Have fun,
>> Mark
>>
>> Sent from my iPhone
>>
>> On 15 Mar 2015, at 7:19 pm, Rick Bakker <rbakker at gmail.com> wrote:
>>
>> Hello,
>>
>> Make sure your event -> workflow binding is correct.
>>
>> Try creating the event with SWUE and see if that works.
>>
>> regards
>> Rick
>>
>> On Sun, Mar 15, 2015 at 6:08 PM, Shaurya Jain <jain.shaurya at gmail.com>
>> wrote:
>>
>>> Dear Experts,
>>>
>>> I have a custom BO created for a specific purpose and getting an event
>>> of the same triggered using FM 'SAP_WAPI_CREATE_EVENT'. The issue arises
>>> when I see my workflow log in SWI1 and doesn't find any instance assigned
>>> to the object defined in workflow container.
>>>
>>> Various checks performed by me are as follows:
>>>
>>>    - Checked event log  in 'SWEL' and found everything perfect there.
>>>    - Digging further deep I found that there are no entries in tables
>>>    'SWW_CONTOB' & 'SWIVOBJECT' for my workflow runtime instance.
>>>    - Also checked table 'SWW_WI2OBJ' and found that entry exists for my
>>>    workflow runtime instance with object instance but with 'Removed' indicator
>>>    set. I didn't understand what does this actually mean as ideally 'Removed'
>>>    indicator should not be set.
>>>
>>>
>>> This problem seems to be currently only with my new BO & workflow as I
>>> checked existing ones & they seem to be working fine. Can anyone of you
>>> please guide me what can be the issue?
>>>
>>> Regards,
>>> Shaurya Jain
>>>
>>> _______________________________________________
>>> SAP-WUG mailing list
>>> SAP-WUG at mit.edu
>>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>>
>>>
>> _______________________________________________
>> SAP-WUG mailing list
>> SAP-WUG at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>
>>
>
> --
> Regards
> Goudham
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20150316/ad33e26b/attachment.htm


More information about the SAP-WUG mailing list