Showing results for 
Search instead for 
Did you mean: 

Permanent error in BPE inbound processing

Former Member
0 Kudos

Hi all,

I have the following problem concerning a BPM.

A message sent from an external R3 system (by proxy) to the integration process does not enter in it.

The queue is in SYSFAIL with the following error :"Permanent error in BPE inbound processing"

Beasides, on LUW data - "Result Message Delivery simulation" says: "Process definition WS99900018 contains no receive steps for message......"

On "Display trace" I could read the following:

"No active correlations for message ..... "

The BPM has 2 correlations, 4 receive steps and one send step (to R3 system via proxy). The first receive step (Start process) activates the first correlation which is used by two receiver steps in a fork.

One of the two branches of the fork step contains an other send step that activates the other correlation which is used from the unique receive step.

There are not failed workitems, and at runtime the correlations are created well

Could someone help me?

Thanks in advance,


Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

This kind of problem occurs when there is a corelation problem in your Integration Process.

First of all check that whether your BPM is activated properly using the transaction SXI_CACHE.

double click on integration process then check the status code for your BPM. If its 99 then double click and check for the error message.

Gaurav Jain

Answers (3)

Answers (3)

Former Member
0 Kudos


Do complete cache refresh........SXI_CACHE



Active Contributor
0 Kudos


It seems that this error due to correlation in your BPM, check you have used correlation properly in your BPM.

Also check status code of your BPM in cache table i.e. SXI_CACHE transaction. If it is not 0 then there is some problem in your BPM.

Now try to activate your BPM in SXI_CACHE there it will show you actual error in your BPM.

Also do complete cache refresha and full CPA cache refesh. Sometimes it solve the issue.

If further clarification required then let us know.



Reward points if helpful.

Former Member
0 Kudos


I had a similar kind of error..

Just do a complete cache refresh.. using sxi_cache transaction.

Also delete the exsisting work items created by BPM usinfg SWWL transaction.

This should help.