Receiver determination error

[Former Member]

My scenarion is RFC->XI->RFC based communication. I have a RFC program which is sending the request from R/3 to the destination system(Non SAP system).

I am using the SAP XI3.0 SP12. I am testing the configuration in the Integration Directory(ID) using the "Test Configuration" functionality in 'Tools' menu of ID.I am getting an error at step 2: Received Determination. Here is the error I see:

Internal Error java.io.IOException

My scenario is RFC->XI->RFC based communication. I have a RFC program which is sending the request from R/3 to the destination system(Non SAP system).

I would appreciate your comments and suggested remedies for the error situation.

Thanks,

Raghu

[Former Member]

It can be mapping error. Please verify the same.

Also, make surethe SENDER IDENTITY is maintained in R/3. Use WE21 to do so.

Also, make sure you have assigned proper logical system and used the same while created an LS partner. Do the same in XI using IDX1 and maintain the recepient identity.

Hopefully this should resolve your issue. I got the same error and maintained the entry in R/3.

Everything works fine now.

Please post your findings.

Thanks,

Srini.

[Former Member]

Hi Raghu,

Sorry the post was bit irrelavent. It was intended for an another post.

Sorry for the confusion.

[Former Member]

That's OK Srinivas.

Do you have any clues for my error situation.

Thee process sholud trigger from R/3 by excuting the RFC(Z_REQUEST_RFC).The RFC destination given is a XI system amintained in SM59 as TCP/IP connection type.

But after executing the RFC no message is sent is sent out of R/3 resulting in a dump on the R3 side.When i reviewed the dump it is a CALL_FUNCTION_REMOTE_ERROR

Obviously, nothing is visible in the SXMB_MONI of XI

Any clues?

Thanks,

Raghu

[Former Member]

Raghu,

I think you have chosen the connection type to be "T".

Try to apply the connection type as "3"-R/3 Connection.

It will be visible in MONI only when the RFC adapter passes it to the central engine. Till then your only option will be RWB or AdapterFramework to monitor it.

Please verify the RFC destination you have created and make the connection type to 3 and try it once.

please let's know what happened

good luck,

Srini.

[Former Member]

Hi Srinvas,

Where are the connection types you specified maintained? Is it on the R/3 or XI side?

Raghu

[Former Member]

SM59, R/3.

If you also have set the SENDER/RECEIVER confi rfc destinations in XI, do check using Sm59.

Thanks,

Srini.

[Former Member]

Thanks Srini,

It is a useful information, though the problem is not solved.

It is set to connection type 3, Test connection works fine from XI side too.

When I run the Z_ Program on the R/3 side,it is resulting in a CALL_FUNCTION_REMOTE_ERROR by dump.

Any clues?

Raghu

[Former Member]

Hi Raghu,

How did you solved your reciever determination problem.I

am also getting the same problem.Plz help me out if you know something about this

Thanx in advance.

Rekha

[Former Member]

Raghu,

One quick question. Is the function module or the zcode you have designed in R/3 is enabled for remote call?

The error you are getting CALL_FUNCTION_REMOTE_ERROR is normally caused only when the function module is not set to be remotely enabled in the process type. Just check the attributes and make sure it is REMOTE ENABLED.

I tried simulating your scenario and used the BAPI

BAPI_ACC_DOCUMENT_POST for testing.

from the sender system, collected the data using the standard function module ACC_DOCUMENT_RECORD and created a Z Program for testing to pass the synchronous messages to the receiver.

in XI, checked IDX5--> RFC Monitor -->Program -> Execute and could see two XML messages for inbound and outbound for the function module.

1. Did you change the RFC adapter properties file

2. Did you initiate the RFC adapter to start while the transaction is executed.

3. I used the connection types T and L and used the RFC program ID in Sender system for communicating to RFC adapter.

Thanks,

Srini.

[Former Member]

Hi Srinivas,

The RFC is remote enbled.I have executed IDX5, but I couldn't see any XML messages in the adpter monitor.

1. Yes , I changed the RFC adpter.Please send me your e-mail id, I will mail you the screen shot.

2.Can you let me know how we check this?

3. I have used the connections types 'T' on the r3 side and connection type '3' R3 Connection on the XI side.

Thanks,

Raghu

[Former Member]

Hi,

My scenario is MQ --> XI --> File. Iam getting same error as in the first post(in the same thread only):

Internal Error java.io.IOException when testing config with "Test Configuration" functionality in 'Tools'

And in the adapter monitor for the inbound CC I can see this error:CC_Inbound_MQ_to_xi Sender channel. Details: MQJMS2005: failed to create MQQueueManager for '10.69.255.34:MQSIDV4'. Server port i am using is 1419. Any information on this would be appreciated.

Thanks

Indrasena

[Former Member]

Hi Indrasena,

Internal Error java.io.IOException when testing config with "Test Configuration" functionality in 'Tools'

I was also getting the same error for test tool in Integration directory.

The solution is

note 858049 - IOException in a Test Configuration Tool

Hope it helps.

Thanx

Rekha

[Former Member]

Thanks Rekha. It did help.

Thank you

Indrasena

[Former Member]

You should check the url of the Adapter engine on your XI Server.The error that you get is when you have invalid url.

Thanks

A

[Former Member]

Dear Ashish,

Thanks for the reply. It looks like a correct URL, placed in the Integration Directory in "Service Without Party".

It is like this:

https://staging.nameofthecompany.com/JetStream/500/Presentation/ASP/HRISIntegration/MsgDispatch.Asp

Do you see any thing wrong with this URL?

Secondly, when I run the "Test configuration" functionality wizard from Tools->Test Configuration, I see a error

Internal Error Java,io.IOException

This is a generic eroor. Is there a palce where I can see the details of this error, like may be a error log.

Does the "Test Configuration" generate any descriptive error logs any where?

Thanks for your reply.

Raghu