Where did my payload go???

[Former Member]

Dear experts,

I have a very strange thing happening to me, at least as far as I can tell...

I have set up a file to rfc/proxy scenario. I'm sending some master data to a system via proxy (inbound).

The problem I am experiencing is as follows:

When I track the message (in SXMB_MONI), I can see the payload of the message from "inbound message (central)" up till "technical routing".

After this, so in "Call Adapter" and "Response" the payload is gone.

XI tells me the message is sent out successfuly, however nothing is getting through, because the payload is gone missing.

Any suggestions?

<i>Will awards points for good answers</i>

Regards.

[Former Member]

Hi,

You can try one more thing.

You can check your LOGGING parameter value under SXMB_ADM transaction.

This parameter enbles you to log every pipeline steps/services.

go to Transaction on PI system: SXMB_ADM -> then click to specific configuration -> and add or update LOGGING parameter there and value for this parameter should be 1.

Let us know if you face any issue in this.

Divyesh

[Former Member]

I had this problem and I was using XSLT mapping and I had to deal with prefixes for namespace so my payload was like this

<?xml version="1.0" encoding = "UTF-8"?>

<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:ns="http://www.xxxx.com/scp">

<xsl:template match="/">

<ns:Mt_ECC_and_BI_File1>

<xsl:for-each select="/ns:Mt_xxx_File/Records">....

.....

....

those ns prefixes were causing the problem, there was no error, I could even see the messages in sxmb_moni in ECC system where my proxy was defined but when I debug proxy there was no data

I changed the prefixes to ns0 and it worked so best way to find the problem is using the graphical mapping and find out what kind of prefix your ABAP proxy is expecting and fix your XSLT or Java mapping accordingly.

Hikmet

Edited by: Hikmet Tenis on Jun 22, 2010 12:40 AM

[stefan_grube]

In an asynchronous scenario, there is no response, so the response payload is empty.

Regards

Stefan

[Former Member]

> In an asynchronous scenario, there is no response, so

> the response payload is empty.

>

> Regards

> Stefan

I'm talking about Respone node in "Display XML message versions". Not about a response message.

Furthermore, this would not explain the adapter call with no payload.

Cheers.

[stefan_grube]

Be assured that the payload is not gone.

If there is no call of your proxy/RFC, the error must have a different reason.

Regards

Stefan

[Former Member]

> Be assured that the payload is not gone.

> If there is no call of your proxy/RFC, the error must

> have a different reason.

>

> Regards

> Stefan

how can I check this?

[henrique_pinto]

> I'm talking about Respone node in "Display XML

> message versions". Not about a response message.

>

> Furthermore, this would not explain the adapter call

> with no payload.

>

> Cheers.

And that is exactly what this node is all about.

If there is no technical response to your message, it should be empty.

To check the exact paylod that went through the adapter, check Message Monitoring on RWB for the Adapter Engine. Select your message, click on Details and go to payload tab.

Regards,

Henrique.