Deep Structures in container

[Mark Daley]

Hello folks, 
 
I am building a Material Master Data Request workflow (ECC 5.0) and I would like your input on storing large amounts of data in deep structures in the workflow container.
 
The business requirement is to gather the material data from several agents concurrently/parallel(via custom screens) and once all tasks are completed the Material request is sent for approval. If all is well the data  is posted to SAP (via BAPI). Each agent enters unique data pertaining to their role in the business eg R&D, Finance etc.
 
In the workflow, I am storing this data in a single container element(deep structure) containing 18 sub structures eg MARA, MARC etc and 9 tables eg MAKT , MARM etc. 
 
The intention of using a single deep structure is to reduce maintenance on the number of wf bindings. The interface to the FM that calls the various custom screens uses this same deep structure. 
 
Could passing a large deep structure data element between task and wf cause issues eg performance/storage/archiving?  There will be approx 2000 workflows a month.
 
Given the data gathered from the agents must be approved before being posted in SAP, is there any other way I could be doing this other than using a deep structure to store the data in the workflow?
I don’t want to explicitly add a data element for each piece of material data in my wf container plus all the bindings!
 
I’d appreciate your input/experience especially if you have any experience of workflow handling large amounts of data in the container or with deep structures.
 
Thanks
Mark 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20110418/a42dc3b8/attachment.htm