file to abap proxy error : HTTP connection not found

[Former Member]

Hi,

I have run into a bit of an issue with file to proxy scenario...

On ECC side..

I created rfc dest of tye http pointing to PI system

LCRSAPRFC and SAPSLDAPI are also maintained..

configured business system as application system.

with sproxy transaction.. I get all the swc that have in PI..

when I run the scenario.. I get the below error...

have also maintained details in SLDAPICUST in ECC

On Pi side using XI recv channe.. have given HTTP addressing and the name of dest in ECC...

Am i missing out on something?

SAP:Category>XIServer</SAP:Category>

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

<SAP:P1>HPIDCLNT125</SAP:P1>

<SAP:P2>PID</SAP:P2>

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:Stack>HTTP destination HPIDCLNT125 missing (system , transaction SM59)</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

[former_member568822 · Accepted solution]

Hi,

The HTTP DEST in SM59 should be create in you PI server not ECC cause you connection is from PI to ECC.

[Former Member]

Hi,

HTTP Connection created in ECC is used for retrieving the SWC components of IR....but it cannot be used by PI for psoting the data to Proxy...

so in this need to provide the needed details at XI adapter level ...

chk the below blog which can give u an idea...

/people/siva.maranani/blog/2005/04/03/abap-server-proxies

Also for the above error check below threads

HTH

Rajesh

Edited by: Rajesh on Apr 15, 2010 12:04 PM

[Former Member]

I have done the same entries..

[aashish_sinha]

Hi Ibrahim,

check out in SXMB_ADM if it is pointing to correct system.

its global entry should be like dest:// HPIDCLNT125 ..

I hope this will help. For a check also ... check in Visual Admin-> JCo Abap -> Both RFC destinations for PI is maintained.

I guess you only missing global entry in correct format. Also check if in SLDAPICUST -> PI system is primary.

Regards

Aashish Sinha

[Former Member]

Yeah, It is pointing to the crrect destination..

One doubt ashish.. I checked rz70 in the eccc system... it points to solman...

could that be the reason?.

[aashish_sinha]

Hi Ibrahim,

In RZ70, it should point to the same system not solman.. its a wrong entry.

2nd thing is that in sxmb_adm -> the url should start with dest://.. not with http. and if your http connection of ABAP is XYZ created in sm59. it should look like dest://XYZ.

check sldcheck and let me know if u see any red line. as u mentioned earlier, there is no red, means you successfully pointed to SLD of XI.

One more extra check need to be done. Just for precaution.

After editing in sxmb_adm -> dest://XYZ just click on check button to verify if its running. If u getting any error there means thr is some problem.

Regards

Aashish Sinha

[Former Member]

Hi Aashish,

The destinations look fine...

Actually XI was not in the landscape initially.. it has been added recently..

So on this r3 system it corresponds to solman...

how can i correct this?/

[prateek]

HPIDCLNT125 should be present in PID pointing to ECC.

Regards,

Prateek

[Former Member]

The rfc destination is just on ECC right??

so in the path prefix i add /sap/xi etc

do I have to have one on PI as well??

type H?

The only other rfc dest of type http is integration_directoy_hmi

is this right?

[prateek]

Your scenario is Abap proxy at receiver end. What do you use in XI receiver channel? Have you mentioned any RFC destination there? If yes, that RFC destination must be present in PI not ECC.

Regards,

Prateek

[Former Member]

Hi,

Create type 'H' RFC in SM59 of your PI system, Give 'target Host' & 'port' values. 'Path Prefix' value will be '/sap/XI/engine/?type=entry'. Give a user ID and password and check if the connection test is working or not. Use this rfc in your reciever channel of PI.

Thanks

[Former Member]

I did the URL addressing in XI rcv channel...

I have maintained the piappl user in sldapicust in ecc (MD1).. the error now changes to as below....

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

<SAP:P1>MD1</SAP:P1>

<SAP:P2>300</SAP:P2>

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:Stack>Error when reading the ID of the business system from the SLD for system MD1 and client 300</SAP:Stack>

I also did a sldcheck in ECC, it is able to retrieve the busniess system name correctly..but sez connection sld does not work..

Ne ideas guys???

Regards,

Ibrahim