Suggestion required for creating sales process through workflow

[Dart, Jocelyn]

Hi Nanda,


1)      Nothing wrong with using CX_BO_TEMPORARY as a permanent solution  ... although you might want to adjust the number of retries as well. Particularly if you are using the event queue to help spread the load.

2)      That's what the Event Queue is for.

3)      That's not an issue it's a description of the business scenario.

4)      The point of the event queue is to drip feed the events into the system to AVOID system performance issues caused by too many events hitting the system at one time.

The numbers you are talking about 100s are actually fairly small volumes for workflow.  Event queue should be enough for 100s and even 1000s.
But your stress test should include monitoring and if necessary adjusting the event queue parameters for read accesses and intervals - start with the standard and work from there.
Regards,
Jocelyn

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Nandakumar Alavandar
Sent: Saturday, 23 July 2011 7:50 PM
To: sap-wug at mit.edu
Subject: Suggestion required for creating sales process through workflow

Hi,

I have a specfic requirement to implement sales process worklow for my client .
Requirement:
The entire sales process starting from Sales order to Shipment cost is already completed in the legacy system, and the data is later send to Process Interface as a flat file to update the staging table in SAP through proxy.
The data recieved is for the previous day transactions, in few region records can be send every 20 minutes instantly from the legacy sytem to SAP .

The client is interested in doing the entire process of creation sales order to shipment process using the workflow , advantage the client thinks is the tracking process.

Issues Identified -
1) Locking issues while creating sales orders for the same contract.(there could be 400 sales order created in the same day and contract ),the  CX_BO_TEMPORARY to handle the temporary locking issue but not a permant solution.
2) Huge volume of workflow events will be triggered in a short duration of time,
3) Each workflow instance triggered will be involved in creation of sales order to shipment cost prcoess.
4)  Activated the event queue which distributes the load, but system performance could be affected.

Alternative solution proposed to do the entire process in schedule batch program and handle the error scenario through workflow .

Suggestion required whether the above process could be efficient through the workflow process for high voume data.

--
Warm Regards
Nanda kumar
SAP-Workflow Consultant.
Mobile: +61432070354<tel:%2B61432070354>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20110726/2a9bea2d/attachment.htm