Versions Compared

Old Version 1

changes.mady.by.user Maria Hald

Saved on

compared with

New Version Current

changes.mady.by.user Maria Hald

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Image Added
Panel
panelIconId1f4d9
panelIcon:orange_book:
panelIconText📙
bgColor#FFFAE6

Using TM Integration Framework a Solution Manager ticket can be assigned to a transport request in SAP.
The prerequisite for this is that an OData service developed by REALTECH is installed on the Solution Manager system and the TM Integration Framework is configured in the Transport Management Server.

On this page

Table of Contents
maxLevel4
outlinetrue
stylenone
excludeOn this page

Prerequisites

SmartChange

Required Software components:

  • SAP_BASIS min 7.31 SP15

  • If the system runs on 7.31 as a prerequisite you have to deploy at least the following three add-ons IW_BEP, GW_CORE and IW_FND using transaction SAINT. When using SAP NetWeaver 7.40 or higher, this step is not necessary since the software component SAP_GWFND is already deployed as part of SAP Basis.

    Minimum requirement:

    • SAP Gateway Backend Framework:

      • IW_BEP 200 SP12

    • SAP Gateway Hub Framework:

      • IW_FND 250 SP12

      • GW_CORE 200 SP12

The compatibility matrix about SAP Gateway 2.0 support package stacks and the corresponding support package stacks for software component SAP_GWFND in SAP NetWeaver 7.40, 7.50 are to find in the SAP Note 1942072.

Solution Manager

  • Import transport request with the OData service developed by REALTECH

  • Service Registration /RTC/SOLMAN_SRV

On this page

Table of Contents
maxLevel4
outlinetrue
stylenone
excludeOn this page

Solution Manager

Odata Service /RTC/SOLMAN_SRV

Info

To get the transport request with the OData service, please ask for the latest version in the Support Portal.

  1. Import Transport Request REALTECH SC - SolMan API for TM Integration Framework.

  2. Service Registration (transaction /IWFND/MAINT_SERVICE)
    Go to /IWFND/MAINT_SERVICE to activate the Service Registration. The SICF node is delivered by default as inactive for security reasons.
    The technical service name is /RTC/SOLMAN_SRV - TransportManager OData Service.

    1. Click on the service name in the Service Catalog. 
      In the Systems Aliases window - add the system alias created before. 
      In the ICF nodes window - Activate the ODATA ICF node.  

      Image RemovedImage Added

Panel
panelIconIdatlassian-info
panelIcon:info:
bgColor#DEEBFF

REALTECH SC - SolMan API for TM Integration Framework

Service name: /RTC/SOLMAN_SRV

Partner configuration

With transaction /RTC/SM_API_CONFIG, you can configure the partners returned by the Realtech Solution Manager API, per transaction type (incident, service request, etc. ).
For version 1 of the API, only the first 3 partners are considered, in the ascending order of the sequence field.

Per transaction type up to three partner can be configured to return by the REALTECH Solution Manager API to the TM Integration Framework. In the TM Integration Framework, these partners can be selected for display in the selection pop-up. when a transport request is assigned to a Solution Manager ticket.

Call the transaction /RTC/SM_API_CONFIG to perform the configuration:

  1. Create an entry for relevant transaction type:

    Image RemovedImage Added

  2. Select up to three partner functions and define the sequence:

TM Integration Framework

ITSM System Configuration

You can easily configure a Solution Manager system within the TM Integration Framework, without knowledge of the technical details.
For the ITSM sytem configuration there are following templates with ITSM Type SOLMAN available:

  • TEMPLATE_ SOLMAN_SMIN - Integration with Incidents

  • TEMPLATE_ SOLMAN_SMIR - Integration with IT Requirements

Info

Copy existing templates for the Solution Manager integration as the initial configuration.

Inside of the ITSM configuration following two item types are available:

  • GET -> Query Solution Manager Tickets to display the selection popup
    The template is configured to display all three partners, configured in the SAP Solution Manager system. The number of partners is depending of configured sequence. Following is an example of configured fields, that will be displayed with the selection popup:

  • J2O -> Jump from TM Monitor to the Solution Manager Ticket

Workflow Step Configuration

For the Workflow step configuration, the following actions are included:

  1. Example to display selection popup at transport request creation time, but selection is optional and can be cancelled.
    If no Solution Manager incident was selected, then at release time the popup is displayed again and an incident must be selected.

    • TEMPLATE_ SOLMAN_SMIN GET - AFTER_WF_A After workflow assignment before release is finalized

    • TEMPLATE_ SOLMAN_SMIN GET - CREATION Creation of a request

  2. Example to display selection popup at transport request creation, but selection of an IT requirement is mandatory

    • TEMPLATE_ SOLMAN_SMIR GET CREATION - Creation of a request

Info

The filter query of the workflow step GET is used to define the Solution Manager transaction type. The filter can additional be used to limit the displayed entries in the selection popup. For example, to show only incidents with the status “In Progress”, you could extend the filter with the Estat field as follows:
Estat eq 'E0002' and ProcessType eq 'ZMIN'

The filter can be done by:

  • ObjectGuid

  • ObjectId

  • ProcessType

  • Estat

  • StatusTxt

  • CreatedBy

  • PartnerFct1

  • PartnerFct1txt

  • PartnerNo1

Note:
Selected partners to be displayed can be configured in transaction /RTC/SM_API_CONFIG.