Archiving - SAPHTTP not using Fully qualified server

[michael_fallenbchel]

Hi experts,

when I try to archive a document (for example for Purchase order (ME23N) -> Store business document), I have a problem with SAPHTTP:

I get popup to confirm that system tries to open program SAPHTTP with command line

/H/XYZ sapgwXX 1651651 IDX=2

In this case, the server is not fully qualified (XYZ).

When I test the SAPHTTP-RFC in SM59, server is fully qualified (XYZ.sap.com).

Instance profile seems to be correct:

SAPLOCALHOSTFULL is fully qualified

SAPLOCALHOST not

icm/host_name_full is fully qualified.

What am I doing wrong?

Thanks for you help

Michael

[Reagan]

Hello

Could you provide the screen shot of the RFC settings please ?

Regards

RB

[michael_fallenbchel]

Hi Benjamin,

sure, pls see attached.

s

Regards

Michael

[Reagan]

Hello Michael

According to the RFC configuration the program SAPHHTP is started from the front-end work station.

So the saphttp.exe will be started from here C:\Program Files (x86)\SAP\FrontEnd\SAPgui

It looks like the connection from the front-end work station is resolved as XYZ and not to the FQDN (XYZ.sap.com)

Do you have any entries for this server in the hosts file ?

Regards

RB

[michael_fallenbchel]

My host file is empty, yes.

It will work if I make an entry here, already tested.

The question is - why does SAP use FQDN in SM59, but not when trying to archive?

Is there any entry I have to set, any profile parameter,...?

[Reagan]

The question is - why does SAP use FQDN in SM59, but not when trying to archive?

I am not sure how you concluded that SAP is using FQDN in SM59.

Did you notice any information in the dev_rfc trace files ?

If the FQDN parameters are set correctly then the problem could be with the DNS

Regards

RB

[Former Member]

Hi,

As it is to store some doc.

(for example for Purchase order (ME23N) -> Store business document),

Please check the settings of OAC0  then go in the repository which you are trying to use to save doc and see if you have specified the fully qualified name in there in the server place.

Do the document get saved in content server?

Thanks

RishI abrol

[michael_fallenbchel]

How do I know?

See the Security Popup in the Connection test in SM59:

And here the security popup when trying to archive in ME23N:

As you can see - fully qualified in SM59, but not in ME23N.

Error in the trace file is ERROR       hostname 'XXXX'' unknown - sure, it's not fully qualified 🙂

So...why not using the fully qualified server in ME23N? What I have to customize?

Thanks

[michael_fallenbchel]

Hi,

see screenshot of OAC0 and our repository

Server name is fully qualified.

I don't think this is the problem - as the error occurs with my SAP server name (esapXXX.xyz.net) which is not resolved when using ME23N (here I only see esapXXX).

[Former Member]

Hi,

Please go to SAP GUI ==>>Options==Security==>>Security settings==>>make status is disable.

another way is login to your sap==>>click button customize & local layout (Alt +F12)==>> Security==>>Security settings==>>make status is disable

[Former Member]

Hi,

I tried the first part of the rfc SAPHTTP and that is getting affected with the gui settings in sap. So if i change the name in the gui it change the command in the rfc.

Second thing that i would suggest to activate the trace and run ME23N and see the trace where its picking hostname.

Thanks

Rishi Abrol

[michael_fallenbchel]

Why should I do this? Then I won't have the security popup...ok, but I want to have it in this case to see what SAP wants to do.

Without the popup I won't know that SM59 wants to do different things than ME23N...

[Former Member]

This popup is due to only sap gui security setting. please disable this & then try.

[michael_fallenbchel]

Okay, have tried - nothing changed (except that I don't have the popup anymore).

[michael_fallenbchel]

I debugged the whole process now..

Problem is function RFC_PING

When I execute directly, it uses FQDN, when archiving not.

I traced it also, can't find out where the name is picked..damn it!