SmartChange 2019 SP2 HF05

Enhance SAP webgui service for Jira integration

With this feature, an enhancement for standard SAP OData service for SAP login page has been developed, for sending cookies to the server request of the Jira Plugin 'SAP Transport Integration for Jira' (https://sap-transport-integration-for-jira1.azurewebsites.net, or the Jira Server host)
The feature request is needed for using specific application functionalities within the Jira plugin:

• Create SAP transport request
• Approve/Revoke transport request within the TM workflow

The enhancement is necessary as the cookies cannot be retrieved from the browser when logging into SAP from an external server because of different origin security policies. The browser security is not allowing a server to access cookies from another server, therefore the cookies are sent from SAP with the enhancement and saved temporarily in Jira.

In order to activate the feature, the following steps have to be done:

• On the TM server, maintain the Whitelist for the allowed external servers (to which the cookies can be sent): Table HTTP_WHITELIST, create an entry for host 'https://sap-transport-integration-for-jira1.azurewebsites.net' if Jira is a Cloud instance type, or the Jira Server host for the other Jira types.
• On the TM server, activate and configure the WebGui SAP standard service /default_host/sap/bc/gui/sap/its/webgui (transaction SICF>tab Handler List), by adding the handler /RTC/CL_HTTP_HANDLE on the first position.

Integration Framework, Jira_App

SC-742

Automation of TM Integration Framework User Exits / BAdIs by moving to standard

With this new feature, you no longer have to configure the specific TM IF function modules as TM User Exits. They are automatically called in the /RTC/ standard, depending on the TM Integration Framework Configuration.

The following scenarios/user exits have been moved to the standard:

Scenario: Assign Ticket ID
TM User Exit: BADI_CHECK_BEFORE_CREATION

Scenario: Update ITSM (Jira issue)
TM User Exit: BADI_FEEDBACK_AFTER_EXPORT
TM User Exit: AFTER_ADD2_WF
TM User Exit: ACTION_LOG
TM User Exit: AFTER_IMPORT

The TM IF functionality is only executed if the TM IF is active.
The parameter SWITCH_OFF has been enhanced (/RTC/TM_IF_CONFIG>Global Configuration):

• the Integration Framework is considered active only if the parameter SWITCH_OFF is configured and set to value ''.
• to turn off the Integration Framework, you can either delete the SWITCH_OFF parameter from the configuration or set it to 'X'.

Note!
The TM IF is delivered by default as inactive.
If TM IF is activated, there are several consistency checks of the configuration which are executed and might interrupt the TR creation process.

Integration Framework

SC-781

View package information in Personal Queue

With this new feature, you can view the Package Number and Package Short Text in the Personal Queue. The two columns are only displayed if at least one transport from the queue belongs to a package.

Queues/Proposals, UI

SC-673

View package information in System Queue

With this new feature, you can view the Package Number and Package Short Text in the System Queue. The two columns are only displayed if at least one transport from the queue belongs to a package.

Queues/Proposals, UI

SC-790

TM Tools > Import Tracking: Show 'Umode' information

With this feature, a new column for Umode was added in TM_TOOLS->Import Tracking: Single System and TM_Tools->Import Tracking: Between two systems. If the user wants to add the transport to the personal queue with the existing Umode, then the "ext_umodes" feature from /rtc/tm_opt table need to be activated.

Tools, UI

SC-642

SM>Workbench Detail section>tab Request: show the status of the object as well

With this feature, the column "Status" from the detail section was changed in "Tasklist status". Additional was added a new column "Object status" that shows the color of the status as in the object list section. This helps when several objects belong to one transport and some objects have already been synchronized while others have not.

Objects analysis, Synchronization, Workbench

SC-768

Synchronization Transport sequence check (part 2)

With this feature, you are now able to see if objects from current transport are synchronized in the right order. If there are previous transports not synchronized for the object, or a newer transport was already synchronized for the object corresponding messages will be displayed:

• 'Previous TRs have not been synchronized yet. Do you want to continue?'
• 'Latest version has already been synchronized. Do you want to overwrite?'

Synchronization, UI

SC-688

Authorization 'AP' is needed for entering TM>Project Manager in display mode

Issue:
If the user does not have the activity "AP" (AP = Administration Projects, authorization object ZRTC_TM), he cannot enter the Project Manager tab (TM>ProjectManager).
This is inconsistent with the other configuration screens, Systems&Groups or Destinations, when the user can enter in display mode. And the proper authorization is checked only when changing to edit mode.

Root cause:
The program checks for activity "AP" when calling the Project Manager.

Solution:
The code was changed, the activity "AP" is checked only when the "Change" button is pressed.

Configuration, Roles/Authorizations, UI

SC-772

Approve/Revoke approval for TR in SmartChange Panel

Issue:
When performing an approval/revoke approval via the OData service (/sap/opu/odata/RTC/TM_GW_SRV/TR_ApproveSet) for a transport level, the action is successfully performed, but nevertheless, the call returns an error code.

Root Cause:
The call is trying to perform the action for all the levels, not only for the current one.

Solution:
The program has been corrected. The OData is executing the action only for the current level.

OData Services

SC-750

OData Create_TR attributes 'ExternalAttribute' and ''ExternalID' are wrongfully mapped to the TM IF attributes

Issue:
When creating a transport request via Odata service, passing value to the parameters 'Externalattribute' and 'ExternalID', they are mapped like this:
'Externalattribute' -> ZRTC_TM_TICKET_ID
'ExternalID' -> ZRTC_TM_ITSM_ID.
According to the documentation, it should be the other way around.

Root cause:
Programming error.

Solution:
The program has been corrected.

OData Services

SC-797

Reference Timestamp for External Transport is confusing

Issue:
When adding an external transport in TM, if the reference timestamp can not be read from the Cofile, a pop-up window appears, warning the user and asking to insert it manually.
However, the inserted timestamp is sometimes not taken into consideration. Instead, it is replaced with the current timestamp when the transport was added in TM.

Root cause:
There is a configuration table, /RTC/TM_SPECS, containing SIDs of special systems. If the originating system of a transport request is mapped in this table, the original release date and time will be considered as reference timestamps when manually adding the transport into the TM Workflow.
Otherwise, the current date and time will be considered.

There was a programming error handling this scenario when the timestamp cannot be read from the Cofile.

Solution:
The program has been corrected. The popup to insert manually the reference timestamp will be displayed only if the SID for the external transport exists in the table /RTC/TM_SPECS, therefore it is needed and used.
Otherwise, the reference timestamps is completed automatically with the current date and time when the transport was added in TM.

UI

SC-698

TM>Global Settings: When entering the screen a second time, an empty window is displayed

Issue:
When a user enters TM>Global Settings a second time without completely leaving the transaction, an empty rectangle window appears on top of the screen. The settings can not be seen anymore, the only solution is to exit completely from TM and enter again.

Root cause:
This bug is caused by SAP Theme. It seems not all the SAP Themes free the ALV container after leaving the screen.

Solution:
The code has been corrected and now the containers are freed manually.

UI

SC-726

Short dump GETWA_NOT_ASSIGNED occurs in program /RTC/SAPLSA_CUST when displaying object details

Issue:
Short dump GETWA_NOT_ASSIGNED is occurring in program /RTC/SAPLSA_CUST, in SM>Customizing when double-clicking an object of type BOBX (Business Object Extension) for details.

Root cause:
The Details view is limited to 40 tabs; if more than 40 tabs are necessary for displaying the tables entries of the specific object, the short dump occurs.

Solution:
The maximum number of displayed tabs has been increased to 50.
If more than 50 tabs are still necessary a message like: 'Number of displayed tabs is limited to 50 from &.' This means that the user cannot see all the data within the SM Details tab.

Customizing, Objects analysis, UI, Workbench

SC-774

Empty popup is displayed when double-clicking a SYNC request in the synchronization tree

Issue:
By double-clicking an SYNCXXXXX request in the SM Request tree, an empty popup window is showing.

Root cause:
The standard behavior is to show the MAINT TR including all the objects, but when choosing an SYNCXXXXX there is nothing to display.

Solution:
The program has been corrected.

Synchronization, UI

SC-761

Synchronization via Original TR is not possible due to missing objects on DEV system

Issue:
Synchronization via Original TR is not possible due to missing objects on DEV system.

Root cause:
Due to objects consistency check on DEV system when object or parent do not exist in DEV system, the synchronization option via Original TR was not allowed.

Solution:
Add a button to allow the user to continue the Synchronization process at their own risk.

Synchronization

SC-784

Object modified remains locked in a released Rollout Request

Issue:
When the original transport request is added to a Rollout Request and the Rollout Request is released without synchronizing/importing the original transport first, the objects from the original transport remain locked and can not be added to a new Rollout Request.
When trying to add the object to a new Rollout Request, the message "Transport Request already waiting for import" is displayed.

Root cause:
This use case was not handled, as the rollout request should only be released after the import of the attached Synchronization requests.

Solution:
The program has been modified to ignore the object locks if the Rollout Request has already been released.

Synchronization

SC-792

RTC LOGO is not displayed

Issue:
For some customers, the RTC logo is not displayed.

Root cause:
The logos are loaded in SAP as PNG instead of as GIF.

Solution:
The RTC logos have been converted to GIF.

UI

SC-776