ABAP Client Proxy not sending the data to XI ?

[Former Member]

Hi Guys,

My scenario is proxy - soap asynchronus process.

when i execute the report on the R/3 side, i am able to see message in sxmb_moni in R/3 with the proper sender service but i could not see the receiver side.

There is proper HTTP connection defined and it works properly with the proxy- soap synchronus scenario for another interface.

The data is not coming into XI only for the asynchronus scenrio. I could not find any messages in XI under sxmb_moni or in RWB.

any help would be really appreciated

Thanks,

srini

[Former Member · Accepted solution]

Hi,

As I understand, the message has not reached XI itself. If that is right, what is the status of message in SXMB_MONI of R3? Have you checked the possibility that it might have been stuck in queue there?

Thanks,

Bhavish

[Former Member · Accepted solution]

Hi Bhavesh,

ya you are right, the message has not reached xi itself. How to check whether the message has been stuck in the queue and how to release it from the queue.

Thanks,

srini

[Former Member · Accepted solution]

Hi ,

Login to your ERP system and check t-code SM58.

If you cant see in SM58 check SXI_MONITOR and check the message status.

Regards,

Sumit

[former_member189387]

Hi srinivas,

You are getting the following

<i><Trace level="1" type="T">no interface found</Trace></i>

Please check your configuration whether receiver determination and interface determination for proper sender service ?

Have u created the proper Business syetm in SLD. ?

Did u use that business system as Sender Business system ?

are u getting succes flag ?

Regards.,

V.Rangarajan

[Former Member]

Hi there,

Don't know how your report looks like. Did you try to add commit work at client proxy side??

Cheers,

emile

[Former Member]

Hi Emile,

In this program there is a Bapi calls which performs the activity. I did not find any commit work. I am able to see the xml out of the proxy and in the trace i am seeing the following error

Trace level="1" type="T">Get definition of external pipeline = SENDER</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />

<Trace level="1" type="T">Get definition of internal pipeline = SAP_SENDER</Trace>

<Trace level="1" type="T">Queue name : XBTS0007</Trace>

<Trace level="1" type="T">Generated prefixed queue name = XBTS0007</Trace>

<Trace level="1" type="T">Schedule message in qRFC environment</Trace>

<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>

<Trace level="1" type="T">----

---

</Trace>

<Trace level="1" type="T">Going to persist message</Trace>

<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>

<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>

<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>

<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>

<Trace level="1" type="T">----

---

</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />

- <!-- ************************************

-->

<Trace level="1" type="T">--start sender interface action determination</Trace>

<Trace level="1" type="T">select interface ClearingHousePaymentOrderRequest_Out*</Trace>

<Trace level="1" type="T">select interface namespace http://sap.com/xi/APPL/SE/Global</Trace>;

<Trace level="1" type="T">no interface found</Trace>

</SAP:Trace>

</SOAP:Header>

- <SOAP:Body>

- <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">

- <SAP:Payload xlink:href="cid:payload-DC67984E6E4856F19E9B000C29ED9442@sap.com">

<SAP:Name>MainDocument</SAP:Name>

<SAP:Description />

<SAP:Type>Application</SAP:Type>

</SAP:Payload>

</SAP:Manifest>

</SOAP:Body>

</SOAP:Envelope>

[Former Member]

Srini,

You need to call commit work after calling Bapi.

Also check if messages are stuck in qRFC. Tranaction code : SM58.

Nilesh

[Former Member]

Hello,

Is this a new installation? If yes just check in

SXMB_ADM->Integration Engine Configuration->Specific Configuration

for the below

RUNTIME ENGINE_TYPE <b>HUB</b> <b>UNDEFINED</b>

RUNTIME LOGGING <b>1 0</b>

RUNTIME LOGGING_PROPAGATION <b>1 0</b>

RUNTIME TRACE_LEVEL <b>1 1</b>

Regards,

[Former Member]

Hi Srihari,

I have all those settings in sxmb_adm.

Thanks,

srini