Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 9 Next »

TM IF Configuration cockpit

The configuration cockpit (transaction /RTC/TM_IF_CONFIG) needs to be run on the TM Server only.
A default configuration is provided for activating a JIRA ITSM system, under following names:

  • TEMPLATE_ JIRA CLOUD

  • TEMPLATE_ JIRA SERVER

Calling transaction /RTC/TM_IF_CONFIG

TM Workflow step configuration

For an easy configuration, these entries can be copied changing the Server ID and setting the proper RFC destination.

Global activation settings

General settings for activating the TM Integration Framework.

 Technical details

Following entries can be defined by global settings:

Technical name

Field name

Value

Optional

SWITCH_OFF

'X' = TM Integration framework is inactive

Switch off the Integration Framework.
(‘X’ -> switched off)

ITSM_ATTR

Name of TR attribute for storing the ITSM server id

Name of the SAP Transport Request Attribute  

The SAP Transport Request attributes must exist on the Development systems (TCode SE03).

TITLE1

Title for pop up

Customized texts for the popup title

X

POPUP_TEXT

Name of Long Text (SO10) to be displayed in the popup

Name of a Smartform Text Module to be additionally displayed on the popup, as information

X

TR_TYPE

 

'A' = All, ' ' = Customizing and Workbench

Possible values:

  • 'A' : All type of transport requests;

  • ' ': Customizing and Workbench.

 This setting applies only to APPROVAL event. Define it as ‘A’ if Transport of Copies should also have a Ticket ID assigned.

If the entry is not defined, ‘ ‘ is considered as default value.

X

MOD_GET

Name of the function module for getting data

Name of customer function module to fetch the Ticket information from the ITSM System

X

MOD_SCREEN

Function module which contains the (individual) screen.

Feature not implemented in this version.

Name of the individual customer function module, which calls an individual screen.

X

ITSM systems configurations

In this step, you’ll configure parameters for external server.

  • ITSM system


 Technical details

Following fields can be defined:

Technical name

Field name

Value

Mandatory

SERV_ID

Server ID

Unique identifier for ITSM system.

ACTIVE

Active

‘X’ – ITSM is actively used by the Integration Framework

SERV_DESC

Server Description

Description of ITSM system (used in the popup_to_assign)

SERV_PATH

Server Path

Path of the external server (used in RFC destination).

SERV_RFC

RFC Destination

Name of the RFC destination of type G (HTTP Connection to External Server)

X

ITSM_TYPE

ITSM Type

Supported ITSM types:

  • JIRA (both On Premise and On Cloud)

  • SNOW (Service Now)

  • POLARION

X

  • Work Item

On this page

  1. TM IF Configuration cockpit

  2. Activate BADIs on the Development systems

  3. TM User Exits supported for Jira Plugin

    • Assign Ticket ID

      • BADI_CHECK_BEFORE_CREATION -> Action CREATION

    • Update Ticket ID

      • BADI /RTC/TM_IF_BD_CREATE_REQUEST -> Action LINK_TO_EXT

      • BADI /RTC/TM_IF_BD_DELETE_REQUEST -> Action DELETE_TR

      • BADI_FEEDBACK_AFTER_EXPORT-> Action RELEASE

      • AFTER_ADD2_WF -> No action (Must be activated in TM if either CREATION/AFTER_WF_A are activated)

      • ACTION_LOG -> Action APPROVAL

      • AFTER_IMPORT -> Action IMPORT

  • No labels