Idoc to File Scenario

[Former Member]

Hi,

I have configured Idoc-to-Idoc Scenario and one Idoc-to-File Scenario for same Message type MATMAS from SAP r/3 system.

Idoc to Idoc is working perfectly, BUt Idoc-to-XI is throwing this error.

Just check if someone can analyze from the error message.

-

-

---

td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;} A:link A:visited A:active

-

-

---

Tell me if more details are required.

Thanks and Regards,

Vijay Raheja

[bhavesh_kantilal · Accepted solution]

Vijay,

As you have an exisiting scenario which is working for Idoc to idoc, are you postingt the same idoc from the same System with the same Busss System? if yes, you should have Multiple receivers in the receievr determination and interface determiantion.

Can you give more details on the Idoc to File you have created.

Also take a look at this blog for the HTTP errors in XI,

/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi

Regards,

Bhavesh

[former_member529475]

Hi Vijay

Check your j2ee admin whether it is up or not

cheers

Vasudeva Rao. V

[former_member192798]

Hi Vijay,

Check if J2EE/Adapter engine is up and running. Do a complete CPA cache refresh. In general 503 means service not available.

Ensure that all the services are activated, SICF->sap->xi->engine.

Hope this helps.

Regards.

Praveen

[Former Member]

Hi Praveen,

I guess you are on the track.

I checked for service /default_host/sap/xi/-->engine

Service is Active,But in logon data nothing has been mentioned there.

I tried both scenarios: Ido-to-File and FIle-to_File. In both the cases it is throwing same error at receving end. In file to file, It is able to poll from FTP location i gave. and file is getting picked and deleted, But it is unable to write and that location and that location has write access also.

More inputs from your end is required.

Thanks and Regards,

Vijay Raheja

[former_member192798]

Hi Vijay,

Are you maintaining the Client, Userid, Password, and Language information in SICF transaction -> sap/xi/engine ? If so double click on service and check whether you have entered correct information.

This kind of error is already mentioned in one of the threads. Anyway check the following:-

1. Check this- SAP note- 821026,

2. Delete the Adapter Engine cache in transaction SXI_CACHE

3. Check XIAPPLUSER is having this Role -SAP_XI_APPL_SERV_USER

4. Check the Exchange Profile and transaction SU01, try to reset the password -for XIISUSER etc Restart the J2EE Engine to activate changes in the Exchange Profile After doing this, you can restart the message

I hope this provides you a solution.

Regards.

Praveen

[Former Member]

HI Vinay,

If your file is being picked up.

Can you check in Adapter monitoring as well in ABAP Monitoring what is the error ?

I am taking about file->file.

Thanks,

TUhin

[Former Member]

HI Praveen

As i told in previous reply,

<b>Service is Active, But in logon data nothing has been mentioned there</b>

What should i maintain in logon details, I mean which user.

Thanks

Vijay Raheja

[Former Member]

Hi,

Just if this gives an overview on problem...I tried opening what is given in SLD->Business system->Integration Srevre->Pipeline URL

http://hostname:8001/sap/xi/engine?type=entry

- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

<SOAP:Header />

- <SOAP:Body>

- <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

<faultcode>SOAP:Client</faultcode>

<faultstring>Empty HTTP request received</faultstring>

<faultactor>http://sap.com/xi/XI/Message/30</faultactor>

- <detail>

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

<SAP:Category>XIProtocol</SAP:Category>

<SAP:Code area="MESSAGE">EMPTY_HTTP_REQUEST_RECEIVED</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Empty HTTP query received; message processing not possible</SAP:Stack>

</SAP:Error>

</detail>

</SOAP:Fault>

</SOAP:Body>

</SOAP:Envelope>

Thanks

Vijay Raheja

[former_member192798]

Hi Vijaym

Just cross check whether you have done the following steps:-

SLD-

1) Create a Product/Software Component

2) Technical System pointing to R/3 system

3) Business System for the above technical system

In the Repository

1) Import the Software component created in the sld

2) Create a namespace,

3) import the idoc and then create sender data type/message type etc and mapping

4) Mapping Rules is depends on the requirement

In the Directory

1) Create a Scenario /import the business system

2) Create Receiver/Interface determination

3) Create communication channels for sender and receiver

4) Sender Agreeement and Receiver Agreement.

Then the file adapter configuration is depend on the input file format.

Also you need to have Logical destionation created in the XI , and the IDX1 entry

In R/3 Port, Partner profiles etc should be created

Have a look into this document~

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38...

In addition do the following in XI:

1. SM 59 - Create RFC destination pointing to R3.

2. IDX1 - Create a port for R3

3. IDX2 - Import IDOC metadata.

Hope this provides you a solution.

Regards.

Praveen