cancel
Showing results for 
Search instead for 
Did you mean: 

Permanent error in BPE inbound processing

Former Member
0 Kudos

Hi all,

My Scenario is IDOC to File which involves BPM , While executing the same it ended up with an error "Permanent error in BPE inbound processing " in SWWL and its was struck in the queue smq2 as well.When remove the messages from the SWWL and after running the IDOC regenerated manually,It worked fine since then.

What could be the reason for this error.Did any one face simillar error? Any SAP Notes on this?

Kindly let me know.

thanks,

Anil.

Accepted Solutions (1)

Accepted Solutions (1)

prateek
Active Contributor
0 Kudos

Let me explain you this in simple terms

When you tried to run the scenario earlier, there were some earlier incomplete BPM instances waiting for some messages. These instances could be in error states while testing earlier scenarios. The file you run in current scenario could have satisfied condition for some other erroneous open instance. And hence your scenario was not running. Once you delete the instances usinf SWWL, the open instances gets deleted. The new files coming in would create a fresh new instance without any harm from other instances. Thats why it started working. Since then, there must not be any erroneous instance and therefore you haven't faced such error since then.

I hope it was simple to understand

Regards,

Prateek

Answers (3)

Answers (3)

Former Member
0 Kudos

Yes,

When you use BPM , in SMQ2, It will give same error message(Permanent error in BPE inbound processing) for any sort of error or exception . When control is in the BPM ( means after processing of first recieve step and before last send step) ,if some error comes in your CC configuration, it will be shown as "Permanent error in BPE inbound processing" in your SMQ2.

Regards,

Reyaz

Former Member
0 Kudos

Hi Anil,

Note 1126656 - BPE-TS: Permanent errors in the BPE inbound processing

Note 1082099 - BPE-TS: Transactional behavior

Regards

Sunil.

JoelTrinidade
Active Contributor
0 Kudos

Hi,

There is no exact no exact root cause analysis done for this but then i could give you some case where in which this error occurred.

"This behavior is when we place the files in the respective folders both the files are picked up by the file adapter. Process instance is generated for BPM. First receive step is encountered and the file is received by it. But due to the wait step the second receive step is not open and hence the second file cannot be delivered to it. Unlike the first case, in this case as the buffering is deactivated the file is not buffered and hence the inbound processing of BPM fails for the second receive step."

Check out

sap note no. 1126656 where exactly why this error comes up is mentioned

Regards

joel

Former Member
0 Kudos

I faced the similar issue in PI 7.0 ,

are you on same environment?,you can search the notes for that

remedy is send idoc one by one .