Introduction

With ConnectALL's support for SAP Solution Manager, you will be able to configure the SAP Solution Manager adapter and sync records from it to other applications.

What's Supported

Authentication

Username/Password–Cookie Based Authentication

Functionalities

 Sync Comments

Sync Attachments

Sync Parent–Child Linking

Standard and Custom Processes

Partner Function Fields

Multi-Status Transition

Processes

ChaRM & ITSM

Standard Process Types

S1CR – Request for Change

S1DM – Defect

SMCR – Request for Change

SMIN – Incident

Setup

Configuration

The SAP Solution Manager adapter can be configured through the Value Stream Designer screen. The first step is to create a connection. To create a connection, drag the SAP Solution Manager adapter icon from the left panel on to the canvas; then draw a line between the SAP Solution Manager icon and the other adapter you wish to connect to. To know more about this in detail, click here.  You will need the below details to create the SAP Solution Manager connection:

• URL (Add the URL of the SAP Solution Manager server.)
• Username
• Password
• Time Zone

Time Difference Configuration

To know how to calculate the time difference, and configure it in the ConnectALL UI,  read the topic Time Difference Configuration.

Entity Mapping

We have shown below the Entity Mapping between Atlassian Jira and SAP Solution Manager. 

For more information on entity mapping, click here.

Flow Filters

We have provided the flow filters here.

Field Mapping

A typical field mapping between Atlassian Jira and SAP Solution Manager is shown below:

Available Fields

Mapped Fields

Sync _URL Field

The SAP SolMan adapter allows you to sync URLs. When a _URL field is mapped, you have to activate the AGS_WORKCENTER service in SolMan to render the SolMan artifact URL correctly in the browser.

For more information on field mapping, click here. 

Enhancements

Supported Processes

• ChaRM & ITSM

Note that ConnectALL supports only the standard set of fields common for all the processes. Also, if you select the processtype as Change Document (as shown in the image), you have to select one of the options from the drop-down list ('true' or 'false') in the isChangeDocument field.

Supported Standard Process Types

• S1CR – Request for Change
• S1DM – Defect
• SMCR – Request for Change
• SMIN – Incident

If you want to add more custom process types (YDCR & YMPR) as shown in this adjacent image, you can add them by going into the Manage Connections  screen and providing the respective process type’s key in the Connection Advanced Properties screen. This is explained further below.

Adding Custom Processes

To add more custom processes (so they can be available as an artifact type on the Entity Mapping tab.), 

1. Click Connections from the top navigation bar. The Manage Connections screen will be displayed.
2. Click the cogwheel icon to edit the existing connection. The Connection Advanced Properties screen will be displayed.
3. Add the key and the description of the additional process type you wish to add in the Additional Process Types field. For example, if you want to enter YDCR, then mention it as YDCR=DPAce Change Request. If you have more than one additional process type, use a semicolon (;) to separate each additional process type. 
4. Click Save Properties.

Establishing Parent – Child Relationship

ConnectALL allows you to establish a relationship between the parent-child entities such as RFC (Request for Change) and CD (Change Document). Let's say you have an SAP SolMan <–>Jira automation. Assume that in Jira, you have a User-Story and its sub-task. Further, in SAP SolMan you have Request for Change and its child entity, Change Request. In such a scenario, for the record synchronization to happen between the parent-child entities of both the applications,

• Create an automation between the issue types — User Story(Jira) and RFQ (SolMan)
• Create an automation between the issue types — sub-task (Jira) and CD (SolMan)

In the second automation, map any text or hidden field (in Jira) with the 'Scope Description' field (in SolMan) as shown below.

Doing this will help ConnectALL to identify the corresponding change document in SAP by using the text/hidden field’s content (in Jira's sub-task). In the absence of this field mapping, ConnectALL will use the 'Summary' field (in Jira's sub-task) to identify the corresponding change document in SolMan. The mapping direction of this row has to be uni-directional.

Multi-Status Transition

ConnectALL's SAP adapter is capable of handling multi-status transition. You have to enable multi-status transition (image 1) in the Connection Advanced Properties field (Connections>Manage Connections>Connection Advanced Properties). Only if you enable, the MultiStatus option will be available to be selected and will be visible as one of the options against the Data Type Mapping drop-down list (image 2) in the Field Configuration screen.

                                                                                                 Image 1

Note: The inclusion of the last entry in the above image (CHARM_ITSM_UTILS_SERVICE_NAME)is essential for multi-status transition and for enabling Parent-Child relationship. 

                                                                                                  Image 2

Comment Synchronization

Comment Synchronization is supported in ConnectALL’s SAP adapter. As SAP has different field options such as ‘Description’, ‘Internal Note’, ‘Reply’ etc.., to enter a comment, these fields also have to be mapped separately while mapping. And this mapping is done using the Comment Visibility Mapping feature in the Value Mapping screen. While mapping, instead of mapping those field names, the IDs of the fields have to be selected. This is illustrated in the image. (Note that the respective field IDs are chosen in the Value Mapping screen using Advanced Value Mapping options to achieve comment synchronization.)