AW: Accessing a container value in EBP 3.5

[Michael Pokraka]

Hi Sue,
The container stuff has moved out of the tables into XML formats, which 
is more suitable to store structured elements. I've tried to retrieve 
this manually before and it got ugly beforeI got very far so I left it 
as is. (My initial reasons were similar to yours).
You can tell it to use conventional containers, though I'd very much 
advise not to. SWDC, tab 'Default Values', persistence profile. This can 
also be changed on a per WF basis, under header tabs version dependent 
-> Control -> Persistence profile. This is provided for cases where a 
lot of custom reporting has been built around SWW_CONT, and is such a 
non-recommended option that Jocelyn didn't even dare mention it. For 
your case it's probably a bit late since it's only new WF's that wil use 
the setting, but I thought I'd mention it since you asked about the 
differences... The upgrade / 'whats new' notes for 620 have a few useful 
pointers as well.
Cheers
Mike

Susan R. Keohan wrote:

> Hi Nate,
>
> Of course, that's all I really want to do (read the tables using the 
> data browser), but it seems in EBP 3.5/Basis 6.20 things are a little 
> different.  I cannot get the container element using SE16, workitem 
> ID, elementname.  I can, however, retrieve it if I use 
> SAP_WAPI_READ_CONTAINER.
>
> Understanding the underlying differences here would also be helpful.
>
> Regards,
> Sue
>
> Workflow wrote:
>
>> Hello Sue
>> If all you are doing is reading the data for a one-time query and you 
>> know
>> precisely what table is involved, why write a report, use the data 
>> browser.
>> If you want to manipulate the container data and/or workitem status 
>> then it
>> is highly recommended to use the new SAP_WAPI functions.  Updating via
>> SAP_WAPI is the application equivalent of calling a BAPI with everything
>> implied, data consistency, rollback, authorisations, etc.
>>
>> Yours truly
>> Nate
>>
>>
>> -----Ursprungliche Nachricht-----
>> Von: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]Im Auftrag
>> von Susan R. Keohan
>> Gesendet: Dienstag, 31. Mai 2005 20:28
>> An: SAP Workflow Users' Group
>> Betreff: Accessing a container value in EBP 3.5
>>
>>
>> Hello all,
>>
>> Keeping in mind Jocelyn's advice to use SAP_WAPIs to access data from
>> workflow containers, and also,
>> that I am new to the Basis 620/EBP 3.5 world, I have a need to do a 
>> one-time
>> report in production of
>> all instances of a certain container element (which would indicate to me
>> whether a Shopping Cart was
>> changed or rejected, as our custom-built workflow treats both cases 
>> the same
>> way).  In the R/3 days,
>> for this type of one-off analyis, I would, pardon me Jocelyn, just 
>> run TX
>> SE16 against SWW_CONT and
>> pull all occurrences of this container element.
>>
>> Obviously, in the brave new world, I can't do that.  I've looked at
>> SAP_WAPI_READ_CONTAINER, and it
>> passes back the container elements I am interested in, but I am 
>> reluctant to
>> a) run it 60000 times,
>> or b) code a wrapper and go through the whole 'move to prod' business if
>> there is a simple elegant
>> solution for such a simple query.
>>
>> If there is no simple elegant way, then I'll just write a wrapper, 
>> because
>> probably these one-off
>> things turn into regular reports anyway.  But I'd appreciate any 
>> feedback
>> from you EBP/SRM/WF gurus!
>>
>> Thanks
>> Sue
>> -- 
>> Susan R. Keohan
>> SAP Workflow Developer
>> MIT Lincoln Laboratory
>> 244 Wood Street
>> LI-200
>> Lexington, MA. 02420
>> 781-981-3561
>> keohan at ll.mit.edu
>>
>> _______________________________________________
>> 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
>>
>