R/3 - (RFC) -> XI - (File) -> Legacy System

[Former Member]

Hello there,

I followed a document to setup SAP XI to/from external systems.

I did a setup that execute bapi QIRF_SEND_CATALOG_DATA from R/3. Then, it uses RFC to transfer data to XI, and store as a file @ Legacy system.

When I executed the BAPI with the RFC destination as created on R3, it failed.

Besides, when I check the message monitoring at XI Runtime Benchmark, it shows an error as :

ErrorCode:ICF-NF-http-... HTTP 403 Forbidden.

I believe I activated ICF engine service.

My question is "do I have setup Single Sign-on" for XI or is that optional?

I followed the instruction call "How to Configure SAP XI to use the standard SAP communication APIs (idoc, bapi, rfc) from external systems".

Any comment is appreciated.

Thank you very much.

TBLuong.

[Former Member]

Hello all,

I really appreciate your help.

However, I followed some instructions and still not able to solve the problem.

The error now I get is:

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

- <!-- Call Adapter

-->

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

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>

<SAP:P1>401</SAP:P1>

<SAP:P2>Unauthorized</SAP:P2>

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>&lt;!DOCTYPE HTML PUBLIC &quot;-//W3C//DTD HTML 4.0 Transitional//EN&quot;&gt; &lt;html&gt; &lt;head&gt; &lt;title&gt;Error Report&lt;/title&gt; &lt;style&gt; td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;} A:link A:visited A:active &lt;/style&gt; &lt;/head&gt; &lt;body marginwidth=&quot;0&quot; marginheight=&quot;0&quot; leftmargin=&quot;0&quot; topmargin=&quot;0&quot; rightmargin=&quot;0&quot;&gt; &lt;table width=&quot;100%&quot; cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; border=&quot;0&quot; align=&quot;left&quot; height=&quot;75&quot;&gt; &lt;tr bgcolor=&quot;#FFFFFF&quot;&gt; &lt;td align=&quot;left&quot; colspan=&quot;2&quot; height=&quot;48&quot;&gt;&lt;font face=&quot;Arial, Verdana, Helvetica&quot; size=&quot;4&quot; color=&quot;#666666&quot;&gt;&lt;b&gt;&amp;nbsp;&amp;nbsp;401 &amp;nbsp Unauthorized&lt;/b&gt;&lt;/font&gt;&lt;/td&gt; &lt;/tr&gt; &lt;tr bgcolor=&quot;#3F73A3&quot;&gt; &lt;td height=&quot;23&quot; width=&quot;84&quot;&gt;&lt;img width=1 height=1 border=0 alt=&quot;&quot;&gt;&lt;/td&gt; &lt;td height=&quot;23&quot;&gt;&lt;img width=1 height=1 border=0 alt=&quot;&quot;&gt;&lt;/td&gt; &lt;td align=&quot;right&quot; height=&quot;23&quot;&gt;&lt;font face=&quot;Arial, Verdana, Helvetica&quot; size=&quot;2&quot; color=&quot;#FFFFFF&quot;&gt;&lt;b&gt;SAP J2EE Engine/6.40&amp;nbsp;&lt;/b&gt;&lt;/font&gt;&lt;/td&gt; &lt;/tr&gt; &lt;tr bgcolor=&quot;#9DCDFD&quot;&gt; &lt;td height=&quot;4&quot; colspan=&quot;3&quot;&gt;&lt;img width=1 height=1 border=0 alt=&quot;&quot;&gt;&lt;/td&gt; &lt;/tr&gt; &lt;/table&gt; &lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt; &lt;p&gt;&lt;font face=&quot;Arial, Verdana, Helvetica&quot; size=&quot;3&quot; color=&quot;#000000&quot;&gt;&lt;b&gt;&amp;nbsp;&amp;nbsp;Internal server error. An error log with ID [00123FE5030C00560000000800000A5000040B5ABE8AB74F] is created. For more information contact your system administrator.&lt;/b&gt;&lt;/font&gt;&lt;/p&gt; &lt;p&gt;&lt;font face=&quot;Arial, Verdana, Helvetica&quot; size=&quot;2&quot; color=&quot;#000000&quot;&gt;&lt;table&gt;&lt;tr&gt;&lt;td valign=&quot;top&quot;&gt;&lt;b&gt;&amp;nbsp;Details:&lt;/b&gt;&lt;/td&gt;&lt;td valign=&quot;top&quot;&gt;&lt;PRE&gt;No details available&lt;/PRE&gt;&lt;/font&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;&lt;/font&gt;&lt;/p&gt; &lt;/body&gt; &lt;/html&gt;</SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>HTTP response contains status code 401 with the description Unauthorized XML element Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>

<SAP:Retry>N</SAP:Retry>

</SAP:Error>

Again, I follows an scenario to execute an bapi at R3 using RFC to IS, then put as a file at Legacy system.

On R3, I did some setups:

- created an RFC type TCP/IP with gateway hostname and id pointing to R3, and a reg Prog ID named CC_RFC2XI.

- call Trans: SXMB_ADM to setup Intg. Eng. Config with the role as Appl System & Intg Server point to http://<host>:<port>/sap/xi/engine?type=entry

On the Intg Dir:

- created comm. channel from R3 as SAP_2_EXT_RFC as sender with the hostname as R3 host and gateways, and also Prog ID named CC_RFC2XI.

- created comm. channel for Legacy system as SAP_2_EXT_FILE to stored file as .txt file at legacy system.

- created Reciever Determination with condition as BAPI execution condition

- created Interface Determination for interbound interface.

- created Sender Agreement.

- created Receiver Agreement.

- I activated /sap/xi/engine from Trans SICF and also insert user login and password.

I tested the connection for SM59 from R3 and it's ok. However, after execute the BAPI with the destination RFC as created, I got the error message above.

Please tell me what else I am supposed to do.

Again, I really thank you so much for all your time and help.

tbluong.

[Former Member]

Hello there,

Now, I get a new problem from Message Workbench -> Message Monitoring after trying from a few suggestions:

- Returning snchronous error notification to calling application: Received HTTP response code 500.

- Transmitting the message using connection http://ngxisvr:8004/sap/xi/engine?type=entry failed, due to: Received HTTP response code 500.

- The message status set to FAIL

- Returning to application exception: Received HTTP response code 500.

Any suggest is appreciated.

Thank you very much.

tbluong.

[Former Member]

Hello there,

Following are the errors description:

- Received XI system error:

ErrorCode: NO_RECEIVE_CASE_BE

Error Text: No receiver could be determine.

- Returning synchronous error notification to calling application XIserver: NO_RECEIVER_CASE_BE.

- Transmitting the message using connection: http://hostname:80xx/sap/xi/engine?type=entry failed, due to XIServer: NO_RECEIVER_CASE_BE.

My case is sending data from R/3 to XI (RFC) to Legacy system (File).

I setup TCP/IP connection at R/3 with Registered program ID matched with RFC registered ID at sender communication channel and the gateway point to R/3 server.

I am still confused that how the R/3 recognizes the XI server.

Thank you so much for all your help.

TbLuong.

[Former Member]

Hi,

Are you running SP12 or earlier?

If you are getting hhtp 500 as a error then its an Internal server error.

http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html

Regards,

Anirban.

[Former Member]

Hi,

Is 8004 Correct port for you?

<i>HTTP 500 is an error caused at the Web Server side. Any http connection happens in 4 steps:

1) Obtain the IP address from the URL - provied by DNS

2) Open Ip Socket for that IP

3) Use this socket to write data

4) Receive data stream back from the server.

</i>

Please see this thread

Try chaning your Pipeline url to,

http://<hostname>:8000/sap/xi/engine?type=entry

Regards,

Anirban.

[Former Member]

Hi,

Is the issue solved. Was just curious to know if it was really the url or port issue.

Take care,

Anirban.

[Former Member]

Hello there,

When I check for the error message from message monitoring, it says:

XIServer

RCVR_DETERMINATION: NO_RECEIVER_CASE_BE

Would anyone tell me what it means.

Thanks.

tbluong.

[Former Member]

Check your Receiver Agreement and the whole receiver determination.

KK

[Former Member]

Hi Thaiba,

<i>RCVR_DETERMINATION: NO_RECEIVER_CASE_BE</i>

Have you configured your legacy system as Business Service? Have you attached you MI and Interface mapping in the Interface determination and configured your communication channel properly in receiver agreement?

Cheers,

Rashmi