no payload found in Req msg mappng step in MONI

[Former Member]

i did , file to proxy scenario, in messge mapping test, i am able to find the target xml document. But in sxmb_moni, the pay load for Request Messgae Mapping pipe line step is not found.

what would be the problem,,

can any body tell me?

Thanks,,,

Kumar

[Former Member]

hi

this is error i am getting in the Recever R/3 System.

ie Application error.

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

- <!-- Call Inbound Proxy

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">

<SAP:Category>Application</SAP:Category>

<SAP:Code area="ABAP">APPLICATION_ERROR</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="http://xyz.com/f2ps">f2psfltmt</SAP:ApplicationFaultMessage>

<SAP:Stack>Application has thrown an exception</SAP:Stack>

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

</SAP:Error>

Thanks,

kumar

[Former Member]

hey all....

i got the msg proceessed successful. but the data is not updated in the reciever R/3 z table. but i got the fault msg back to the sxmb_moni of the R/3.

In mapping test, i got the target xml pay load as per mapping.

But in sxmb_moni of PI this payload is not appended the pipeline step Request Message Mapping . and is having simply as fallows.....

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

<ns0:f2ps_p_mt xmlns:ns0="http://xyz.com/f2ps" />

but in mapping test i got the target xml as fallows...

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

<ns0:f2ps_p_mt xmlns:ns0="http://xyz.com/f2ps">

<record>

<empcode>234</empcode>

<ename>wer</ename>

<sal>456</sal>

<dept>wqer</dept>

</record>

<record>

<empcode>567</empcode>

<ename>wer</ename>

<sal>890</sal>

<dept>wqer</dept>

</record>

</ns0:f2ps_p_mt>

why is it not appended in moni?

can any body ......?

thanks...

Kumar

[Former Member]

Hi,

Can u paste the error message thrown in the proxy,Get it from SXMB_MONI of u r backend System.

Better goto -> sproxy of u r backend system.Click on the method and press test (Testing of u r proxy)

a default xml would appear -> cut and pate u r source xml

and run , for better clarity try to put break point in u r proxy and see y u r table not getting updated>

If u wanna run with the scenario put external break pojnt to u r proxy and test.u can see whether data flow is happening from outbound intrface

rgds

srini

[Former Member]

hey, all...

i found msg processing successfull, but in recever R/3 side data is not updated in the z table, and i am getting fault masg back in R/3 moni. ok..

in maapint test , i get the target xml data/pay load.

But in sxmb_moni of PI , this payload is not appending at Request Message Mapping pipe line step. its giving simply as fallows....

[Former Member]

Hi,

Configure the Integration Engine According to this Blog and then you wil come to see all the messages in MONI

REgards

Seshagiri

[former_member192295]

Hi,

Mapping test is internal testing between two interfaces, SXMB_MONI is complete transaction log check proxy statements once again and activate it

[former_member182455]

hi kumar,

When a source message reaches the Integration server, it performs 6 steps before the message reaches the destination. The steps are:

1) Receiver Determination: This steps determines the system that participates in the exchange of the message.

2) Interface Detremination: For each receiver determine which interface will should receieve the message.

3) Message Split: If more than one receievers are found, Xi will instantiate new message for each receiver.

4) Message Mapping: Mapping to transform the source message to destination message format.

5) Technical Routing: Bind a specific destination and protocol to the message.

6) Call outbound Adapter: Send the transformed message to the adapter or a proxy.

One can examine these steps in Runtime Workbench using the Transaction: SXMB_MONI.

and also chech this link

https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/u/34500 [original link is broken] [original link is broken]

regards

srinivas

[Jitendra_Jeswan]

Check the following things;

1) check if you have used the correct Interface Mapping in Interface Determination in ID

2) Check if the Interface Mapping has the correct Message Mapping assigned to it.

3) Check if all the objects are Activated !

Revert after checking all this.