Workflow Container Limiations & Design Considerations

[Dart, Jocelyn]

Eneko, 
That sounds an ideal fit for HCM Workforce Process Management, otherwise known as HR Administrative Services. This is an Adobe/Workflow framework that includes update of pretty much any PA and/or PT infotypes.
Requires ECC 6.0 extension set 2. 
 
But no I wouldn't store all that data in the workflow - better to store it separately with just references passed to/from the workflow.  You could always consider using locked infotypes for the essays, with a final unlock at the end. 
Regard,s
Jocelyn

________________________________

From: sap-wug-bounces at mit.edu on behalf of eneko.bilbao at accenture.com
Sent: Fri 7/12/2007 2:34 PM
To: sap-wug at mit.edu
Subject: Workflow Container Limiations & Design Considerations



Hello All,

 

I'm looking for some design considerations and recommendation regarding workflow. 

 

We have a client who is asking for very complicated workflows, (6-14+ steps!!) with a large amount of data stored in the workflow container. The requirement is for each recipient to add approximately 1 page of data, (comments, recommendations, reviews etc) to the workflow. At the end of this workflow they would like all of this data posted to some custom HR Infotypes. However, the client does not want to access and process these "essays" in the GUI only in the UWL.

 

My questions are regarding technical limitations of SAP and possible negative impacts of the above approach. 

 

Can the workflow container handle this amount of data? Would you recommend storing this data in the container? If not, why not? Can the UWL display this much data? What are some possible alternative approaches we could recommend?

 

Any suggestions would be welcome.

 

Thank you.

 

Eneko Bilbao

Email: eneko.bilbao at accenture.com <mailto:eneko.bilbao at accenture.com> 

 

This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 6938 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20071207/34e69cd0/attachment.bin