Professional Documents
Culture Documents
Step by Step Process of Integrating SAP Solution Manager To External Systems
Step by Step Process of Integrating SAP Solution Manager To External Systems
External Systems
Scenario:
SAP Solution Manager is an Incident Life Cycle tool for SAP Systems. There are
many such tools in market for different ERP which does the same job. Organizations
may have more Incident Lifecycle tool and managing them centrally helps
organization to view status of incident in a single dashboard.
Integrating two different ERP systems is achieved only with HTTP Calls and without
middleware. This blog will cover the integration between SOLMAN and SNOW for
the Incidents, Problem management and Service requests to be communicated
between these two systems which are connected through HTTP/HTTPS SOAP 1.1
call.
Mid Server is Java Application built by Service Now to access SAP System outside
its Network. Since Service Now is in Cloud, it can’t access SAP without this server.
Mid Server is set of libraries that must be installed in Firewall of SAP Network
Settings.
Service Consumer proxy for external WSDL can’t handle response as it doesn’t have
ABAP Class. Response must be handled separately via Service Provider Proxy.
3.Methods and Fields inside the WSDL structure can be viewed in External View.
Service Consumer Methods
SOAMANAGER
BAdI Implementation
Now Implementation Class and Proxy is Created. Once the fetching logic is
processed, Proxy class method can be called which in turn sends the data to Service
Now System.
Useful Tips:
Function Module
WSDL generated from this Proxy can be utilized to send Response for request sent
from Service Provider Proxy created above.
Create FM with import parameters in such a way that it should populate values for
ICT_INCIDENTGUID and ICT_INCIDENTATTR tables for Solman Service Now
Incident GUID Mapping
1. Create Remote Enabled Function module and convert the FM to Web Service
(Create a Web Service from Function Module, go to Utilities -> More Utilities -
> Create Web Service -> From Function Module)
SPRO
SPRO
Step 4: Create a logical port for the proxy and make it default.
Step 5: Got to SPROXY and WSDL for the consumer Proxy can be imported from
here .
Step 6: Data can be passed to any method of this WSDL structure and based on
requirement and Incidents can be processed (Create/Update/Delete/Read) in the
database .