<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
Hi Paul/Mike<BR>
<BR>
thanks for your replies, sorry for the delay getting back, we've been discussing this internally.<BR>
<BR>
I agree with you both that storing outside of workflow on either SAP or custom tables is the best approach. <BR>
<BR>
Storing the data in SAP Master Data and using statuses is an obvious way to go, but it not an option here for legitimate but annoying reasons I won't go into.<BR>
Storing in Z tables, is too complex as it will effectively mean replicating SAP Material Master.<BR>
<BR>
So we're are going to take approach of storing in the deep struc in the container. I've done some anaylysis of SWWCNTP0<BR>
I did a simple test with a container with 1 basic element, it takes up approc 1 line (1024 chars). My deep struc unfilled takes up 3,700chars, and filled takes up 10,000chars.<BR>
<BR>
Is this alot of space for a WF container are there any guidlines on this? Or is it all down to system size etc.<BR>
<BR>
I've read that if this table gets too large there could be performance issues, so our intention is that in PRD we'll just have to archive more frequently. <BR>
<BR>
Is this the main potential impact on performance or could there be others associated with passing alot of data between containers?<BR>
<BR>
Would like to hear your experience.<BR>
<BR>
Mark<BR>
<BR>
<BR>
> Subject: Re: Deep Structures in container<BR>> To: sap-wug@mit.edu<BR>> From: Paul.Bakker@osr.treasury.qld.gov.au<BR>> Date: Tue, 19 Apr 2011 08:06:12 +1000<BR>> <BR>> Mark,<BR>> <BR>> Your approach sounds a lot like the workflow 'forms' concept, where a form<BR>> full of data is passed to various users for completion (and approval), and<BR>> is then committed to the database. But I think 'forms' can only handle flat<BR>> structures.<BR>> <BR>> Generally it is not best practice to pass large amounts of data in a<BR>> workflow. Imagine how the container database table would blow out in size,<BR>> if the data was replicated for each workitem..!<BR>> Instead, pass a unique key to the data.<BR>> <BR>> So in this case, you could store all this to-be-approved Material data in a<BR>> custom (nested) database table. The table could have a GUID key, which the<BR>> workflow can refer to.<BR>> <BR>> Or.. does Material Management have the concept of a 'parked' material, that<BR>> can be stored in standard tables, pending approval?<BR>> <BR>> cheers<BR>> Paul Bakker<BR>> <BR>> <BR>> <BR>> From: Mark Daley <mark_daley@hotmail.com><BR>> To: <sap-wug@mit.edu><BR>> Date: 18/04/2011 10:59 PM<BR>> Subject: Deep Structures in container<BR>> Sent by: sap-wug-bounces@mit.edu<BR>> <BR>> <BR>> <BR>> <BR>> Hello folks,<BR>> <BR>> I am building a Material Master Data Request workflow (ECC 5.0) and I would<BR>> like your input on storing large amounts of data in deep structures in the<BR>> workflow container.<BR>> <BR>> The business requirement is to gather the material data from several agents<BR>> concurrently/parallel(via custom screens) and once all tasks are completed<BR>> the Material request is sent for approval. If all is well the data is<BR>> posted to SAP (via BAPI). Each agent enters unique data pertaining to their<BR>> role in the business eg R&D, Finance etc.<BR>> <BR>> In the workflow, I am storing this data in a single container element(deep<BR>> structure) containing 18 sub structures eg MARA, MARC etc and 9 tables eg<BR>> MAKT , MARM etc.<BR>> <BR>> The intention of using a single deep structure is to reduce maintenance on<BR>> the number of wf bindings. The interface to the FM that calls the various<BR>> custom screens uses this same deep structure.<BR>> <BR>> Could passing a large deep structure data element between task and wf cause<BR>> issues eg performance/storage/archiving? There will be approx 2000<BR>> workflows a month.<BR>> <BR>> Given the data gathered from the agents must be approved before being<BR>> posted in SAP, is there any other way I could be doing this other than<BR>> using a deep structure to store the data in the workflow?<BR>> I don’t want to explicitly add a data element for each piece of material<BR>> data in my wf container plus all the bindings!<BR>> <BR>> I’d appreciate your input/experience especially if you have any experience<BR>> of workflow handling large amounts of data in the container or with deep<BR>> structures.<BR>> <BR>> Thanks<BR>> Mark_______________________________________________<BR>> SAP-WUG mailing list<BR>> SAP-WUG@mit.edu<BR>> http://mailman.mit.edu/mailman/listinfo/sap-wug<BR>> <BR>> *********************************************************************************************<BR>> Only an individual or entity who is intended to be a recipient of this e-mail may access or use the information contained in this e-mail or any of its attachments. Opinions contained in this e-mail or any of its attachments do not necessarily reflect the opinions of Queensland Treasury.<BR>> <BR>> The contents of this e-mail and any attachments are confidential and may be legally privileged and the subject of copyright. If you have received this e-mail in error, please notify Queensland Treasury immediately and erase all copies of the e-mail and the attachments. Queensland Treasury uses virus scanning software. However, it is not liable for viruses present in this e-mail or in any attachment. <BR>> ***************************************************************************************************<BR>> <BR>> <BR>> _______________________________________________<BR>> SAP-WUG mailing list<BR>> SAP-WUG@mit.edu<BR>> http://mailman.mit.edu/mailman/listinfo/sap-wug<BR> </body>
</html>