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 3 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

Global activation settings

ITSM system configuration

TM Workflow step configuration

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

General activation settings

Description: Global settings for activating the TM Integration Framework.

Following entries can be defined by global settings:

Field name

Value

SWITCH_OFF

Switch off the Integration Framework.

(‘X’ -> switched off)

ITSM_ATTR

Name of the SAP Transport Request Attribute for storing the ITSM system ID

 

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

TITLE1

Customized texts for the popup (title)

Optional.

POPUP_TEXT

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

Optional.

TR_TYPE

 

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.

 

Optional.

MOD_GET

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

Optional.

MOD_SCREEN

Feature not implemented in this version.

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

On this page

  1. TM IF Configuration cockpit

    • Calling transaction /RTC/TM_IF_CONFIG

    • Global activation settings

    • ITSM system configuration

    • TM Workflow step configuration

  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