---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management
Release :
- yokohama
ft:locale :
- en-US
ft:publication_title :
- Yokohama IT Operations Management
ft:clusterId :
- itom
bundleId :
- itom
workflow :
- Technology
---
# SAP products
# SAP products discovery {#ariaid-title1}
* Release version: Yokohama
*
* Updated December 16, 2025
*
*  13 minutes to read
ITOM Visibility can discover SAP applications, SAP HANA Database, and SAP HANA DB Catalog. Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.
## Request new or enhanced Patterns on the ServiceNow® Store {#sap-discovery__id_btt_g3g_tzb}
Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/application/06a71b1367e4130051c9027e2685ef1e/1.6.0?referer=/store/search?listingtype=allintegrations%253Bancillary_app%253Bcertified_apps%253Bcontent%253Bindustry_solution%253Boem%253Butility%253Btemplate&q=Patterns&sl=sh) to view all the available updates and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/r/store-release-notes/sn-store-release-notes.html).{#sap-discovery__p_d21_nfg_h1c}
To learn about the SAP components and their versions that you can discover, refer to [Detailed information on products discovered by ITOM Visibility](https://servicenow-prod.fluidtopics.net/AB0jKyDtjf78iS3uAPUKpg "Discovery and Service Mapping can discover a wide range of operating systems and applications.").
## Prerequisites {#sap-discovery__section_msw_rsc_qrb}
Verify that the applications are up to date
: Discovery and Service Mapping Patterns
: Visibility Content
: CMDB CI Class Models
Verify the configuration of the credentials
:
* (If hosted on a UNIX server) On the ServiceNow AI Platform, configure [applicative credentials](https://www.servicenow.com/docs/access?context=applicative-creds&version=yokohama&pubname=yokohama-platform-security&ft:locale=en-US) and [SSH credentials](https://www.servicenow.com/docs/access?context=r_SSHCredentialsForm&version=yokohama&pubname=yokohama-platform-security&ft:locale=en-US). The SSH credentials are used to create connections from SAP Central Instance (CI) to other applications and devices. In addition, provide the user elevated rights to be able to run commands requiring a privileged user: [Service Mapping commands requiring a privileged user](https://servicenow-prod.fluidtopics.net/KmX~uDsV3RoqnUbrW~2SFA "Service Mapping uses commands requiring elevated rights to discover and map Unix-based hosts in your organization. In addition to configuring necessary credentials, configure servers in your organization to allow Service Mapping to run these commands with elevated rights.").
* (If hosted on a Windows server) On the ServiceNow AI Platform, configure [Windows credentials](https://www.servicenow.com/docs/access?context=r_WindowsCredentialsForm&version=yokohama&pubname=yokohama-platform-security&ft:locale=en-US) to create connections from SAP CI to other applications and devices.
* (Optional) For discovering using the WinRM protocol, see [Configure WinRM trusted hosts on MID Server](https://www.servicenow.com/docs/access?context=enable-winRM-MID-servers&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US).
* (Optional for top-down discovery by Service Mapping) Provide a user with permissions to run SOAP on RFC read table function.
* (Optional for top-down discovery by Service Mapping) If your organization deploys SAP Digital Business Services using web services and you want to map all connected services, perform the following actions:
* Configure applicative credentials for a user with permissions to access the following tables: CVERS, DBCONS, and RFCDES.
* Ensure that you have the web service URL. For information on how to create web services, see .
{#sap-discovery__ul_y4j_4zy_dfb}
{#sap-discovery__ul_rt1_frx_mfb}
SAP HANA 2.0 DB Catalog on UNIX
: Verify that the Applicative Credentials for SAP HANA DB App Creds are configured with SAP Hana Db \[cmdb_ci_appl_sap_hana_db\] as CI type.
Verify the permissions to run Service Mapping commands
: [Service Mapping commands not requiring a privileged user](https://servicenow-prod.fluidtopics.net/PWerd39b5nEL~pJPadH4lQ "Most of commands utilized by Service Mapping for discovery and mapping do not require elevated rights.")
Verify the user has the permissions to run the Patterns queries
: The following commands are executed when running the SAP HANA DB and SAP HANA DB Catalog Patterns.
* `select * from schemas;`
* `select * from M_HOST_INFORMATION where upper(KEY) like '%TIMEZONE%';`
* `select SCHEMA_NAME, round(sum(TABLE_SIZE) /1024/1024) from M_TABLES GROUP BY SCHEMA_NAME`
{#sap-discovery__ul_b1c_4zf_vzb}
{#sap-discovery__table_nmf_jcg_vzb__entry__2}
| The query type | Fallback commands executed in order |
|-|-|
| Schemas Info | 1. `$hdbsql_path + " -n " + $entry_point.ip_address + ":" + $query_port + " -i " + $digits + " -u '$$username$$' -p '$$password$$' \"select * from schemas;\""` 2. `$hdbsql_path + " -n " + $ip_address + ":" + $query_port + " -i " + $digits + " -u '$$username$$' -p '$$password$$' \"select * from schemas;\""` 3. `$hdbsql_path + " -n " + $server_name + ":" + $query_port + " -i " + $digits + " -u '$$username$$' -p '$$password$$' \"select * from schemas;\""` 4. `$hdbsql_path + " -n localhost -i " + $digits + " -u '$$username$$' -p '$$password$$' \"select * from schemas;\""` {#sap-discovery__ol_yqb_lcg_vzb} |
| Time Zone: | 1. `$hdbsql_path + " -n " + $entry_point.ip_address + ":" + $query_port + " -i " + $digits + " -u '$$username$$' -p '$$password$$' \"select * from M_HOST_INFORMATION where upper(KEY) like '%TIMEZONE%';\""` 2. `$hdbsql_path + " -n " + $ip_address + ":" + $query_port + " -i " + $digits + " -u '$$username$$' -p '$$password$$' \"select * from M_HOST_INFORMATION where upper(KEY) like '%TIMEZONE%';\""` 3. `$hdbsql_path + " -n " + $server_name + ":" + $query_port + " -i " + $digits + " -u '$$username$$' -p '$$password$$' \"select * from M_HOST_INFORMATION where upper(KEY) like '%TIMEZONE%';\""` 4. `$hdbsql_path + " -n localhost -i " + $digits + " -u '$$username$$' -p '$$password$$' \"select * from M_HOST_INFORMATION where upper(KEY) like '%TIMEZONE%';\""` {#sap-discovery__ol_hzv_5cg_vzb} |
| Disk Size | 1. `$hdbsql_path + " -n " + $entry_point.ip_address + ":" + $query_port + " -i " + $digits + " -u '$$username$$' -p '$$password$$' \"select SCHEMA_NAME, round(sum(TABLE_SIZE) /1024/1024) from M_TABLES GROUP BY SCHEMA_NAME;\""` 2. `$hdbsql_path + " -n " + $ip_address + ":" + $query_port + " -i " + $digits + " -u '$$username$$' -p '$$password$$' \"select SCHEMA_NAME, round(sum(TABLE_SIZE) /1024/1024) from M_TABLES GROUP BY SCHEMA_NAME;\""` 3. `$hdbsql_path + " -n " + $server_name + ":" + $query_port + " -i " + $digits + " -u '$$username$$' -p '$$password$$' \"select SCHEMA_NAME, round(sum(TABLE_SIZE) /1024/1024) from M_TABLES GROUP BY SCHEMA_NAME;\""` 4. `$hdbsql_path + " -n localhost -i " + $digits + " -u '$$username$$' -p '$$password$$' \"select SCHEMA_NAME, round(sum(TABLE_SIZE) /1024/1024) from M_TABLES GROUP BY SCHEMA_NAME;\""` {#sap-discovery__ol_vpp_bdg_vzb} |
[ ]
{#sap-discovery__table_nmf_jcg_vzb}
Verify the configuration of the Discovery schedule
: For more information, see [Running discoveries in your network](https://servicenow-prod.fluidtopics.net/z1YAnBcRkarsV70KmkIhPw "You can run discoveries from schedules or scripts to create configuration items, define subnets, or to find resources in AWS and Azure clouds.")
## Data collected by Discovery during horizontal discovery {#sap-discovery__section_fyy_5nc_qrb}
{#sap-discovery__table_tvn_14c_qrb__entry__2}
| Table and field | Description |
|-|-|
| SAP ASCS \[cmdb_ci_appl_sap_ascs\] ||
| Name \[name\] | Data collected for SAP ABAP Central Services (ASCS) |
| Version \[version\] | Data collected for SAP ABAP Central Services (ASCS) |
| Installation directory \[install_directory\] | Data collected for SAP ABAP Central Services (ASCS) |
| Configuration directory \[config_directory\] | Data collected for SAP ABAP Central Services (ASCS) |
| Configuration file \[confi_file\] | Data collected for SAP ABAP Central Services (ASCS) |
| Instance name \[instance_name\] | Data collected for SAP ABAP Central Services (ASCS) |
| Instance number \[instance_number\] | Data collected for SAP ABAP Central Services (ASCS) |
| System ID \[sid\] | Data collected for SAP ABAP Central Services (ASCS) |
| System directory \[system_directory \] | Data collected for SAP ABAP Central Services (ASCS) |
| System type \[system_type\] | Data collected for SAP ABAP Central Services (ASCS) |
| Transport domain \[transport_domain\] | Data collected for SAP ABAP Central Services (ASCS) |
| SAP Business Objects CMS server \[cmdb_ci_appl_sap_bo\] ||
| Name \[name\] | Data collected for SAP Business Objects CMS Server |
| Server Name \[server_name\] | Data collected for SAP Business Objects CMS Server |
| Version \[version\] | Data collected for SAP Business Objects CMS Server |
| Installation directory \[install_directory\] | Data collected for SAP Business Objects CMS Server |
| SAP SCS Application \[cmdb_ci_appl_sap_scs\] ||
| Name \[name\] | Data collected for SAP Central Services (SCS) |
| Version \[version\] | Data collected for SAP Central Services (SCS) |
| Installation directory \[install_directory\] | Data collected for SAP Central Services (SCS) |
| Configuration directory \[config_directory\] | Data collected for SAP Central Services (SCS) |
| Configuration file \[config_file\] | Data collected for SAP Central Services (SCS) |
| Instance name \[instance_name\] | Data collected for SAP Central Services (SCS) |
| Instance number \[instance_number\] | Data collected for SAP Central Services (SCS) |
| System ID \[sid\] | Data collected for SAP Central Services (SCS) |
| System directory \[system_directory\] | Data collected for SAP Central Services (SCS) |
| System type \[system_type\] | Data collected for SAP Central Services (SCS) |
| Transport domain \[transport_domain\] | Data collected for SAP Central Services (SCS) |
| SAP CI Application \[cmdb_ci_appl_sap_ci\] ||
| Name \[name\] | Data collected for SAP CI |
| Version \[version\] | Data collected for SAP CI |
| Installation directory \[install_directory\] | Data collected for SAP CI |
| Configuration directory \[config_directory\] | Data collected for SAP CI |
| Configuration file \[config_file\] | Data collected for SAP CI |
| Instance name \[instance_name\] | Data collected for SAP CI |
| Instance number \[instance_number\] | Data collected for SAP CI |
| System ID \[sid\] | Data collected for SAP CI |
| System directory \[system_directory\] | Data collected for SAP CI |
| System type \[system_type\] | Data collected for SAP CI |
| Transport domain \[transport_domain\] | Data collected for SAP CI |
| SAP DI Applications \[cmdb_ci_appl_sap_di\] ||
| Name \[name\] | Data collected for SAP Dialog Instance (DI) |
| Version \[version\] | Data collected for SAP Dialog Instance (DI) |
| Installation directory \[install_directory\] | Data collected for SAP Dialog Instance (DI) |
| Configuration directory \[config_directory\] | Data collected for SAP Dialog Instance (DI) |
| Configuration file \[config_file\] | Data collected for SAP Dialog Instance (DI) |
| Instance name \[instance_name\] | Data collected for SAP Dialog Instance (DI) |
| Instance number \[instance_number\] | Data collected for SAP Dialog Instance (DI) |
| System ID \[sid\] | Data collected for SAP Dialog Instance (DI) |
| System directory \[system_directory\] | Data collected for SAP Dialog Instance (DI) |
| System type \[system_type\] | Data collected for SAP Dialog Instance (DI) |
| Transport domain \[transport_domain\] | Data collected for SAP Dialog Instance (DI) |
| SAP ERS Application \[cmdb_ci_appl_sap_ers\] ||
| Name \[name\] | Data collected for SAP Enqueue Replication Server (ERS) |
| Version \[version\] | Data collected for SAP Enqueue Replication Server (ERS) |
| Installation directory \[install_directory\] | Data collected for SAP Enqueue Replication Server (ERS) |
| Configuration directory \[config_directory\] | Data collected for SAP Enqueue Replication Server (ERS) |
| Configuration file \[config_file\] | Data collected for SAP Enqueue Replication Server (ERS) |
| Instance name \[instance_name\] | Data collected for SAP Enqueue Replication Server (ERS) |
| Instance number \[instance_number\] | Data collected for SAP Enqueue Replication Server (ERS) |
| System ID \[sid\] | Data collected for SAP Enqueue Replication Server (ERS) |
| System directory \[system_directory\] | Data collected for SAP Enqueue Replication Server (ERS) |
| System type \[system_type\] | Data collected for SAP Enqueue Replication Server (ERS) |
| Transport domain \[transport_domain\] | Data collected for SAP Enqueue Replication Server (ERS) |
| HANA Database \[cmdb_ci_appl_sap_hana_db\] ||
| Name \[name\] | Data collected for SAP HANA Database |
| IP Address \[id_address\] | Data collected for SAP HANA Database |
| Class \[sys_class_name\] | Data collected for SAP HANA Database |
| Fully qualified domain name \[fqdn\] | Data collected for SAP HANA Database |
| Version \[version\] | Data collected for SAP HANA Database |
| Installation directory \[install_directory\] | Data collected for SAP HANA Database |
| SAP SID \[cmdb_ci_sap_sid\] ||
| Name \[name\] | Data collected for the SAP System Identification (SID) code is a unique identification code for an SAP R/3 installation. An SID is a three-character code like D10, PRD, or E56. An R/3 installation consists of a database server plus several application servers. ITOM Visibility uses the SAP SID shared library pattern to discover SIDs for SAP applications. |
| Version \[version\] | Data collected for the SAP System Identification (SID) code is a unique identification code for an SAP R/3 installation. An SID is a three-character code like D10, PRD, or E56. An R/3 installation consists of a database server plus several application servers. ITOM Visibility uses the SAP SID shared library pattern to discover SIDs for SAP applications. |
| Patch Level Info \[sap_patch_info\] | Data collected for the SAP System Identification (SID) code is a unique identification code for an SAP R/3 installation. An SID is a three-character code like D10, PRD, or E56. An R/3 installation consists of a database server plus several application servers. ITOM Visibility uses the SAP SID shared library pattern to discover SIDs for SAP applications. |
[ ]
{#sap-discovery__table_tvn_14c_qrb}
## Data collected by the SAP HANA DB Catalog on UNIX pattern during horizontal discovery {#sap-discovery__section_rht_nmg_tzb}
{#sap-discovery__table_sx4_3ng_tzb__entry__2}
| Field | Description |
|-|-|
| Catalog Owner \[catalog_owner\] | The user ID of the schema owner. |
| Catalog Create Time \[catalog_create_time\] | The catalog creation time. |
| Disk Allocated Size (MB) \[disk_allocated_size_mb\] | The allocated Disk size in MB. |
| Database Reference \[database_instance\] | The reference to the SAP HANA DB. |
[Table 1. SAP HANA Catalog \[cmdb_ci_db_hana_catalog\]]
{#sap-discovery__table_sx4_3ng_tzb}
## CI Relationships {#sap-discovery__section_xmm_ynz_qrb}
The SAP SID shared library pattern creates CI relationships between all major CI applications and SAP System ID.{#sap-discovery__table_jcw_14z_qrb__entry__3}
| CI | Relationship | CI |
|-|-|-|
| SAP ERS Application \[cmdb_ci_appl_sap_ers\] | Uses::Used by | SAP SID \[cmdb_ci_sap_sid\] |
| SAP DI Applications \[cmdb_ci_appl_sap_di\] | Uses::Used by | SAP SID \[cmdb_ci_sap_sid\] |
| SAP ASCS \[cmdb_ci_appl_sap_ascs\] | Uses::Used by | SAP SID \[cmdb_ci_sap_sid\] |
| SAP CI Application \[cmdb_ci_appl_sap_ci\] | Uses::Used by | SAP SID \[cmdb_ci_sap_sid\] |
| SAP SCS Application \[cmdb_ci_appl_sap_scs\] | Uses::Used by | SAP SID \[cmdb_ci_sap_sid\] |
| SAP JC Application \[cmdb_ci_appl_sap_jc\] | Uses::Used by | SAP SID \[cmdb_ci_sap_sid\] |
[ ]
{#sap-discovery__table_jcw_14z_qrb}
SAP HANA DB Catalog on UNIX CI relationships
: {#sap-discovery__table_nqp_34g_tzb__entry__3}
| CI | Relationship | CI |
|-|-|-|
| SAP HANA DB \[cmdb_ci_appl_sap_hana_db\] | Contains::Contained by | SAP HANA DB Catalog \[cmdb_ci_db_hana_catalog\] |
[ ]
{#sap-discovery__table_nqp_34g_tzb}
## Limitations {#sap-discovery__section_odz_zwy_dfb}
Service Mapping can map only one instance
of ASCS per deployment.
The SAP HANA DB Catalog pattern can only run on UNIX.
## Map application services containing SAP applications {#ariaid-title2}
Map an service instance containing an SAP applications and verify that Service Mapping discovered
all SAP components correctly.
### Before you begin
Role required: service_mapping_admin
### Procedure
1. Create a service instance.
1. Navigate to AllService MappingService Instances.
2. Click New.
The Discoverable by Service Mapping option is selected by default.
3. In the Name field, enter a descriptive name for the service instance.
{#map-service-containing-SAP__substeps_fmn_1by_32b}
2. Define the entry point for this application service:
1. Select the SAP application tile.
The Discoverable by Service Mapping option is selected by default.
2. Define the entry point as follows:
* A URL to any SAP module
* A TCP connection to any SAP module
* To discover environments with connected services, provide the URL to the web service in the following format:
http://:/sap/bc/srt/scs/sap/z_servicenow_read?sap-client=003
{#map-service-containing-SAP__ul_fk3_mbz_dfb}
3. Click Add.
4. Click Save.
{#map-service-containing-SAP__substeps_iwl_q1z_dfb}
3. Click Additional Info on the left and clear the Traffic based discovery check box.
4. Click Update.
5. Verify that the mapping result is satisfactory:
1. Click View Map and wait until the mapping is complete.
It may take a few minutes.
2. Review the application service map and make sure that the service layout is as in the following examples.
{#map-service-containing-SAP__substeps_tzh_ycy_32b}
If the SAP environment integrates SAP components with Tibco services, you can expect this mapping result:
## Troubleshoot application services containing SAP applications {#ariaid-title3}
Fix basic discovery issues based on the symptoms and discovery messages.
### Symptom {#troubleshoot-services-containing-SAP__section_e2c_bdf_2fb}
The application service map in Service Mapping displays the following message `Failed to discover .`
### Cause {#troubleshoot-services-containing-SAP__section_y4h_lrf_2fb}
The CI failed to identify, and process detection retrieves the process attributes.
### Solution {#troubleshoot-services-containing-SAP__section_l1h_mrf_2fb}
Perform the following steps:
1. Open the failed pattern step in Debug mode:
1. On the business service or service instance map, right-click the error message and select Show discovery log.
The Discovery Log window opens.
2. In the right pane, locate the failed identification section and the failed step within this section.
3. Select this failed identification section and click Debug.
The Debug Identification Section window opens.
4. If necessary, fill in the required details and click Connect.
{#troubleshoot-services-containing-SAP__ol_fvn_2pp_mfb}
2. Click the set variables step under Steps.
3. Make sure that the regular expression includes `SYS` as shown in the following figure.
4. Click the set install_dir step under Steps.
5. Make sure that the regular expression includes `sap` as shown in the following graphic.
{#troubleshoot-services-containing-SAP__ol_ffb_trf_2fb}
### Symptom {#troubleshoot-services-containing-SAP__section_zny_b5f_2fb}
Service Mapping fails to discover the web service your organization uses to deploy SAP digital business services.
### Cause 1 {#troubleshoot-services-containing-SAP__section_fjk_c5f_2fb}
The pattern fails at the EVAL function for identifying the web service.
### Solution 1 {#troubleshoot-services-containing-SAP__section_tpp_c5f_2fb}
1. Verify that the format of the entry point is the URL to the web service as described in the mapping procedure.
2. Verify that you configured the necessary applicative credentials as described in the mapping procedure.
3. Check that the discovery log contains the following message: GROOVE_CODE_FAILURE: No such property: com for class: Script1.
4. Open the failed pattern step in Debug mode:
1. On the business service or service instance map, right-click the error message and select Show discovery log.
The Discovery Log window opens.
2. In the right pane, locate the failed identification section and the failed step within this section.
3. Select this failed identification section and click Debug.
The Debug Identification Section window opens.
4. If necessary, fill in the required details and click Connect.
{#troubleshoot-services-containing-SAP__ol_lpf_zpp_mfb}
5. Pattern Designer opens showing the selected identification section.
6. Select the failed step on the right.
7. Verify that the function running on EVAL is `com.snc.sw.util.HttpInvokerUtil.post`.
8. Try to map the application service again and check the result.
{#troubleshoot-services-containing-SAP__ol_j5q_2xf_2fb}
### Cause 2 {#troubleshoot-services-containing-SAP__section_bers_sbg_2fb}
The pattern fails at the EVAL function for identifying the web service, because the web service was configured incorrectly.
### Solution 2 {#troubleshoot-services-containing-SAP__section_cc5e_sbg_2fb}
1. Verify that the format of the entry point is the URL to the web service as described in the mapping procedure.
2. Verify that you configured the necessary applicative credentials as described in the mapping procedure.
3. Check that the discovery log contains the following message: "Debug run railed: Test step failed. GROOVE_CODE_FAILURE: All command implementations (HTTP) failed on host 10.x.x.x. Host must be down or unreachable. ()"
4. Recreate the web service as described in .
5. Try to map the application service again and check the result.
{#troubleshoot-services-containing-SAP__ol_dcd_sbg_2fb}
### Cause 3 {#troubleshoot-services-containing-SAP__section_px5_p84s_2fb}
The pattern fails at the EVAL function for identifying the web service, because the URL configured in the entry point is not correct or because the MID Server cannot access this URL.
### Solution 3 {#troubleshoot-services-containing-SAP__section_q455_48g_2fb}
1. Verify that the format of the entry point is the URL to the web service as described in the mapping procedure.
2. Verify that you configured the necessary applicative credentials as described in the mapping procedure.
3. Check that the discovery log contains the following message: "Debug run railed: Test step failed. GROOVE_CODE_FAILURE: All command implementations (HTTP) failed on host 10.x.x.x. Host must be down or unreachable. ()"
4. Verify that you used the correct URL for the service entry point:
1. In the TCode SOAMANAGER, navigate to Simplified Web Service Configuration.
2. On the Configuration tab of the Simplified Service Configuration window, search for the web service that is part of the service instance.
3. Click the check box under User Name/Password (Basic) for this web service.
4. Click Show Details.
5. On the Details of the Service Definition window, verify the actual URL of the web service under WSDL URLs.
6. If necessary, fix the URL you configure for the entry point and try to map the service instance again.
{#troubleshoot-services-containing-SAP__ol_z4c_thg_2fb}
{#troubleshoot-services-containing-SAP__ol_rx5_pdg_2fb}
### Cause 4 {#troubleshoot-services-containing-SAP__section_kwfrm_z3g_2fb}
MID Server cannot access this URL configured in the entry point of the service instance.
### Solution 4 {#troubleshoot-services-containing-SAP__section_l4ersm_z3g_2fb}
1. Verify that the format of the entry point is the URL to the web service as described in the mapping procedure.
2. Verify that you configured the necessary applicative credentials as described in the mapping procedure.
3. Check that the discovery log contains the following message: "Debug run failed: Test step failed. GROOVE_CODE_FAILURE: All command implementations (HTTP) failed on host 10.x.x.x. Host must be down or unreachable. ()"
4. Verify that you used the MID Server that can access the URL you configured in the service entry point:
1. Log into the MID Server host remotely.
2. Open a browser.
3. Paste the URL into the browser address bar and press Enter.
4. If the page does not open, it means that there is a network issue, for example, there is a firewall that prevents the MID Server from accessing this URL.
{#troubleshoot-services-containing-SAP__ol_n4m_z3g_2fb}{#troubleshoot-services-containing-SAP__VerifyingCredentials-networkIssues}
{#troubleshoot-services-containing-SAP__VerifyingCredentials-networkIssues}
5. Resolve the network issue and verify that the MID Server can access the URL as described in step [4](https://servicenow-prod.fluidtopics.net/~xvN7_LzKsSGGJ3jiuGOFw#troubleshoot-services-containing-SAP__VerifyingCredentials-networkIssues).
{#troubleshoot-services-containing-SAP__ol_m4m_z3g_2fb}
### Cause 5 {#troubleshoot-services-containing-SAP__section_qjm_ewg_2fb}
MID Server cannot access this URL configured in the entry point of the service instance.
### Solution 5 {#troubleshoot-services-containing-SAP__section_r99_3mg_2fb}
1. Verify that the format of the entry point is the URL to the web service as described in the mapping procedure.
2. Verify that you configured the necessary applicative credentials as described in the mapping procedure.
3. Check that the discovery log contains the following message: "Debug run railed: Test step failed. GROOVE_CODE_FAILURE: All command implementations (HTTP) failed on host 10.x.x.x. Host must be down or unreachable. ()"
4. Verify that the applicative credentials you configured on the ServiceNow AI Platform for the web service are valid:
1. Log into the MID Server host remotely.
2. Open a browser.
3. Paste the URL into the browser address bar and press Enter.
4. The browser page displays the credentials pop-up window.
5. Enter the credentials and check that the page opens. The page does not open, it means that the configured applicative credentials are incorrect.
{#troubleshoot-services-containing-SAP__ol_tjm_3mg_2fb}{#troubleshoot-services-containing-SAP__CredetialVerif-IncorrectCredtials}
{#troubleshoot-services-containing-SAP__CredetialVerif-IncorrectCredtials}
5. Find out the right credentials.
6. Verify the new credentials as described in step [4](https://servicenow-prod.fluidtopics.net/~xvN7_LzKsSGGJ3jiuGOFw#troubleshoot-services-containing-SAP__CredetialVerif-IncorrectCredtials).
7. If the page opens after you use the new credentials, configure these credentials as applicative credentials on the ServiceNow AI Platform.
{#troubleshoot-services-containing-SAP__ol_sjm_3mg_2fb}
### Cause 6 {#troubleshoot-services-containing-SAP__section_skg_wmg_2fb}
MID Server cannot access this URL configured in the entry point of the service instance.
### Solution 6 {#troubleshoot-services-containing-SAP__section_tkg_wmg_2fb}
1. Verify that the format of the entry point is the URL to the web service as described in the mapping procedure.
2. Check that the discovery log contains the following message: "Debug run railed: Test step failed. GROOVE_CODE_FAILURE: Missing applicative credentials for CI type \".
3. Verify that you defined applicative credentials for the relevant CI according as described in [Map application services containing SAP applications](https://servicenow-prod.fluidtopics.net/~xvN7_LzKsSGGJ3jiuGOFw#map-service-containing-SAP "Map an service instance containing an SAP applications and verify that Service Mapping discovered all SAP components correctly.").
{#troubleshoot-services-containing-SAP__ol_ukg_wmg_2fb}
*[\>]: and then