Deep Structures in container

[Mike Pokraka]

Hi Mark,

Technically it's possible - if not ideal- but practically I don't see the
value in it. There are plenty of alternatives to prevent a material from
being used during creation. Plant/Material status fields are easy
candidates. The advantage of doing it all directly on the material is that
you have the entire history of who added what and when as opposed to a big
pile of data created by a system user.

More importantly, as you are already aware materials are complex, and
you're throwing any config-based validations and consistency controls out
of the window when you create a temporary storage concept. You either need
to duplicate this in all your input dialogs, or are headed for some
serious exception handling at posting stage.

Regards,
Mike


On Mon, April 18, 2011 1:55 pm, Mark Daley wrote:
>
>
>
>
>
>
> 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 		 	   		  _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>