Release Strategy issues in 4.6c

[Florin Wach]

Hi,

oh, I see. There's no problem with that on purchase requisitions BUS2105, as that table attribute is reading by itself using a SELECT ... FROM EBAN, but the same form within BUS2012 uses the function module for a buffered read.

To work around that, create a subtype w/delegation.
Redefine the attribute ReleaseStatus
Change the Source from "Database field" to "Virutal"
Create a coding with SELECT SINGLE FRGST FROM EKKO INTO object-releaseStatus WHERE ebeln = object-key.

Best wishes,
Florin

-------- Original-Nachricht --------
> Datum: Wed, 2 Jul 2008 08:37:34 -0500
> Von: "Sample, Rick" <Rick.Sample at graybar.com>
> An: "SAP Workflow Users\' Group" <sap-wug at mit.edu>
> Betreff: Release Strategy issues in 4.6c

> 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