cancel
Showing results for 
Search instead for 
Did you mean: 

Inbound ABAP Proxy posting messages to wrong pipeline

Former Member
0 Kudos

Hi there,

I have a simple scenario in which a third party system sends and receives a flatfile to/from R/3. I have implemented this scenario using an inbound and an outbound ABAP proxy on the SAP side.

The outbound (from a SAP perspective) part is working fine, however, the inbound scenario is not working properly.

I can see the incoming messages flowing into the SAP receiver system (using trx SXMB_MONI on the R/3 system), these have status successful processed. However, <b>the column pipeline</b> has the value <b>SENDER</b> which is not correct as these messages are coming into SAP so I'd expect to see <b>RECEIVER</b> as pipeline value. As a result of this the implemented execute_asynchronous method is never triggered.

Why is the inbound proxy putting messages on the SENDER instead of the <b>RECEIVER</b> pipeline? What would be the reason for this behavior?

Thanks for your feedback

Cheers,

Rob

Message was edited by: Roberto Viana

Accepted Solutions (0)

Answers (2)

Answers (2)

stefan_grube
Active Contributor
0 Kudos

Let see, if I have understood this correctly.

You have three SAP Systems and you have ABAP proxy on sender and receiver side?

In the local pipeline of the sending system, the pipeline entry should be SENDER, in the XI CENTRAL and in the receiving system RECEIVER.

When the pipeline entry is wrong, you might have the wrong URL-path prefix.

In XI 3.0 you can use the path prefix

/sap/xi/engine?type=entry

for addressing XI and application systems.

If your application system is based on WebAS 6.20 you have to use

/sap/xi/engine?type=receiver

for the application system, but this entry works as well for WebAS6.40 application systems (for compatibility reasons).

Check your settings of the receiver channels according to this.

Regards

Stefan

Former Member
0 Kudos

Stefan,

Thanks for your answer.

Just before reading your reply, we just found out that this indeed was the cause of the problem.

In XI we had /sap/xi/engine?type=entry in the HTTP dest. pointing to the app. server. This should be replaced by /sap/xi/engine?type=receiver as we are running under a WEBAS 6.20 system.

Cheers,

Roberto

Message was edited by: Roberto Viana

stefan_grube
Active Contributor
0 Kudos

The documentation will be updated with SP15, so the correct path prefixes will be mentioned at the place, where it should be

best regards

Stefan

Former Member
0 Kudos

I still need some help here, please send me any ideas!

Thanks,

Roberto.