RFC sender problem

[Former Member]

Hi

The scenario is RFC>XI>File(text)

In the rfc i create a table with 2 records fields : matnr & kunnr

If the table contain at 100 or 150 records it is all okey , the file is created.

The problem begin if the i need to send 3000 records ( 3.8 Mb ) then the file is not created i not see nothing in XI but i see in transaction SM58 the next problem/message/status :

<b>Commit fault: no message</b>

I don't understand what not correct ,

Where is the problem :

in R3 (timeout parameter ) or

in XI ( memory parameter ).

[gopalkrishna_baliga]

Hi George,

Did you get any solution for this? I am also facing this issue.

I will be greatefull to you if you can send me the details.

You can also mail me at: gopalbaliga2003@yahoo.co.in

Hope to get some positive response from you.

Thanks

Gopal

[thomas_jork]

Hello

Has anybody found a solution to this problem.

We have the same error, also with a very large

message. And we just can see the 'Commit fault: No Message'

entry in SM58. No Entry in SXMB_Moni.

Regards

Thomas

[Former Member]

Yes i try , you cannot debug T connections.

[Former Member]

Yes, you are right, I forgot that the connection versus XI is type "T".

You said that you can't see nothing in the Communication Channel monitor, maybe you can see something from the Log Viewer in the Visual Administrator of J2EE ?

Sandro

[Former Member]

<b>you cannot debug T connections in sm58.</b>

the problems is when the function send the table to xi :

CALL FUNCTION 'Y_DAX_RFC_VARIETY_DATA'

IN BACKGROUND TASK

DESTINATION 'PXI400_RFC'

TABLES

O_VARIETY_DATA = dxb_variety.

COMMIT WORK.

and i see in sm58

Caller Function module Target system Date Time Status text

QA_GEORGES Y_DAX_RFC_VARIETY_DATA PXI400_RFC 04.02.2007 06:49:04 Commit fault: no message

[Former Member]

George, have you tried this (selecting the specifc LUW in error):

<img src="http://www.salveitalia.com/DebugtRFC.jpg"/>

<br>

<br>

Sandro

[Former Member]

If i send 100 records the scenario work ok.

[Former Member]

If the problem is at tRFC level between R/3 and XI the problem is at ABAP stack level: if some problem occurs you can debug from SM58, (exaclty with the function Debug from the menu)

Sandro

[Former Member]

No

i not see nothing in st22 and sm21 in XI.

Only in sm58 i see status : <i>"Commit fault: no message"</i>

the problem is tunnning , but where ?

[Former Member]

Very strage that you don't see any error in XI:

1) have you tried to re-process the tRFC from SM58 ?

2) Have you double checked if you are pointing to the right RFC destination ?

3) Have you tested the RFC destination logon from SM59 ?

Sandro

[Former Member]

hi

i not see nothing in xi , not in the sxmb_moni and not errors in the channel .

i see only the error in r3 , in transaction SM58 !! The data is not sender to Xi.

what is the reason or problem , i don't now.

[Former Member]

In this case is the ABAP stack of XI that is not capable to accept a message of such dimension, at the moment. You should have a DUMP in XI (transaction ST22 and SM21) that tell will you something more.

Sandro

[Former Member]

It's a problem of parameters/tuning.

We have to understand if the message fail during the communication with Adapter Engine or inside the Integration Engine.

Do you see the message in SXMB_MONI ?

In with step of the pipeline you see the message in error ? (CALL ADAPTER?)

If so, we have to adjust some parameters in AE, that looks not capable of messages of that dimension, at the moment.

These notes may help:

<a href="https://websmp101.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=872508&_NLANG=E">Note 872508 - XI 3.0 AF: BufferOverflowException when sending large msgs</a>

<a href="https://websmp101.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=821267&_NLANG=E">Note 821267 - FAQ: XI 3.0 / PI 7.0 File Adapter</a>

Sandro