XI - Call Adapter Error - HTTP client. Code 402 reason ICM_HTTP_TIMEOUT

I am using HTTP adapter to post XML PO to vendor's site. We are having this problem with one of our vendor when PO's has more than 15 line items. XI server is getting error-"Call Adapter Error - HTTP client. Code 402 reason ICM_HTTP_TIMEOUT". Actually PO is posted good for the first time on vendor's site but XI is getting above error message and it keeps posting it again. Is there anyway to stop it otherthan manually stopping the XI message? Is there anyway to increase the wait time of the XI server to get the message.
Thanks in advance.
Mrudula Patel

I'm getting the same issue "500 TIMEOUT error" in runtime work bench-->IE--->Test Message. When i manually trigger the file.
The issue is basically from 01-01-2015 02:00 pm to 02-01-2015 01:am , File is picked from source ftp folder and places in archive but xml messages are not reflecting in SXMB_MONI.
Today suddenly after 01:00 am messages are successfully processing.
Please help on this issue. Many Thanks.

Similar Messages

HTTP client code 402 reason ICM_HTTP_TIMEOUT

Hi Experts,
My Scenario is RFC-XI-HTTP syncronous and was working fine for some period.
after that when am sending request to XI it is processinig successfully till technical touting and in call adapter step under response am finding error as <SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code>
             <SAP:P1>402</SAP:P1>
             <SAP:P2>ICM_HTTP_TIMEOUT</SAP:P2>
             <SAP:Stack>HTTP client code 402 reason ICM_HTTP_TIMEOUT</SAP:Stack>
             <SAP:Retry>N</SAP:Retry>
and i gone through relevent SAP notes and configured the parameters in ICM monotor and Visual admin for the same.
and still am getting the same error as mentioned in above.
Could you please any one help me out in this regard ?
Many thanks,
Siva

Hi Raj,
Thanks for your reply,
I already gone through the mentioned link nd followed the steps.
still am facing the same problem for this scenario. and some other scenarios of same type RFC XIHTTP are working fine.
and could you please let me know is it throughs the error that i mentioned in case when the Target system wont give response to XI ?
why because am finding the Time out error that mentioned under Response message.
Kindly help in this regard.
thanks
siva

Error in scenario "FILE to HTTP(with SSL)" - HTTP client code 110 reason.

Hi friends,
Our scenario is as follows:
We are trying to send XML file from our SAP-XI to external tool "COMMunix XC" (a multi-protocol EDI platform tool).
We have configured " FILE TO HTTP(with SSL)" scenario (trying to connect HTTPS/port)
1. We have created RFC destination of type G and refered the same RFC in Communication channel (Adapter type: HTTP)
2. We have send the SSL Server certificate to other party and ensure that they have imported at thier end.
3. We have included the certificates from other party in our SAP XI STRUST under SSL Client (Standard) node.
4. We have tried " CONNECTION TEST " in the RFC destination created in type G (in STEP 1) and it shows the GREEN TICK at bottom, no other message nor any error message
When we trigger the communication we recieve the error: HTTP client code 110 reason in SXMB_MONI.
Please let us know if we have missed out some step.
What does error message indicate,
Regards,
Rehan

Hi Rehan,
I see that the PROCTIMEOUT was already at a very high value.
Does this occur for messages of a particularly large size? If yes, you could increase the parameter
icm/HTTP/max_request_size_KB = 2097152
This would need to be done in the sender/receiver system as well as XI.
Otherwise you could try reproducing the issue and checking the dev_icm log in the work directory, or go to SMICM -> Goto -> Display trace file
check for errors like NIECONN_REFUSED or "no service for protocol HTTPS" which can often be related to this type of issue.
Kind regards,
Sarah

HTTP Receiver Adapter - HTTP client code 110 reason error when sending

Hi,
I am getting the following error when using the HTTP adapter as a receiver to perform an HTTP Post in a destination system :
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code>
<SAP:P1>110</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP client code 110 reason</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Does anyone know what causes this error and more importantly how to trace it ?
Cheers
Colin.

hi Colin,
Check in SMICM if your HTTP service is running. Also in RFC destination one of the parameter (SSL client Certificate) might be wrong which could also cause this problem.
Also check this thread:-
XI Error when upgraded to SP14 (Error Code 110) CLIENT_RECEIVE_FAILED
Have a look into this SAP Note - 897583
Regards.
Praveen

HTTP client code 405 reason ICM_HTTP_INTERNAL_ERROR

Hi Experts,
Getting the below error in the RWB could any one look at this and help me out.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlnsAP="_http://sap.com/xi/XI/Message/30" xmlnsOAP="_http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code>
<SAP1>405</SAP1>
<SAP2>ICM_HTTP_INTERNAL_ERROR</SAP2>
<SAP3 />
<SAP4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAPtack>HTTP client code 405 reason ICM_HTTP_INTERNAL_ERROR</SAPtack>
<SAP:Retry>N</SAP>
Thanks
Venkat Anil

Hi Venkat,
Just check eith your basis team had they restatred the j2ee engine proprely or not ,are all the nodes working fine in visual admin.
Regards

HTTP Client : Code 110 reason

hi,
when i try to send a IDOC to XI to HTTP Receiver.
The flag shows red in the SXMB_MONI and the error is HTTP Client : code 110 reason message.
I am using a HTTP adapter for a HTTPS url as a receiver.
If i test the xml from a WFETCH i get a response saying no cXML Sent but there is cXML that i am adding in the Header body.
I have not used HTTP Client.
Any tips.
Thanks,
Tirumal

Hi Tirumal,
you were going correct man ...
The 400 error that you are getting can be because of :
The verb used in the request is invalid.
The requested URL is invalid.
The requested header name is invalid.
The requested hostname is invalid.
The request contains an invalid carriage return and/or line feed as a terminator.
The request contains an invalid content length header or invalid entity chunk length.
The cumulative length of the headers in the request is longer than the maximum allowed.
The header field in the request is too long.
The request header is too long.
Check on these lines and see if your problem is solved.
Rgds
joel

HTTP client code 400 reason ICM_HTTP_CONNECTION_FAILED

Hi
when using an https receiver adapter in PI 7.11 I get the error message
"HTTP client code 400 reason ICM_HTTP_CONNECTION_FAILED".
The server I am trying to connect to is running and I have activated all services under sap -> xi in SICF.
The ICM log shows this:
WARNING => Connection request from (38/18489/0) to host: https, service: 80 failed (NIEHOST_UNKNOWN)
AP-T38, U18489, 001 ALE_K01, , 15:45:37, M0, W9,     , 1/0 [icxxconn.c 2222]
On the PI Integration Server the outbound queue (smq1) is empty.
However, the message seems to be sitting in the inbound tRFC queue (smq2)
Function Module: SXMS_ASYNC_EXEC
Queue Name: XBTO6___0002
Status Text: Transaction Recorded
I also get the error message in the inbound tRFC queue:
"XI Error ATTRIBUTE_CLIENT.PLAINHTTP_ADAPTER: Queue"
It does not help to chose "save LUW" on the erroneous message in the queue.
In the http receiver adapter I entered these values:
Addressing Type: URL Address
Target Host: https://biztalk.lm-gruppen.dk
Service Number: 443
Path: /******/BTSHTTPReceive.dll
What should I do to make it work?
Mikael

Hi,
In the http receiver adapter I entered these values:
Addressing Type: URL Address
Target Host: https://biztalk.lm-gruppen.dk
Service Number: 443
Path: /******/BTSHTTPReceive.dll
If you want to enable HTTPs, you should use HTTP to RFC destination using SM59 (for the RFC destination) and STRUST (for the SSL authentication). Also, do not specify the http:// or https:// parameter in your target host. The correct parameters should be:
Target Host: biztalk.lm-gruppen.dk
Service Number: 443
Path: /******/BTSHTTPReceive.dll
hope this helps,

Receiver XI adapter error :HTTP Status Code 200 during Reponse Parsing

Hi Exeprts,
My Scenario is mail to ABAP proxy , I have got the bellow error in moni while testing my secnario .
Please help me reslove this .
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">OK_BUT_NO_XI_MESSAGE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3>(See attachment HTMLError for details)</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>HTTP Status Code 200 Received But Error During Response Parsing: No XI Response Received XML element Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Regards
Upendra

Hi Mark ,
No error message in attachement . only it daisplay the following information
SAP Library
SAP Library contains the complete documentation for SAP NetWeaver Application Server Java. You can access it by choosing SAP NetWeaver.
      SAP NetWeaver Administrator
A powerful administration, configuration and monitoring tool, which bundles key administrative tasks to keep your SAP NetWeaver system landscape running. SAP NetWeaver Administrator can be used in a central or local scenario. Here you access the local NetWeaver Administrator.
    System Information
System information provides administrators with an overview of the system configuration and its state. It shows all of the system's instances and processes, their current state and important parameters (such as ports) that may be required for support cases, as well as the versions of the components installed.
      Services Registry
The Services Registry is a UDDI based registry that contains definitions of enterprise services and references to their metadata.
   User Management
The user management administration console provides administrators with the functions they need to manage users, groups, roles, and user-related data in the User Management Engine (UME). Users without administrator permissions can use it to change their user profile.
      UDDI Client
The UDDI client provides query and publishing functions for UDDI entities to any UDDI compliant registry.
   Web Services Navigator
Web Services Navigator is a tool that gives you a short overview of a specific Web service based on its WSDL, and enables you to test your Web service by creating and sending a client request to the real end point.
      Web Dynpro
Web Dynpro is a User Interface technology available within the SAP NetWeaver Developer Studio.
Various Web Dynpro tools provide administrators and application developers with performance measurement and application administration capabilities. The Web Dynpro runtime is already deployed.
Regards
Upendra

HTTP server code 500 reason Internal Server Error

HI,
I am getting following error in Call Adapter
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Internal Server Error</SAP:P2>
<SAP:P3>Internal Server Error</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP server code 500 reason Internal Server Error explanation Internal Server Error</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I have a Business system that is sending the material master data to a different Business System via XI. The message is received by XI correctly. XI correctly performs the transformation and identifies the message interface and selects correct receiver for the message. XI communicates with the receiving business system via the appropriate communication channel.
The message "fails" in the receiving system with the following error:
HTTP server code 500 reason Internal Server Exception explanation Error parsing of SOAP header.
The channel is using HTTP Adapter type, and i cross checked the communication channel details like Addressing type, target host, service number, path, user name, user password.......each and every detail is correct.
Please help me out to find the solution to the problem.
Points will be gladly awarded.
Edited by: Ashish Soni on Sep 24, 2008 9:02 PM

try sending the same XML message picking from moni and check whether you are getting same error or not?
if you get same error then check at web server for logs there you can find exact error.

HTTP server code 404 reason Not Found explanation Not Found

Hi all
I am facing this error "HTTP server code 404 reason Not Found explanation Not Found" during a asynchronous xml message sent to a buisiness service
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>404</SAP:P1>
<SAP:P2>Not Found</SAP:P2>
<SAP:P3>Not Found</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP server code 404 reason Not Found explanation Not Found</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
could you provide an explanation on this error.

Hi
Go through this
Error: 404 Not Found
Description: The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.
Possible Tips:- for HTTP_RESP_STATUS_CODE_NOT_OK 404
404 is an HTTP response code that indicates that the resource in question couldn't be found. Usually this is due to an incorrect URL, so it is better to cross check all URLs. Check pipeline URL in the SLD in the business system of the Integration Server For this go to SLD->Business System-><yourIntegrtaion Server>->Pipeline URL: It should be like this http://<host>:<port>/sap/xi/engine?type=entry Where host is the host name of the Integration Server and port is the HTTP(8xxx) port. To verify this in Integration Server you can do like this. Go to SXMB_ADM->Integration Engine Configuration->Choose Edit from Menu -> Change Global Configuration Data to switch to change mode. Then select System Landscape - Load Configuration. (This is not required always)
Check that the port really is the ICM HTTP Port and not the J2EE port i.e SMICM then menu GOTO --> SERVICES and check the port number for HTTP. It should be HTTP port
If the error is Page cannot be displayed, cannot find server in https configurations Check and correct the SSL configuration for the ABAP and the J2EE side of the system
If the error is because of integration server when using Proxy communications then check these. i.e SXMB_ADM->Integration Engine Configuration->Corresponding Integration Server enrty should be dest://<Http Integration server-Destination> Where < Http Integration server -Destination > is the RFC destination (SM59) of type HTTP connection (type H) to the Integration Server. In this case, host name, port, and path prefix are saved in the RFC destination.
**********Reward points if usefulll.**********

HTTP server code 500 reason Internal Server Error explanation Error during

Hi,
I am trying to connect to SAP TM (Tranportation Management) System using HTTP adapter using PI 7.0.The scenario is
ECC ->PI->SAP TM. I have configured HTTP adapter as the receiver with addressing type as HTTP Destination. I have created a RFC destination of type H pointing to SAP TM on PI. I have encountered the following error after executing the scenario.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Internal Server Error</SAP:P2>
<SAP:P3>Error during parsing of SOAP header</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP server code 500 reason Internal Server Error explanation Error during parsing of SOAP header</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks,
Kiran

Error during parsing of SOAP header
Can you mention what are the settings done in Receiver HTTP channel.....the request that you send to target is not in proper format.
One reason could be incorrect Content Type.....is it text/XML ?
Regards,
Abhishek.

PLAINHTTP_ADAPTER ATTRIBUTE_CLIENT HTTP client code 400 ICM_HTTP_CON_FAILED

Hi Experts,
Ssytem details:PI7.1,
While processing messages from source system to PI system. we are getting the below error :
PLAINHTTP_ADAPTER ATTRIBUTE_CLIENT HTTP client code 400 ICM_HTTP_CON_FAILED
The messages get stuck while processing from source system(abap stack) to PI and every time we need to restart the ICM service and then messages are flowing to the PI system successfully .
Additional screenshots are given below:
Please provide your valuable solutions
Regards
Ram

Hi Rafikul,
Let me know if time out parameter can be pinpointed issue .
icm/server_port_0 = PROT=HTTP,PORT=8000
Further traces of icm from source system are below ::
[Thr 140571804710688] *** WARNING => IcmMsgProcess: connection to WP 77 broken (rc=-8,nirc=-6)
[Thr 140571804710688] Wed Mar 5 16:09:27 2014
[Thr 140571804710688] *** WARNING => IcmMsgProcess: connection to WP 34 broken (rc=-8,nirc=-6)
[Thr 140571804710688] Wed Mar 5 17:42:33 2014
[Thr 140571804710688] *** WARNING => IcmMsgProcess: connection to WP 12 broken (rc=-8,nirc=-6)
[Thr 140571804710688] Wed Mar 5 19:43:48 2014
[Thr 140571804710688] *** WARNING => IcmMsgProcess: connection to WP 3 broken (rc=-8,nirc=-6)
[Thr 140571804710688] Wed Mar 5 19:54:37 2014
[Thr 140571804710688] *** WARNING => IcmMsgProcess: connection to WP 14 broken (rc=-8,nirc=-6)
[Thr 140571804710688] Wed Mar 5 20:05:22 2014
[Thr 140571804710688] *** WARNING => IcmMsgProcess: connection to WP 4 broken (rc=-8,nirc=-6)
[Thr 140571804710688] Wed Mar 5 20:06:01 2014
[Thr 140571804710688] *** WARNING => IcmMsgProcess: connection to WP 8 broken (rc=-8,nirc=-6)
[Thr 140571804710688] Wed Mar 5 20:16:55 2014
[Thr 140571804710688] *** WARNING => IcmMsgProcess: connection to WP 22 broken (rc=-8,nirc=-6)
[Thr 140571804710688] Wed Mar 5 20:36:43 2014
[Thr 140571804710688] *** WARNING => IcmMsgProcess: connection to WP 10 broken (rc=-8,nirc=-6)
[Thr 140571804710688] Wed Mar 5 21:45:29 2014
[Thr 140571804710688] *** WARNING => IcmMsgProcess: connection to WP 0 broken (rc=-8,nirc=-6)
[Thr 140571804710688] Thu Mar 6 02:48:42 2014
[Thr 140571804710688] *** WARNING => IcmMsgProcess: connection to WP 12 broken (rc=-8,nirc=-6)
[Thr 140571804710688] Thu Mar 6 03:19:56 2014
[Thr 140571804710688] *** WARNING => IcmMsgProcess: connection to WP 19 broken (rc=-8,nirc=-6)
[Thr 140571804710688] Thu Mar 6 04:20:56 2014
[Thr 140571804710688] *** WARNING => IcmMsgProcess: connection to WP 1 broken (rc=-8,nirc=-6)
[Thr 140571804710688] Thu Mar 6 05:33:57 2014
[Thr 140571804710688] *** WARNING => IcmMsgProcess: connection to WP 2 broken (rc=-8,nirc=-6)
[Thr 140571804710688] Thu Mar 6 06:28:58 2014
[Thr 140571804710688] *** WARNING => IcmMsgProcess: connection to WP 10 broken (rc=-8,nirc=-6)
[Thr 140571804710688] Thu Mar 6 06:46:25 2014
[Thr 140571804710688] *** WARNING => IcmMsgProcess: connection to WP 0 broken (rc=-8,nirc=-6)
[Thr 140571804710688] Thu Mar 6 06:46:31 2014
[Thr 140571804710688] *** WARNING => IcmMsgProcess: connection to WP 1 broken (rc=-8,nirc=-6)
Regards
Bharat

Simple HTTP Receiver - HTTP server code 405 reason Not Allowed explanation

Hi, I am using simple HTTP Receiver to receive the XML file from the below url http://www.bank-ua.com/export/currrate.xml
But receiving the below error in SXMB_MONI
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>405</SAP:P1>
<SAP:P2>Not Allowed</SAP:P2>
<SAP:P3><html> <head><title>405 Not Allowed</title></head> <body bgcolor="white"> <center><h1>405 Not Allowed</h1></center> <hr><center>nginx/1.4.1</center> </body> </html></SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>HTTP server code 405 reason Not Allowed explanation <html> <head><title>405 Not Allowed</title></head> <body bgcolor="white"> <center><h1>405 Not Allowed</h1></center> <hr><center>nginx/1.4.1</center> </body> </html></SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Initially the same URL was working could you advice what to change to make this working?
Thanks,
Dhill

Hi Senthil,
There is a way, you can expose the function module HTTP_GET as an rfc-enabled FM and use it to call the webservice. Here is a POC I made before:
Proof of Concept: An Alternative HTTP GET using a Remote-Enabled Version of the Function Module HTTP_GET
Another is to create a UDF that uses an HTTP Client class to call the webservice.
Regards,
Mark

Http server code 503 reason Service Unavailable explanation Service Unavail

Hi all
I am trying to send data to a HTTP SITE.
I am getting the following error.
Could somebody guide me how to solve this.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>Oxalate</SAP:Category>
<SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>
<SAP:P1>503</SAP:P1>
<SAP:P2>Service Unavailable</SAP:P2>
<SAP:P3>Service Unavailable</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Http server code 503 reason Service Unavailable explanation Service Unavailable</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thankyou

Same errors are comming up.
Could not do a RFC connection to website.

Http server code 401 reason Unauthorized explanation Unauthorized

Hello to you all,
I have a SRM-XI-SUS scenario and I try to connect to SUS with XI but I am facing the follwoing issue:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="<b>PLAINHTTP_ADAPTER</b>"><b>ATTRIBUTE_SERVER</b></SAP:Code>
<SAP:P1>401</SAP:P1>
<SAP:P2>Unauthorized</SAP:P2>
<SAP:P3>Unauthorized</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack><b>Http server code 401 reason Unauthorized explanation Unauthorized</b></SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can someone guide me towards a solution?
Kind regards,
Kamran

I am not intimate with the SRM-SUS integration via XI, but based on the business scenario configuration guide (https://service.sap.com/~sapidb/011000358700002897402004E/ServiceProcurementNEW.pdf) it seems that communication between SRM and SUS via XI takes place via proxies. Assuming that's what you're trying to do, to communicate to SUS via proxies, you would need to use the adapter type (XI). The communication is still technically over HTTP, but using the XI messaging protocol.
The use of an sm59 destination is optional. The XI type communication channel allows addressing types of "URL Addressing" or "HTTP Destination". If you choose the latter, you would need a sm59 destination of type H and then refer to it from the channel.
Try using a XI type receiver channel instead. If you run into additional problems, check the "XI Settings" section of the guide above.
Regards,
Jin

XI - Call Adapter Error - HTTP client. Code 402 reason ICM_HTTP_TIMEOUT

Similar Messages

Maybe you are looking for