Skip to main content
Skip table of contents

SolMan

General information

Scenario

SOLMAN

Implementing class

/INT4/IFTT_CM_SOLMAN

XSLT1

RequestGuid.xslt 

Incident Guid request

XSLT2

RequestSystemGuid.xslt

System Guid Request

XSLT3

ProcessIncident.xslt

Request creating incident

XSLT4

ReadCompleteIncident.xslt

Request reading incident status

XSLT5

CloseIncident.xslt

Request closing incident

XSLT6

AddInfo.xslt

Request adding infos (texts and urls) to the incident


ICT_SERVICE_DESK_API Configuration

To enable the integration between int4 Suite and SolMan, it is required to activate the ICT_SERVICE_DESK_API service in SICF.

Please follow the necessary steps outlined in the links provided below:

  1. https://blogs.sap.com/2015/03/11/how-to-create-incident-in-solution-manager-71-from-the-soapui-or-any-other-external-application/

  2. https://blogs.sap.com/2013/03/09/activating-ictservicedeskapi-in-71/

Go to the transaction SPRO and go to SAP Solution Manager → Capabilities (Optional) → IT Service Management → External Integration → External Service Desk → Web Service - based Configuration:

  1. Create the technical user that will be used to call the web service and assign the following roles:

    1. SAP_CM_MANAGED_ADMIN

    2. SAP_SMWORK_CHANGE_MAN

    3. SAP_SMWORK_INCIDENT_MAN

    4. SAP_SMWORK_SM_ADMIN

    5. SAP_SUPPDESK_CREATE

    6. SAP_SM_CRM_UIU_SOLMANPRO

    7. SAP_SM_CRM_UIU_SOLMANPRO_CREA

    8. SAP_SM_CRM_UIU_SOLMANREQU

  2. Make sure you have activated service ICT_SERVICE_DESK_API in the transaction SICF

  3. Configure the service provider for the service ICT_SERVICE_DESK_API in SOAMANAGER

  4. Configure the Service Consumer. If the application has the SOAP API, provide the WSDL

  5. Add a new entry in table ICT_SYSCONF via tcode ICTCONF:

  • Logical port - port you defined in step 4 of activating ICT_SERVICE_DESK_API

  • Name - type any name you like

  1. Define value mapping:

Fill all the entries as provided on the screenshot:

External Service Desk ID is the GUID from ICT_SYSCONF.


XSLT Configuration

To send valid requests to SolMan ICT_SERVICEDESK_API, you need to configure XSLTs
in the transaction /INT4/IFTT_IMG → Run Configuration wizard → Maintain Change Management Integration.

Add a new record:

You need to upload the appropriate XSLTs to their corresponding fields. The significant benefit is that users can modify the information sent to SolMan by adjusting the XSLTs.

XSLT1

RequestGuid.xslt 

No configuration

XSLT2

RequestSystemGuid.xslt

No configuration

XSLT3

ProcessIncident.xslt

  1. Insert generated Guid from  ICT_SYSCONF into <RequesterGuid> field

  2. Insert number of reporter in SolMan into <ReporterId> 

  3. Insert short description into <ShortDescription>
    (max 40. signs) - you can use function 'substring', ex. substring(TEST_RESULTS/_-INT4_-IFTT_ST_TC_RES[1]/DESCR,1,40)

  4. Insert incident priority in <Priority>

  5. Inser language in <Language>

  6. Insert requested begin and end of incident  in <RequestedBegin> and <RequestedEnd> in the format YYYYMMDD

  7. Inser value into <IctId>

  8. Insert <PersonId> from <ReporterId>

  9. <PersonIdExt> may remain 'dumy'

  10. Insert <FirstName> and <LastName>

  11. Insert <Email> of IctPerson. It is essential that <IctPersons> exists in the query. Otherwise, webservice throws an error

  12. Insert 'SU99' into <TestType>

  13. Under <Texts> → <item> insert any description you want. You can use fields provided in structure /int4/iftt_st_tc_res.

Remember, that <IctPerson> has to exists and all the fields <PersonId> and <Langauage> have to contain the same values.

XSLT4

ReadCompleteIncident.xslt

NECESSARY: Insert  generated Guid from  ICT_SYSCONF into <SystemGuid> field

XSLT5

CloseIncident.xslt

NECESSARY: Insert generated Guid from  ICT_SYSCONF into <RequesterGuid> field

Regarding the rest of the fields - refer to the XSLT3 description

XSLT6

AddInfo.xslt

NECESSARY: Insert generated Guid from  ICT_SYSCONF into <RequesterGuid> field

Regarding the rest of the fields - refer to the XSLT3 description

Usage

When you go to SolMan to the specific incident:

  • In Description you will see what was typed in <ShortDescription> in ProcessIncident.xslt.

  • Reported by is assigned to <PersonId> in ProcessIncident.xslt

  • Priority is <Priority> in ProcessIncident.xslt

In text section you will see Information typed in <Texts> → <item> in ProcessIncident.xslt when incident is created, in AddInfo.xslt when incident is updated:

  • SOL_EXT_SERV is a technical user defined earlier

  • 0000000141 is <PersonId> from the request

In the Attachments section, you will see URLs linked to test case report in int4 Suite:

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.