cancel
Showing results for 
Search instead for 
Did you mean: 

Combined Correlation

Former Member
0 Kudos

Hi there,

i'm currently trying to implement a BPM process. For processing the incoming data, I need one process instance for each "PROCESS_KEY" AND "DOC_TYPE". Therefore, I tried to put these two fields into one correlation as well as using two correlation. But always, each input file runs into the same process instance. Has anybody an idea for solving this problem´?

Here's an example, how it should work:

File 1:

leads to the following process structure:

Process instance 1: File 1, File 2

Process instance 2: File 3

Process instance 3: File 4

Help is (as always) highly appreciated.

Cheers,

Matthias

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

you should use one correlation and specify your elements "PROCESS_KEY" and "DOC_TYPE" in the correlation container. It should work then.

http://help.sap.com/saphelp_nw04/helpdata/en/a5/64373f7853494fe10000000a114084/frameset.htm

Regards

Patrick

Former Member
0 Kudos

Patrick,

thanks for your helpful answer. I had a little error with one field in my correlation, but now it works.

But I have another issue, that is driving me almost mad:

The process I'm implementing is similar to the demo process "BpmPatternCollectMessage". The process collects the messages in an infinite while loop until a commit message arrives for the current correlation. After this, the process sends an RFC to the SAP System.

For any reason, when the commit message arrives the process queue (XBQO$PE_WS...) goes to status u201CSYSFAILu201D with error message u201CNo active correlation for

message...u201D

The commit file definitely matches the correlation. In the Workflow log I can navigate to the workflow objects and the correlation is displayed as follows:

<?xml version="1.0" encoding="utf-8"?>

<CorrelationKey Version="001">

<DOCTYPE>MAT</DOCTYPE>

<PROCESSKEY>0000000090</PROCESSKEY>

</CorrelationKey>

The commit message contains:

<DOC_TYPE>MAT</DOC_TYPE>

<PROCESS_KEY>0000000090</PROCESS_KEY>

The only unusual thing is, that the correlation object exists twice with two different object id's.

If you have further ideas, pleas help.

Cheers,

Matthias

Former Member
0 Kudos

Ok, problem is solved. I had a little error in the commit file. So, the message interface didn't fit for the file and the correlation wasn't found. I need to work more carefully )

Thanks anyway,

Matthias

Answers (0)