strange container and binding behaviour in WAS 6.40

[Mike Pokraka]

Hi Ronen,
In that case, perhaps the system was still a little bit lazy from the
weekend? On the other hand, it's Monday, which is your equivalent of our
European Tuesday, which ... ah, my head hurts!  :)

You say 'is set before the workflow starts'. This is precisely what I am
talking about. How is it set? If it is something saved as part of a
document, it may not yet be in the DB at the time the WF is started,
particularly if you start the WF synchronously in your application. How is
the WF triggered? If you use change docs you should be OK, if you call it
directly, this is exactly the kind of trouble you could expect.

As a test, put in a dummy step with a requested start of 1 min - THEN do
your assignment. If that works then you have some synch issues at play and
I'd suggest looking at your event trigger.

Cheers,
Mike


> Mike,
>
>
>
> Thanks for the quick reply.
>
>
>
> Since Sunday is a working day here in Israel and it's the first day of the
> week, it seems the system was fresh after a peaceful weekend....
>
>
>
> I will try to explain in more detail:
>
>
>
> Business object ZMAT_REQ has an attribute called MRP. The value of that
> virtual attribute can be either X or blank and is set before the workflow
> starts.
>
>
>
> The workflow is triggered by an event from that object and the complete
> object instance is passed correctly to the workflow container.
>
>
>
> 1. Trying to set a simple condition in the workflow that asks if
> ZMAT_REQ.MRP = X always gives a false return even though the container
> element of the object has the value X
>
> 2. After defining a new standalone container element in the WF container
> that has the same properties as ZMAT_REQ.MRP and creating a container
> operation to pass the data from ZMAT_REQ.MRP  to that element, the new
> element always gets a blank value.
>
>
>
>
>
> Again, these are problems I encountered only on WAS 6.40
>
>
>
> We are on the following support package level:
>
> SAP_BASIS    640     0016
> SAP_ABA       640     0016
> ST-PI              2005_1_640 0003
> PI_BASIS        2005_1_640 0006
> SAP_BW        350     0016
> SAP_HR         500     0013
> SAP_APPL     500     0012
>
>
>
>
>
> Any ideas you may have are more than welcome !
>
>
>
> Many thanks in advance,
>
>
>
> Ronen Fox
>
>
>
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>