{"id":27449,"date":"2020-07-01T11:10:13","date_gmt":"2020-07-01T08:10:13","guid":{"rendered":"https:\/\/www.blue.works\/?p=27449"},"modified":"2026-02-19T15:15:24","modified_gmt":"2026-02-19T14:15:24","slug":"how-snow-and-charm-connect","status":"publish","type":"post","link":"https:\/\/www.blue.works\/en\/how-snow-and-charm-connect\/","title":{"rendered":"How SNOW and ChaRM connect"},"content":{"rendered":"\n

As the only SAP certified AddOn in the area of integration with ServiceNow, CONCORN promises with its SNOW adapter the integration with SAP Solution Manager in the areas of ChaRM<\/a>, Alert\/Monitoring and ITSM. In this technical SNOW adapter blog post we would like to talk about the integration with ChaRM.<\/p>\n\n\n\n

When integrating third-party software, the first hurdle is the clarification of the architectural target: How may applications communicate with each other? Are simple port connections sufficient or does the DMZ play a role? These questions can only be answered on a company-specific basis. Once these questions have been clarified and a connection has been established, we move on to the system coupling phase.<\/p>\n\n\n\n

On the SAP side, a service user with suitable authorizations and an RFC destination of type Http connection must be created for the coupling. The accessibility of the oData Services in the AddOn should be checked after installation and activation to avoid connection problems at an early stage.<\/p>\n\n\n\n

The Customizing activities to be carried out afterwards mainly concern the areas CRM and PPF and include the creation of new transaction types with additional new statuses. Status changes are then completed using configurations of PPF actions and scheduling conditions. Z-Customizing is also necessary, for which CONCORN delivers the view cluster \/SNOW\/INT_CONFIG. The last setting concerns the ChaRM UI, which is extended to display the data transferred by SNOW. (e.g. SNOW change ID, SNOW status)<\/p>\n\n\n\n

For the end user, the jump from SNOW is made easier by dynamically generating a link to the change created in ChaRM. This saves the end user the tedious search for the Change generated by SNOW.<\/p>\n\n\n\n

The Customizing settings mentioned above are required for each process. We have configured two processes on our demo: Normal Change and Urgent Change. The following figure illustrates the status change and communication points of both systems in a Normal Change process.<\/p>\n\n\n\n

\"\"
Process Flow between servicenow and SAP Solution Manager.
Click here to download \u2192<\/a><\/figcaption><\/figure>\n\n\n\n

For more information about SNOW and the integration with the ServiceNow suite, please contact Kenneth Staub<\/a>.<\/p>\n\n\n\n

blueworks’ experience with SAP Application Lifecycle Management (ALM) dates back to the early 2000s. blueworks was the first Swiss company to be specifically certified by SAP to offer Solution Manager as a managed service and one of only 10 companies in the Focused Solution Circle. Our mission is to help companies get the most out of the latest ALM solutions and to integrate them optimally into the customers landscapes and their processes.<\/p>\n\n\n\n