XI Adapter LOOP_IN_MESSAGE_ROUTING (Inbound service interface PI->ERP)

[Former Member]

Hello,

my scenario:

PI is sending some data via XI Adapter to ERP (SAP ECC 6.0).

In PI SXMB_MONI shows us LOOP_IN_MESSAGE_ROUTING.

Some points:

- Proxy is generated and activated in ERP

- ERP is type of LOC (application system)

- Corresponding Integ. Server of ERP is our specific PI

- ERP HTTP port is running (SMICM->Services)

- XI Adapter is using messag protocol XI3.0

- XI Adapter refers to an HTTP RFC destination

- PI HTTP RFC destination to ERP uses /sap/xi/engine?type=entry as path prefix

- testing the PI HTTP RFC responses with: Empty HTTP request received (as suggested)

- calling ERPserver:HTTPport/sap/xi/engine?type=entry in local web browser results in: EMPTY_HTTP_REQUEST_RECEIVED (as suggested)

So why our message is send back from ERP to the sender PI integration engine and fails with LOOP_IN_MESSAGE_ROUTING?

Thanks in advance,

André

[marksmyth]

Hi

What is the message flow in the scenario? For example, ECC client 100 -> PI -> ECC client 200

Regards

Mark

[Former Member]

Hi Mark,

the message flow is:

File Server -> File Sender Adapter -> PI -> Xi Receiver Adapter -> ECC Client 300

Best regards,

André

[stefan_grube]

> PI is sending some data via XI Adapter to ERP (SAP ECC 6.0).

> In PI SXMB_MONI shows us LOOP_IN_MESSAGE_ROUTING.

This message occurs when the receiver of the message is the same PI.

So I assume that in receiver channel you have applied the host and port of PI system instead of ERP system.

[Former Member]

Hello Stefan,

Honestly, the receiver HTTP RFC connection that is used in the receiver XI adapter is ponting to the ERP, not to the same PI system. (with path prefix /sap/xi/engine?type=entry)

Is it possible that the ERP is sending the request back to PI because of the linked integration server in ERP? (ERP = LOC / Application Server; Corresponding Integ. Server = dest://HTTP_RFC_to_PI)

Many thanks,

André

[stefan_grube]

I think it is more interesting, where the PI message comes from, not where it should go to.

When you look into the sxmb_moni, at what pipeline step does the error appear?

[Former Member]

Hi,

error occours after calling the XI Adapter in CENTRAL pipeline:

HTTP-client: closing... External error header received Error exception return from pipeline processing! CENTRAL</SAP:P2>

<SAP:P3>XI</SAP:P3>

<SAP:P4 />

<SAP:AdditionalText />

<SAP:Stack> Schleife im Nachrichtenfluss entdeckt: System is.00.sappi1a, Pipeline CENTRAL mit Inbound-Adapter XI bereits durchlaufen (siehe HopList-Header) </SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

Many thanks,

André

Edited by: André Schillack on Dec 6, 2010 10:56 AM

[marksmyth]

Hello André

- Corresponding Integ. Server of ERP is our specific PI

Exactly how is this configured? It should be dest://. See Configuring the Role of the Business System

Also, check if you have specified the correct client in the XI adapter.

Regards

Mark

[Former Member]

Hello Mark,

many thanks for your response.

As shown in the linked document we are ponting from ERP to the related integration server with dest://.

Also the user of thr HTTP RFC has all needed authorizations in the PI system(role SAP_XI_APPL_SERV_USER).

The HTTP destination from ERP to PI itself is configures as described here.

The XI adapter also points to the correct ERP client.

Best regards,

André

Edited by: André Schillack on Dec 5, 2010 8:40 PM

[Former Member]

Hi,

also the engine service (SICF) is activated in ERP.

Any suggestions?

Thanks in advance,

André