Release Strategy issues in 4.6c

[Mike Pokraka]

The BOR DB attributes buffers themselves - Florian's response bears this out.
You could also try doing a:
> SWC_REFRESH_OBJECT self.
in your BOR code either at the beginning of the next method in your WF or
if you are evaluating an attribute then stick a refresh method based on
the above after the event.

Cheers,
Mike


On Wed, July 2, 2008 2:37 pm, Sample, Rick wrote:
> Hi WF's,
>
> I have an issue with performance. I think!
> I have a Purchase Release Strategy WF I am working on.
> User approves his step, Wf catches the Release event and
> evaluates for next approver. Standard approval stuff.
>
> The issue:
> When user approves his task, wf event triggers, then I immediately go
> and evaluate the Rel Strategy.
> The standard BOR swc_get_property self 'RELEASESTATUS' l_status is
> obviously getting the BUFFERED data.
> If I put in a WAIT UP TO 3 SECONDS then to a SELECT with BYPASSING
> BUFFER I get the correct value
> from the SELECT, and I can verify that the BOR get property is the
> buffered data.
>
> In all my time doing WF, I have never had to work around such a timing
> issues.
> This solution 'appears' to work and is in a background task, so I don't
> think it will be an problem.
>
> Also, I tried using the FMs in ME01 to refresh EKKO buffers, read the
> EKKO buffered data, etc. with no success.
> Anyone have a more elegant solution or comments with my above solution?
>
> Thanks much,
>
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>