Deep Structures in container (Mark Daley)

[Colm.Gavin@kerry.ie]

Mark,

I know you have said that you are going to use the deep nested structure 
but for anyone else who may be thinking of going down this route we 
implemented this functionality before using a ZTABLE with a Z business 
object.

We created a Z business object with an attribute that references our 
ZTABLE which was keyed with a request ID. We store the values on the form 
in the ZTABLE as the form is passed around by the workflow and then when 
the method in the ZOBJECT is called to create the material, the ZTBALE is 
read and the values populated.

We did experience some issues around change logging on the form and 
running out of space on the ZTABLE but in the main this issue worked well 
for us.

Good Luck,
Colm

> Hi  Kjetil/Mike/Jocelyn
> 
> thanks for your points, I appreciate your feedback.
> 
> Unfortunately I come to this project too late to impart the change I
> would like and some of your fine suggestions. So for now I am 
> governed by the "legitimate but annoying reasons".
> 
> So our approach (which is OO class based) will be to store the 
> material data in the contrainer. Data is captured in 'stagegates' 
> not all at once, so this minimises the size issue. Also I've done 
> analysis of SWWCNTP0 which is looking manageable (I've added 
> comments to a recent blog on this subject by Eddie Morris SAP)
> https://weblogs.sdn.sap.com/pub/wlg/24176
> 
> If this approach causes  problems, I like the suggestions mentioned 
> before ie XML serialising or the table deep struc. 
> 
> Mike regarding the option of storing the data in a table with a deep
> struc, I didn't think it was possible to store a deep structure in a
> database table, only internally in local tables.? Am I missing 
something?
> 
> Mark
> 
***************************************************************************************
The information transmitted is intended only for the person or entity to which it is 
addressed and may contain confidential and/or privileged material. Any review, 
retransmission, dissemination or other use of, or taking of any action in reliance 
upon, this information by persons or entities other than the intended recipient is 
prohibited and may be unlawful. Kerry Group accepts no liability for actions or effects 
based on the prohibited usage of this information. Kerry Group is not liable for the 
proper and complete transmission of the information contained in this communication or 
for any delay in its receipt. If you received this in error, please contact the sender 
and delete the material from any computer. 

Thank you for your attention.
***************************************************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20110427/9a122a34/attachment.htm