REALTECH SmartChange SP6

The odata for quality aspects has been enhanced to allow the selection of multiple transports or packages.

Example:

/sap/opu/odata/RTC/TM_GW_SRV/QA_TM_TRSet?$filter=(Trkorr eq 'MT1K900356' or Trkorr eq 'MT1K900360')&$expand=NavToCollisions,NavToCritObj,NavToDependency,NavToSpecialAspects

Approve multiple transports or packages.

If the usergroup is not provided then all the usergroups where the current user is authorized will be approved for the specified approval type,

Two additional parameters are added:

• ApproveOneGroup - if the value is true then the “Usrgroup” is ignored and will be approved first usergroup where the current user has authorization.
• IgnoreParams - ignore if the selected transports are in different levels

Call example :

URL: /sap/opu/odata/RTC/TM_GW_SRV/TR_ApproveSet(Trkorr='MT1K900089,MT1K900447')

Body:

{
  "Approve" : "R",
  "ApprovalType" : "C",
  "Usrgroup" : "CONS",
  "ApproveOneGroup" : true,
  "IgnoreParams" : ""
}

The OData project /RTC/TM_GW has been enhanced with a new service for retrieving a comprehensive list of CTS Projects across various systems and clients. This service allows users to specify system and client pairs directly in the URI filter, facilitating targeted queries.

Example Usage:

• HTTP Method: GET
• URI Example: /sap/opu/odata/RTC/TM_GW_SRV/CTS_ProjectSet?$filter=SysClient eq 'MT1/100' or SysClient eq 'MT3/200'

The previous error message was updated to include more context-specific information when the role /RTC/SC_INTEGRATION is missing. The updated error message now includes the system ID and client of the target system, e.g., "You are not authorized to logon to the target system (MT1/100) (error code 1002)."

This specific error code, 1002, indicates a failure in trusted system logon due to missing S_RFCACL authorization in the target system. For further troubleshooting, refer to SAP note: https://me.sap.com/notes/0000320991 - Error codes during logon (list).

The latest update introduces a new feature that enables users to retrieve the SAP session cookie when logging into the SAP Transport Integration App. This enhancement allows users to access the session cookie even when the parameter icf/set_HTTPonly_flag_on_cookies is set to 0. The security cookie information is sent to the external application at sap logon.

The latest update introduces the ability to capture and display external user information when transport requests are approved via the OData service. Previously, the external user details were only recorded in the Action Log of the transport request. With this enhancement, the approvals table is now extended to include an additional field for storing the external user information. This data will be populated whenever available, providing improved traceability and visibility into the approval process. Furthermore, the approvals detail tab in the user interface has been enhanced to display the external user information, enabling users to easily view and track the approvers involved in the transport request lifecycle.

The Authorization Object S_PROGNAM (Generic Programm Start) was added to /RTC/TM_RFC_HIGH role.

Starting from S/4 2021, SAP introduced an additional authorization check for job scheduling using the authorization object S_PROGNAM. This change ensures enhanced security and control over job scheduling processes. To accommodate this requirement, the authorization object S_PROGNAM (Generic Programm Start) has been added to the role /RTC/TM_RFC_HIGH. This update enables with the appropriate permissions to successfully schedule jobs without encountering authorization issues.

To support the development of common core functionalities between TM and SA, the naming convention /RTC/SC* will be utilized. Consequently, the TM communication roles have been extended to include /RTC/SC* objects alongside /RTC/TM*. The roles /RTC/TM_RFC_LOW, /RTC/TM_RFC_MEDIUM, and /RTC/TM_RFC_HIGH have been updated accordingly.

• Authorization objects: S_DATASET
  • PROGRAM: /RTC/SAPLSC_*

The /RTC/TM_ALL role has been enhanced to include authorization for the TM Integration Framework. This improvement allows users assigned to the /RTC/TM_ALL role to access and utilize the functionality provided by the TM Integration Framework seamlessly. By incorporating this authorization within the standard REALTECH role, users can now leverage the Integration Framework without the need for creating custom roles.

A new feature has been implemented to enhance the tracking and visibility of transport requests within the Transport Management (TM) History. When a transport request is moved into the TM History, the system will now update the "Change Date and Time" field in the transport requet details with the current date and time. This improvement allows users to easily identify when a transport request was last modified or moved into the history

Enhanced Visibility of Original Transport Requests for Transport of Copies (ToC). In the latest update, users can now easily trace the origin of a Transport of Copies (ToC). When viewing the details of a ToC entry. The system will display the original transport request from which the ToC was created. This enhancement improves visibility and traceability, allowing users to quickly identify the original transport requests.

The Transport of Copies (ToC) functionality has been enhanced to support selection at the system level. The ToC process has been optimized to handle multiple transport requests. When multiple requests are selected for ToC, the system will split the ToC on the following criteria:

• Transport Requests with different System IDs and Clients will have a separate ToC generated for each unique combination of System ID and Client.
• Transport Requests with different project or destination assignments will continue to be handled as per the existing implementation.

With these enhancements, the ToC button will now be available at all tree levels, including the system level, providing greater flexibility and convenience for users.

When a transport request (TR) is created in an ITSM system or SAP with a CTS project specified, the CTS project information is not displayed after the TR is updated in the ITSM system.

The program has been corrected.

In previous versions, uploading files through TM_UPDATE was not working when the value of parameter REJECT_EMPTY_PATH was set to ‘ON’.

The issue has been addressed to ensure that uploads via TM_UPDATE function correctly, regardless of the REJECT_EMPTY_PATH setting in new SAP releases. The program has been corrected.

In previous versions, after uploading a tmp_upd file using the TM Update Assistant, the message displayed was incorrect, stating "Transports were successfully uploaded" instead of the accurate "Update file was successfully uploaded."

The program has been corrected.

When multiple transports are added to TM and some of them are not allowed in the selected project and destination the error is displayed but the transport is assigned to the wrong project and destination.