Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
Showing results for 
Search instead for 
Did you mean: 
Former Member
0 Kudos
While working on Solman7.2 configuration, I faced an error exception CX_FQDN with Business Server Page (BSP), as it was looking for fully qualified hostname URL.

Tcodes like solman_setup or solman_workcenter were routing to URL with FQHN, but while using tcode sm_crm, it was going to URL without FQHN.

Error screenshot :

Analysis and Solution

Check for below parameters at SAP and OS level, if any of it has not set properly then maintain it.

SAPLOCALHOSTFULL = <FullyQualifiedHostname>
icm/host_name_full = <FullyQualifiedHostname>

Check/maintain host file entries at OS level (Unix : /etc/hosts & Windows : Windows\System32\drivers\etc\hosts )
<IP>     <Fully Qualified Hostname>      <Hostname>

Check hostname parameter at Unix level -
#hostname             -> It should retrun hostname
#hostname –fqd     -> It should retrun FQHN (hostname.domain.ext)

The ICM sets the FQHN using the following hierarchy.

1. The parameter SAPLOCALHOSTFULL in the SAP profile (recommended for high availability configurations) has the highest priority. If it is set in a profile file, the ICM uses this value as the FQHN.
2. If the parameter is not set, icm/host_name_full is analyzed.
3. If this parameter is not set either, the ICM uses the FQHN of the operating system. For this reason, check the settings of the hosts file at the operating system level.

The parameter SAPLOCALHOST is not fully qualified and is not used by ICM for the services.
SAP recommends that you set either SAPLOCALHOSTFULL (for HA configurations) or icm/host_name_full.

In my case everything was set perfectly but still sm_crm tcode was giving error with exception CX_FQDN, solution for this is as below,

1. Go to SE16
2. Display table HTTPURLLOC
3. There should be one or more entries. HOST field needs to be adjusted using FQDN instead of containing only the hostname.

After making changes, tcode sm_crm was routing to FQHN url as required.
Reference :

SAP notes -
- FQHN determination in ICM
654982 - URL requirements due to Internet standards
1936501 - Transaction SOAMANAGER does not work
805344 - Function of automatic generation of URLs in BW ABAP Web Runtime (3.X)
2048519 - Profile parameters for SAP Solution Manager 7.2

1 Comment
Labels in this area