BPM Process Sleep / Wait for long duration - is it feasable in SAP PI?

[Former Member]

Hi

We have a business requirement where based on a particular date in the future, we require a message we receive to "wait" until that date before it can bed processed (several weeks/months).

I understand that there is a "wait" step in CCBPM - has anybody had any experience with using this step for "long running processes".

When using this, is SAP PI intelligent enough to "sleep" and free resources for this process until the date arrives in the wait step?

What happens with other messages hitting the BPM and there is a process on a wait step? Can queing be setup that subsequent messages that are not on a wait step be processed ahead of the BPM sitting on a wait step?

Are there any other better solutions in SAP PI instead of using BPM wait for a long running transaction (several weeks)?

Thanks in advance.

[Former Member]

Thank you for the feedback. Unfortunately, we need to find a mechanism in SAP PI to hold the data until a particular date, as the destination system can only process the data on that particular date. The source system also cannot restrict sending the message on particular date. I guess one alternative is to persist the data in a custom SAP PI table and create a custom report to execute daily and to check for the particular date condition, to pick up the persisted message off that table and feed a SAP PI process to transform and deliver the message to the desintation system.

Do you know how the queing in BPM works when a process is sitting in a wait step? Can other messages invoking the BPM be processed even though their are other instances sitting in a wait step?

[former_member200962]

Can other messages invoking the BPM be processed even though their are other instances sitting in a wait step?

Multiple instances of the BPM cannot be triggered....only when the BPM completes the existing message processing it will be able to process new request.....till then the message will go into queue....may even happen that the queue gets blocked after waiting for a longer duration

Regards,

Abhishek.

[Former Member]

Hi,

AFAIK it's an anti pattern to run a process over such a long time.

Here it's said that at should not longer run than a few days:

http://help.sap.com/saphelp_nw04s/helpdata/en/43/d92e428819da2ce10000000a1550b0/frameset.htm

But even a day is quite a long time.

All informations of the process must get stored and it's very memory consuming specially if you expext a lot process instances.

It would try to avoid this situation.

Regards

Patrick

[Former Member]

Hi,

Running BPM for long duration means hogging on to system memory...One alternative would be to ge tthe data into the destination application and process it when required.

eg. Get the data and store it as IDoc and then write a logic to process it when required

Regards

Vijaya