REALTECH SmartChange SP3

SC-880

Column name changed form "Transport request" to "Request"

Due to length reasons, the column name "Transport request" was changed to "Request".

SC-873

Enhance TMC with approval list

With this feature, all waiting approvals for selected TM servers can be displayed in the TMC.
A new button is available to switch between the approval list and the alert list. Depending on the monitor setting, the approval list will contain only selected approval types.

SC-856

Permit customer adding of User-Exits

Allow customers to add CUSTOMER EXIT TYPES beside the standard Realtech types. The restriction: Custom added CUSTOMER EXIT TYPE name should start with 'ZZ'.

SC-849

Exclude transports in history when adding transports to TM manually

When adding transports to TM manually, in the list of transport also transports that are in history will be shown, the list can become very large and finding the transports that you want will be very painful. Therefore a check-box to enable or disable the selection from history was added in the selection screen.

SC-826

Customizing enhanced to consider exception objects when creating a Synchronizing Request

The user has the possibility to define Exception objects in the SyM Customizing. These objects are excluded from the analysis.
With this new feature, the status of the object (ex. "Excluded") is shown in the screen 'Create Customizing sync request', as displayed in the Customizing Object Comparison screen. The user has now the option to filter by excluded objects or to delete excluded objects.

SC-804

Update Jira after transport request was switched automatically to the next level

This function performs an update in the Jira SmartChange Panel after the transport request has been automatically moved to the next level. In case of an automatic content approval, the approval data is also updated.

SC-803

Update Jira after release transport request w/o add to TM Workflow

This function performs an update in the Jira SmartChange Panel at release of transport request also when is not added to the Transport Management.

SC-788

Replacing obsolete function modules

Issue:
PANAYA tool detected obsolete function modules.

Root cause:
SmartChange code contains calls to standard SAP function modules which are marked as obsolete.

Solution:
The list of obsolete function modules was analyzed. Most of them have been replaced according to SAP suggestions, and the rest have been marked for further review.

SC-679

Allow Transport of Copies to be assigned to an External ITSM issue ID

With this new feature, Transport of Copies (ToC) can now also be assigned to an external ITSM issue (ex. Jira), same as Workbench or Customizing transport requests.
Because the link between ITSM issue and transport request is stored in SAP transport request attributes, this functionality can only be activated if standard SAP allows the ToC to have SAP attributes attached (SAP NetWeaver version greater than 7.50 or S/4 HANA systems).
In order to activate this feature, /RTC/TM_IF_CONFIG > Global Activation setting, TR_TYPE must be set to 'A' (All).

SC-658

Deploy application roles to development systems via TM Update assistant

With this feature, the TM Update assistant will apply the application roles transport to all the development systems.
The queue generation is based on the tm_upd.txt file. The new code, SDEV, determines the import in all development systems configured in TM > Global settings > Standard systems, for all active clients with the role 'Development' or space.

SC-597

Enhance TMC approval and alert list with custom attributes

Possibility to display TM attributes as columns in the alert and approval list of TMC.
A new transaction /RTC/TMC2ATTRIB exists to configure the TM attributes to be displayed for all or for a specific TM server. For configuration, the following fields are to fill:
- TM-Server SID
- TM Attribute Name
- Field name (optional - if not filled, then the attribute name will be used as the field name in ALV)
- Active (used to activate the display of the attribute)
The fields should be unique and distinct from the fields of structure /rtc/tmc_alerts_out_s.

SC-370

Synchronisation of Translation Object

This feature allows the synchronization of translation objects via Transport Requests.

SC-69

Filter in the TM Monitor to select all TRs with intersection of 2 attribute-values

With this feature, the user can filter in the TM for Transport Requests with more than one attribute. The TM Attribute filter can be set by using the “TM Attribute” button in the filter area. Using the “TM Attribute” Button a pop-up is displayed to add TM attributes entries to a list. The TM-Attribute name is mandatory. The value field is not mandatory, if this is empty or '*' then all the Transport that have the inserted TM-Attribute name will be selected. The value field is key-sensitive and does not work with value + '*' like 'REALT*'.

SC-949

TM: Dump trying to delete dependencies

Issue:
Short Dump CALL_FUNCTION_PARM_UNKNOWN in ABAP program /RTC/SAPLTM_SERIAL happens when trying to delete a dependency between two transport requests in TM Monitor.

Root cause:
Programming error.

Solution:
The program has been corrected.

SC-948

TM: German translation missing for dependencies description

Issue:
In TM Monitor, the German translation is missing for the description of the dependencies types.

Root cause:
Programming error.

Solution:
The program has been corrected.

SC-861

System Locked even when Lock is not active

Issue:
If a system is locked and a new client is added, this client will be added as locked. After the system is unlocked, the client will remain locked and the system acts like a locked system.

Root cause:
Programming error.

Solution:
The program has been corrected.

SC-848

Project/Destination short text is not displayed all the time

Issue:
Project/Destination short text is not displayed all the time.

Root cause:
Programming error.

Solution:
The program has been corrected.

SC-847

Empty Transports freezes System Queue

Issue:
When importing an empty transport request via TM>System Queue, it sometimes takes up to 1 minute for the System Queue to show the result. An empty transport freezes the System Queue.

Root cause:
Programing error at lock check.

Solution:
The program has been corrected.

SC-815

Short Dump MESSAGE_TYPE_X when filtering Rollout

Issue:
When adding a filter to Rollout Request by owner, it creates the DUMP MESSAGE_TYPE_X in program CL_GUI_CFW====================CP on the DEV system.

Root cause:
Programming error.

Solution:
The program has been corrected.

SC-789

Customizing objects wrongly not displayed in the tree with filtering options

Issue:
When filtering in the initial customizing selection screen, if all selected customizing objects have not been analyzed, nothing is displayed.

Root cause:
Programing error.

Solution:
The program was changed with an additional check: if at least one of the selected objects is marked to be excluded from the analysis then the information is displayed.

SC-677

Authorization failed due to missing authorization role during SyM Customizing analysis

Issue:
Sometimes, SyM Customizing analysis fails due to missing authorization for the user.
Depending on objects being analyzed, different failed authorization checks are registered, for example when creating the CUST initial job.

Root cause:
Missing authorization in SyM Roles.

Solution:
Authorization role /RTC/SA_CON updated with:
* S_RFC - RFC_name : FUNCTION_EXISTS, SCCR*
* S_TABU_NAM - Activity: 02, 03
* S_TABU_CLI

SC-670

An /RTC/ authorization role is missing to allow creation of Smart Connection

Issue:
When adding a system to the SMART controller, the step of creating the RFC back from the added system to the SMART console fails. There are missing permissions to create an RFC when testing with user ZRTC4_TM_ADM.

Root cause:
The user does not have the necessary rights to create the RFCs.

Solution:
The authorization object S_RFC_ADM needs to be added to the user, with activity 01 (Add or Create) and '*' for 'Logical destination (specified)'. This should be added in 000 clients in all the systems that are added to /RTC/Smart.
Role /RTC/TM_RFC_HIGH has been enhanced with this authorization. Therefore, user ZRTC4_TM_ADM can be used as the login user for the Smart RFC destinations that are created when adding a new system.