unable to send exact data to the target(sap-ztable)

[S0004343680]

hi,

all

i am unable to send exact data to sap-ztable,in sxmb_moni -->payload i am getting exact data,from 3rd party

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

- <ns:MT_INTF_CNG_DISP xmlns:ns="http://CompressedNaturalGas.com">

- <row>

<CNG_STATION_ID>11</CNG_STATION_ID>

<DISPENSER_ID>ABCDE11</DISPENSER_ID>

<LEFTARMS>L</LEFTARMS>

<RIGHTARMS>R</RIGHTARMS>

<STATUS>A</STATUS>

</row>

</ns:MT_INTF_CNG_DISP>

when i am sending it to r/3..

i am able to send

CNG_STATION_ID

DISPENSER_ID

STATUS=A is going into LEFTARMS

my mapping is correct in IR AND even in RWT -->adapter engine i am getting the data perfectly

can any one suggest me what might be wrong.

thanx

kayan

[S0004343680]

hi,

all

i got the solution,

u have to define the maximum & minimum value of the field in the <b>details</b> of datatype(IR). then it will get the exact data.

thanks for support ,

kalyan

[prateek]

Check the payload in sxmb_moni of the receiver R3 system.

Also at receiver, are u using idoc / rfc / proxy?

Regards,

Prateek

[S0004343680]

hi

prateek

i checked my payload i am getting the data perfectly,

i an using rfc at my receiver.

why the data is getting into r/3.

the data is not getting exactly.

is the any way to debbug in xi how the data is getting send to the receiver

thanx

kalyan

[prateek]

If in the sxmb_moni of receiver R3 u r getting correct data, then the problem is with ur RFC code. Try debugging it.

Regards,

Prateek

[Former Member]

In the receiver RFC adapter check the number of connections. Once our problem was solved when we increased the number of connections.

also check if message is getting stuck in SM58

Regards

Rajeev

[Former Member]

otherwise change the comm channel and activate again

have u made any change in the RFC and reimported it. better refresh the cache from Integration builder home page-->Administration for the repository and directory

[S0004343680]

hi

rajeev

can u let me what is the use number of connections in the rfc adapter.

thanx

kalyan