RFC receiver adapter issue - ECC side we are seeing blank data for the RFC

[Former Member]

Hi All,

We are using Receiver RFC adapter to call a custom RFC (Synchronous call). It was working fine, but recently RFC was modified (They added new fields). We re-imported the RFC into ESR and also modified the mapping to reflect the new RFC strucuture. Now when we execute the RFC, at the ECC side no data is beeing seen. On the PI side we see data in sxmb_moni. It looks fine. However we don't see anydata in ECC. We did full cache refresh but it did not help.

Please let me know if anyone has any thoughts on this issue.

Thanks

-Pradeep

[Former Member]

Hi All,

Encountering the same error and did what was explained above: restarting, refresh cache, re-import, ... but no luck for the moment.

Any other idea?

How did you resolve those problems?

THANKS!

Thomas

[Former Member]

Hi Pradeep,

I exactly have the same error, Can you let me know what did was the solution for this.

Rgds,

Mithun

[Former Member]

Issue can be resolved by trying out following methods (It works for me)

1) Import the new RFC into ESR

2) Inactivate and activate back the communication channel at integration builder

3) Using runtime workbench Stop and start the comm channel

[Former Member]

I tried all but still no luck.

A strange behaviour is that when I use the RWB > Integration Server > Test Message to send a message to the pipeline, the RFC can receive the data.

But when I configure a Soap to RFC scenario, the RFC cannot receive the import parameters.

I checked the sxi_monitor, the XML are identical in both testing.

[Former Member]

Hi Tit Tsang Chong,

I exactly have the same error, Can you let me know what did was the solution for this.

Rgds,

Mithun

[Former Member]

I enabled the the RFC adapter trace in PI. It appears like adapter is not sending the structure and tabled that are populated. IT is sending only 230 bytes. Any clue why would rfc adapter drop the tables and structures??

FUNCTION Z_FI_AA_BAPI_ASSET_CHANGE

handle = 2

parameter = <null>

parameter = <null>

tables = <null>

>>>> [2] <unknown> EXT <ac: 6> >>> FLUSH (READ) (88578752)

Send RFCHEADER [2]: 01/BIG/IEEE/SPACE-U2/52494850

Send UNICODE-RFCHEADER [2]: cp:4102/ce:IGNORE/et:6/cs:2/rc:0x00000023

UUID: send_rfcuuid B6D708F0-B946-11E0-BC35-EEB4AC138154

UUID: RfcCallNew send the uuid to the partner:B6D708F0-B946-11E0-BC35-EEB4AC138154

>>>> [2] <unknown> EXT <ac: 7> >>> WRITE (88578752)

000000 | 01010008 01020105 04010002 01010103 |................

000010 | 00040000 020B0103 0106000B 04010002 |................

000020 | 01060200 00002301 06000700 1A003100 |......#.......1.

000030 | 37003200 2E003100 39002E00 31003200 |7.2...1.9...1.2.

000040 | 39002E00 38003400 07001100 02004500 |9...8.4.......E.

000050 | 11001200 06003600 34003200 12001300 |......6.4.2.....

000060 | 08003700 30003000 20001300 08001800 |..7.0.0. .......

000070 | 73006100 70007000 69002D00 64006500 |s.a.p.p.i.-.d.e.

000080 | 76002D00 64003100 08000600 28007300 |v.-.d.1.....(.s.

000090 | 61007000 72006400 62002D00 64006500 |a.p.r.d.b.-.d.e.

0000a0 | 76002D00 64003000 5F004400 52003300 |v.-.d.0._.D.R.3.

0000b0 | 5F003000 30000605 140010B6 D708F0B9 |_.0.0...........

0000c0 | 4611E0BC 35EEB4AC 13815405 14050200 |F...5.....T.....

0000d0 | 00050200 0B000600 36003400 32000B01 |........6.4.2...

0000e0 | 02003200 5A005F00 46004900 5F004100 |..2.Z._.F.I._.A.

0000f0 | 41005F00 42004100 50004900 5F004100 |A._.B.A.P.I._.A.

000100 | 53005300 45005400 5F004300 48004100 |S.S.E.T._.C.H.A.

000110 | 4E004700 45010203 37000003 37051400 |N.G.E...7...7...

000120 | 10B6D708 F0B94611 E0BC35EE B4AC1381 |......F...5.....

000130 | 54051401 3100E62A 54482A03 00E60000 |T...1..TH.....

000140 | 00000000 00000000 00000000 00000000 |................

000150 | 00000000 00000000 00000000 00000000 |................

000160 | 00000000 00000000 00000000 00000000 |................

000170 | 00000000 00000000 00000000 00000000 |................

000180 | 00000000 00000000 00000000 00000000 |................

000190 | 00000000 00000000 00000000 00000000 |................

0001a0 | 00000000 00000000 00000000 73617070 |............sapp

0001b0 | 692D6465 762D6431 5F445049 5F313839 |i-dev-d1_DPI_189

0001c0 | 34303530 00000000 00000000 63303432 |4050........c042

0001d0 | 35313733 62393435 31316530 38373562 |5173b94511e0875b

0001e0 | 30303030 30303163 65366132 00000000 |0000001ce6a2....

0001f0 | 02C04251 73B94511 E0875B00 00001CE6 |..BQs.E...[.....

000200 | A2B6D708 F0B94611 E0BC35EE B4AC1381 |......F...5.....

000210 | 54000000 01000000 002A5448 2A0131FF |T........TH.1.

000220 | FF0000FF FF000000 00000000 00000000 |................

>> CPIC native call CMSEND [2] convid: 88578752 14:23:39,159

<< CPIC native call CMSEND [2] convid: 88578752 rc: 0 14:23:39,159

[Former Member]

Re: RFC receiver adapter issue - ECC side we are seeing blank data for the RFC

[Former Member]

Hi, I have the same issue here. Do you have any solutions?

[Former Member]

Hi All,

Thanks a lot for responding to my query. As suggested i deactivated and activated. the comm channel and the result is same. we don't see any data in ECC side. Please let me know if there any other pointers. Also can you please suggest how to enable RFC trace in SAP PI. I followed the steps suggested sap.help.com but it is not tracing any details. We are using PI 7.11

Thanks

-Pradeep

[baskar_gopalakrishnan2]

You are saying SXMB_MONI shows successful message. That means PI sends to ECC as expected. I would recommend to make some dummy change in RFC comm channel and reactivate it. Then restart it. See that helps.

[Former Member]

As said above, try a dummy change, reactivate, and then stop&start channel in runtime.

[Former Member]

Hi,

Try to stop and start the RFC receiver channel and re execute hte same and check it out..

HTH

Rajesh

[naveen_chichili]

HI,

CHeck in your Receiver RFC channel if the message is successfull or failure?

Regards,

Naveen