Correlation used with synchronous steps in BPM

[Former Member]

Hello,

we have a problem with a correlation.

A receiver step synchronous activates a correlation.

The step is completed by receiving a response.

The receiver step connects via sRFC to an R/3 system to trigger there an IDOC.

Next step of the BPM is to receive the IDOC from the R/3 system (async).

This system uses the correlation (time stamp field from RFC).

But: This doesn not work.

We only had success when using an asynchronous RFC.

Does anybody have experience with such issues?

What is possibly wrong with our correlation ?

(Corr. is local within a block where both steps are included, RFC and IDOC step)

regards

Dirk

[moorthy · Accepted solution]

Hi,

Probably Correlation is not active during the next receive step i,e Idoc .. So

Try out with Global Correlation i.e correlation to the entire process.. but it is not advisable.. but you can try out..

btw, if you are receiving the sync message, then you would have done, sync-async bridge right ? If so, you will get the response back only after closing the sync-async bridge right ? In this case, how are you making the next Recieve Step of Idoc in the same block ? just a thought... check out this.

Regards,

Moorthy

[Former Member · Accepted solution]

Hi Moorthy,

thank you for your answer.

In the meantime we found the error!

It was a fault in the interface which should connect the BPM. It was going into

somewhere.

Complex BPMs are really difficult to control.

But, we don´t use a sync/async bridge here because we were not sure if this is working if additional steps are following. The comm.process splits into an IDOC coming back or an RFC with the message that there is no IDOC.

And the BPM does not start with a synchronous step.

Our BPMs are looking quite interesting I think! And they are running, what a miracle!

Regards

Dirk

[Former Member · Accepted solution]

Here is a little twist to the correlation issue...

I had the following problem. I have a very simple Sync/Async bridge, including a sync. reveiver (sr) at the beginning, as closing S/A bridge sender (ss) at the end, and a async. sender (as) and an async. receiver (ar) in the middle. My messages have an orderId that I use for my correlation.

The first receiver (sr) activates the correclation (using the orderId in the request message).

I then attempted to "use correlation" in my async. receiver (ar) step. The correlation shows up in the drop down options in the properties window of the step, but my selection would not "stick" (it would show it and revert to the red question mark).

After checking my correlation and unsuccessfully trying a few permutations of where to "activate" the correlation, I tried this:

I temporarily turned my synchronous steps into asynchronous steps (sr and ss). Then I selected my correlation in the async. receive step and it "stuck". After my selection was accepted in the "use correlation" property of the async. receiver step, I turned my first and last step (sr and ss) back in to synchronous steps and had the desired result.

... and it worked! I guess it is just a little bug in the tool (which may not be an issue in later releases?!)

Marc

(FYI, I am using XI 3.0 SP 16)