Correlation Problem

[Former Member]

Hi,

We configured a scenario with 4 receive steps with correlation. The scenario works if we use some constant values in correlation. However, when we use the xpath, it gets stuck in queue.

We understand that the problem could be due to some open correlation instances on a particular field. Is there any specific tcode/report to delete/unlock such correlation instances Or even to monitor it? We used SWWL to delete the work items but its not specific to correlation.

Thanks,

Prateek

[former_member537867 · Accepted solution]

Hi Prateek,

Refer to the help in Note 1082099

The inbound processing triggers error if the correlation evaluation shows that a message should be delivered to a process instance that has the status "error". Since delivery to process instances that contain errors is not permitted, the queue is stopped.

Use the simulation of the message delivery in the detail view of the relevant queue LUW to determine the relevant process instance for the affected message and use transaction SXMB_MONI_BPE "Continue Process Following Error" (or transaction SWF_XI_SWPR) to continue. If you cannot continue the process instance, check whether you can logically delete the instance. In this case, use the method that is described in Note 807906 to logically delete a process instance.

Check whether your system contains other process instances that have errors in order to detect similar problems. Use transaction SXMB_MONI_BPE "Continue Process Following Error" or transaction SWF_XI_SWPR.

Use the report RSWF_CRL_MAINTAIN to check all of the correlation instances in question or the relevant process instances that you can reach using "Display Work Item" to see whether they provide the required receive step.

Messages that cannot be delivered because no correlation instance can be found may lead to the error that is mentioned here. Check whether the causes that are outlined in Note 1094028 affect your case.

Also basically inbound processing triggers error if the system can locate a correlation instance for a message but cannot locate an active receive step for the message. However, an active receive step is required in accordance with the delivery mode "Without Buffering" (transaction SWF_INB_CONF).

Check the help in Note 1040614.

Check whether the relevant process instance may have terminated due to a system crash (for example, runtime error) and whether the process instance can continue so that it can reach a suitable receive step. Use the simulation of the message delivery in the detail view of the relevant queue LUW to determine the relevant process instance for the affected message. If required, use transaction SXMB_MONI_BPE "Continue Process After System Crash" (or transaction SWF_XI_SWPC) to continue the process. If you cannot continue the process instance, check whether you can logically delete the instance. In this case, use the method that is described in Note 807906 to logically delete a process instance.

Check whether your system contains other terminated process instances in order to detect similar problems. Use transaction SXMB_MONI_BPE "Continue Process After System Crash" or transaction SWF_XI_SWPC.

Regards,

Vinod.

[Former Member]

hi,

Just have a look at SAP Notes 903139.

Regards

Mamta

[Former Member]

Hi

I just want to say tht block wont hamper's the perfomance nor alter the process . it just enhances the monitoring of the BPM.

It will provide the feature as data passing from each n every step .

so you can monitor better i think so ....

Thank's

Chetan Ahuja.

[prateek]

Thanks Chetan, however we don't find enough utilization of block except for the error handling part. And it would complicate the Original correlation related issue. As I said earlier, it is working right now with Constants as correlation.

Thanks,

Prateek

[Former Member]

Hi

For monitoring the BPM , transitive property must be used i.e . block .

you can try in SXMB_MONI_BPE there various options of checking the log .

After executing the continous process following Errorr , goto options then LOG data u can check there .

or RFC monitor in the same you can debug LUW .

hope this helps .

Regard's

Chetan Ahuja

[prateek]

Chetan,

Can u elaborate on this please. We don't require block as such.

For monitoring the BPM , transitive property must be used i.e . block .

Carlos/Vinod,

This report seems promising, ll update the thread soon.

Thanks,

Prateek

[dharamveer_gaur2]

hi prateek

same problem faced by me in N:1 mapping.

then i checked one property Create New Transaction(provide detail workflow monitoring),after that i checked it in SXMB_MONI. there was problem in workflow step.

then i changed and now working fine.

[prateek]

We are not using any Block step. So there is no such option for us.

Thanks,

Prateek

[Former Member]

Hi Prateek,

With the report RSWF_CRL_MAINTAIN you can check active correlations.

Regards,

Carlos

[prateek]

The notes seemed helpful but couldn't solve anything

The mentioned report displays the instances. But the question is how to delete these instances.

Thanks,

Prateek

[prateek]

SWWL internally deletes the correlation instances also. Nothing additional functionality is required. Our problem was with eariler correlation instances few days back.

Thanks,

Prateek