💡 Surprising Fact: 90% of delays in SmartChange-ServiceNow integrations do NOT occur during technical configuration, but rather due to organizational dependencies. Pure configuration takes only 1 day!
🤔 Why do integrations often take 6-8 weeks instead of 2 weeks
The most common pain points in customer projects:
"Why has the firewall access been blocked for 3 weeks on our project?"
"Why doesn't the registration work even though all services are activated?"
"Why do we see thousands of ServiceNow tickets, but none that are SAP-relevant?"
🎯 The secret to 4-week time savings: Parallel activities during lengthy organizational processes and early preparation of all technical steps!!
🚀 The 4 Critical Implementation Phases
Phase 1
Integration Architecture Decision Option 1: Cloud Connector + SAP Integration Suite (modern solution) Proxy is set up for the connection between SAP and ServiceNow Technical user with user mapping for audit logs and authorization checks Token-based authentication, IP restrictions integrated
Option 2: Classic integration via SAP Gateway Server Direct firewall access required WebGUI registration directly in SmartChange Panel Browser cookies settings to consider (third-party cookies must be allowed!)
| Phase 2
The Critical Path - Organizational Hurdles
🔥 The real time killer: Not the technology, but organizational processes! Firewall-Configuration(⌚ 2-4 weeks average): Other departments need to be involved External teams have different priorities and timelines Approval processes and security guidelines delay the project
💡 Pro-Tip: Use this waiting time as your chance! Run all technical preparations in parallel. | Phase 3
Technical Preparation
(during Firewall Configuration!)🚀Parallel executable preparations - save valuable time here:ServiceNow-Preparation: SAP-Preparation: Check SAP profile parameters Import ServiceNow certificates Create RFC connections to ServiceNow Set up Trusted RFC connections Activate SAP Gateway & REALTECH OData Service TM_GW_SRV Configure user permissions Maintain HTTP whitelist (if used)
SAP BTP/Cloud Connector Preperation (if selected): | Phase 4
Final Implementation
Customer Configuration Workshop 🎯 The implementation happens together with the customer SmartChange Integration Framework: 0,5 days (customer workshop) ServiceNow-Configuration: 0,5 days (customer workshop)
This is the moment when everything comes together! Here, the integration is configured and tested in the SmartChange Integration Framework - after all preparations are completed. |
|---|
Phase 1
Integration Architecture Decision Option 1: Cloud Connector + SAP Integration Suite (modern solution) Proxy is set up for the connection between SAP and ServiceNow Technical user with user mapping for audit logs and authorization checks Token-based authentication, IP restrictions integrated
Option 2: Classic integration via SAP Gateway Server Direct firewall access required WebGUI registration directly in SmartChange Panel Browser cookies settings to consider (third-party cookies must be allowed!)
| Phase 2
The Critical Path - Organizational Hurdles
🔥 The real time killer: Not the technology, but organizational processes! Firewall-Configuration(⌚ 2-4 weeks average): Other departments need to be involved External teams have different priorities and timelines Approval processes and security guidelines delay the project
💡 Pro-Tip: Use this waiting time as your chance! Run all technical preparations in parallel. | Phase 3
Technical Preparation
(during Firewall Configuration!)🚀Parallel executable preparations - save valuable time here:ServiceNow-Preparation: SAP-Preparation: Check SAP profile parameters Import ServiceNow certificates Create RFC connections to ServiceNow Set up Trusted RFC connections Activate SAP Gateway & REALTECH OData Service TM_GW_SRV Configure user permissions Maintain HTTP whitelist (if used)
SAP BTP/Cloud Connector Preperation (if selected): | Phase 4
Final Implementation
Customer Configuration Workshop 🎯 The implementation happens together with the customer SmartChange Integration Framework: 0,5 days (customer workshop) ServiceNow-Configuration: 0,5 days (customer workshop)
This is the moment when everything comes together! Here, the integration is configured and tested in the SmartChange Integration Framework - after all preparations are completed. |
|---|
⚠️ The Most Common Pitfalls (and how to avoid them)
🔥 Pitfall #1: Firewall Process Underestimated
Problem: "That only takes a few days" - wrong thinking! Solution: Plan 2-4 weeks and use this time for parallel activities.
🔥 Pitfall #2: IP Blocking
Problem: SAP Transport Integration App IP 20.29.88.233 is forgotten in firewall policy. Solution: Must be configured in firewall unconditionally - otherwise nothing works!
🔥 Pitfall #3: SAP Services not activated
Problem: Required SAP services are forgotten to be activated. Solution: Activate /sap/opu/odata/RTC/TM_GW_SRV/, WebGUI services only required for classic integration.
🔥Pitfall #4: Trusted RFCs incorrectly configured - Transports don't work
Problem: Transport creation or ToCs fail even though connection exists. Solution: Set up Trusted RFC connections between SAP and ServiceNow correctly - otherwise no transport operations possible.
🔥 Pitfall #5: HTTP Whitelist not maintained
Problem: Connection setup is blocked even though everything is configured. Solution: Maintain HTTP whitelist in SAP if used in the company.
💡 User-Friendliness Tip:
For classic WebGUI integration, allow third-party cookies in browser - otherwise login in new window (less comfortable, but functional).
📊 Realistische Zeitschätzungen
| | | |
|---|
Final Configuration | 1 Day | 1 Day | 1 Day |
Technische Vorbereitung | 1-2 Weeks | 1-2 Weeks | 2-3 Weeks |
🔥 Firewall/Organization | 2-3 Weeks | 3-4 Weeks | 4-6 Weeks |
🎯 TOTAL | 3-4 Weeks | 4-6 Weeks | 6-8 Weeks |
The difference between scenarios: Not the integration type, but the speed of your internal processes!
🎯 Workflow & Permissions: The Essentials in Brief
✅ Workflow Configuration: Nothing needs to be changed in ServiceNow! Status-dependent approvals are configured in the SmartChange Panel.
✅ Permission Check: Done SAP-side with standard authorization mechanism. For technical users, check against the mapped SAP user - that's why user mapping is so important.
✅ Ticket Filtering: Use queries as in ServiceNow. Separate configurations for Incidents and Change Requests required, as ServiceNow uses different tables internally.
💼 Conclusion: Integration type is secondary - the real time gain lies in optimal utilization of unavoidable waiting times during organizational processes. Start technical preparations parallel to firewall configuration and reduce your total project time by up to 4 weeks!
📝 Based on experiance from 50+ SmartChange integration projects
Related articles
