Http server code 401 reason Unauthorized explanation Unauthorized

[Former Member]

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" ?>

- <!-- Call Adapter

-->

- <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

[Former Member · Accepted solution]

Hi -

>>><SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_SERVER</SAP:Code>

What type of channel are you using as the receiver channel to communicate from XI to SUS? As far as I know, the plain HTTP adapter (type HTTP) would not be used. If it's proxy communication, it should be type "XI". Assuming it's proxy, the adapter type should be 'XI' and path value in the CC should be '/sap/xi/engine/?type=receiver' (without quotes).

You need to make sure that the service /sap/xi/engine in SUS is active in txn SICF. You should also make sure that a valid user exists in SUS (e.g. XIAPPLUSER) with the proper role. If not, create it - you can look at XIAPPLUSER in XI to guide you.

Regards,

Jin

[Former Member · Accepted solution]

Jin Thanks for your reply.

If I cant use HTTP adapter, what kind of adapter can I use to communicate with SUS?

Do I also need a RFC Destination from XI to SUS? if so, what kind of RFC Destination?

The SRM and SUS are both installed on 1 client (client 400).

I made a XIAPPLUSER on that client.

Is there anything else I should do, which I forgot?

Regards,

Kamran

[Former Member · Accepted solution]

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

[Former Member · Accepted solution]

Jin,

Thanks, I followed your instruction and it seems to work now. We have to test further, but it looks fine now.

Regards,

Kamran

[Former Member]

Hey

refer to followin

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

thanx

ahmad