ServiceNow Change Request Management controls SAP TMS
Video from 3/27/2023
ServiceNow CTasks easily integrated with SAP Transport Management (SAP TMS)
Please enable videos in our privacy settings
Here we show another type of integration between ServiceNow Change Management and SAP transport management / SAP CTS based on Conigma CCM.
To emphasize the flexibility and power of Conigma Connect, before the video starts, four integration examples are shown on a conceptual level before the video starts.
1. Integration of ServiceNow Incident / Problem and Conigma™ CCM Change
2. Integration of ServiceNow Changes Requests / CTasks hierarchies and the hierarchical Conigma™ CCM changes
3. Integration of ServiceNow CTasks with Conigma™ CCM Changes without any hierarchies
4. Additional integration of ServiceNow incidents created from Conigma™ CCM changes via corresponding status transitions.
In the video, the third example is shown. This is the integration model most often chosen by our customers. It allows complete remote control of SAP transport management / SAP CTS by ServiceNow.
The first example generates Conigma CCM Changes directly from ServiceNow Incidents or Problems.
The second example works with hierarchical Changes. Here, Conigma CCM Changes are created from ServiceNow CTasks.
In addition, hierarchical Changes are automatically created and linked to the corresponding ServiceNow Change Requests.
The third example, which is the one shown later in the video, creates a flat structure of Conigma CCM Changes from ServiceNow CTasks.
This is the integration model most often chosen by our customers.
The fourth example creates the corresponding Incidents in ServiceNow triggered by status transition of a Conigma CCM Changes change. The incidents are linked to the appropriate ServiceNow Change Request.
The following video shows the third example, the link of ServiceNow CTasks with Conigma CCM Changes without further change hierarchies.
On the left side we see a ServiceNow Change Request. This Change Request is already in the status "scheduled".
Linked to this Change Request are already two CTasks.
On the right side we see that the corresponding Conigma CCM Changes have already been created automatically by Conigma Connect.
All these entities are bi-directionally linked to each other via Conigma Connect.
For our present example we now create a new CTask in ServiceNow.
Saving the CTask creates the corresponding Conigma CCM Change.
Conigma CCM Change ID and status are automatically stored on the CTask.
The Conigma CCM Change was created in status new. A status change can now be triggered on ServiceNow.
Triggered from ServiceNow, the Conigma CCM Change has now been moved to the status "In development".
These two SAP transports are not needed now.
We now create a new transport for the new Conigma CCM Change.
Here we now have two new transports, one Customizing, and one Workbench.
One of the two transports will now be released.
The result can be seen by the changed icon (slanted arrow upwards).
A refresh on the left side shows the two transports with their respective properties also in ServiceNow.
Using the context menu, the change is now moved forward in the process. In the current setup, the one open transport is now released and both transports are imported into the QA system.
Here, any behavior can be customized in the context menu, e.g. also working with transports of copies or approvals.
After a refresh on the right side, you can see the change in the status "Development Completed".
The same can be seen on the CTask
Now the import is done in the background. The Change now automatically transitions to the next status, depending on the return code of the import.
In ServiceNow, you can already see this.
In Conigma CCM after a refresh.
Here, the tester can now continue by approving the Change or sending it back to development.
Of course, the same can be done remotely via ServiceNow.