SmartChange 2019 SP1 HF06

Enhance TM>Systems and groups>General check with Security setting for RFC

Issue:
An additional check is needed in TM>Systems and groups>General check for the RFC destination:
If system parameter RFC/callback_security_method is set to level '3' or the whitelist is active, the TM RFC destinations must have the RFC Callback Whitelist maintained.

Solution:
The program has been enhanced.
The warning 'Whitelist should be maintained for RFC destination &' will be displayed in the log.

Configuration, UI

SC-464

Enhance TM System Queue logging

Issue:
To offer better troubleshooting of the System Queue, an additional option to log the incoming traffic to a System Queue is needed.
Information about the system, host, client, etc. where the system queue import runs should be available centrally in the TM server.

Solution:
The required log information is stored in the new table /RTC/TM_RFC_LOG centrally in the TM Server.
The System Queue report has been enhanced in order to save data into the table.

Configuration of the new feature:
In order to activate/deactivate the storage of the data in the log table, table /RTC/TM_OPT has been enhanced with two new fields:

• RFC_LOG_INACTIVE - if 'X', the logging is deactivated (information is not stored in the log)
• RFC_LOG_DAYS - number of days to be kept in the log

As the default setting, the log is ACTIVE and 10 days are kept in the log.

Structure of the log content:
For a System Queue run, in the /RTC/TM_RFC_LOG table the following data will be saved:

• one entry with information from the target system (from where the System Queue starts)
• one entry for each imported TR with information from TM server

The SID of the target system will be specified in all the entries in the field REFSID.
The non-key fields represent information from either TARGET system or TM Server.

Configuration, Queues/Proposals

SC-481

Enhance the creation/modification of TM RFC destinations: automatic assignment of RFC Callback Whitelist

Issue:
During the automatic creation of an RFC destination for TM via TM>Systems and Groups>Add system or transaction /RTC/TM_INI, the RFC callback whitelist should also be automatically maintained.
The RFC Callback whitelist is mandatory for Transport Manager RFC destinations if the security level is set to level '3'. The level can be checked via T-code RZ11, parameter RFC/callback_security_method.

Solution:
The programs have been enhanced.
When the TM RFC Destinations are Created/Modified the corresponding WhiteList is automatically updated with the standard entries required for TM functionalities:

Called FM | Callback FM
/RTC/TM_GET_TRFILES | EPS_GET_FTP_SYSTEM_INFO
/RTC/TM_GET_TRFILES | EPS_OPEN_INPUT_FILE
/RTC/TM_GET_TRFILES | EPS_READ_BLOCK
/RTC/TM_GET_TRFILES | EPS_READ_TEXT_BLOCK
/RTC/TM_GET_TRFILES | EPS_CLOSE_FILE

Configuration

SC-571

Enhance SM>Systems creation/check functionality with RFC Callback Whitelist assignment/validation

Issue:
During the automatic creation of an RFC destination for SYM via SYM>Systems>Add a new system (DEV or MAINT) or when checking/reconnecting an existing system pair (DEV or MAINT), the RFC Callback Whitelist should also be automatically maintained/validated on the created/checked SYM RFC destinations.

Solution:
The program has been enhanced.
The process has been included in the screens where the systems are added, once "Create/Check RFC connection is clicked". Additional feedback from this step is available in the following "Log connection" screen.

The corresponding whitelist is automatically updated with the standard entries required for SyM functionalities:

Called FM | Callback FM
/RTC/SA_COPY_TR_FILES|EPS_GET_FTP_SYSTEM_INFO
/RTC/SA_COPY_TR_FILES | EPS_OPEN_INPUT_FILE
/RTC/SA_COPY_TR_FILES | EPS_READ_BLOCK
/RTC/SA_COPY_TR_FILES | EPS_READ_TEXT_BLOCK
/RTC/SA_CHECK_OBJECTS | /RTC/SA_GET_UPDATE_RECORDS

Configuration, UI

SC-573

Code security enhancement for Code Profiler test case "Missing AUTHORITY-CHECK in RFC-Enabled Functions"

Issue:
Code profiler tool highlights the following security issue in the SmartChange coding:
"Missing AUTHORITY-CHECK in RFC-Enabled Functions"

Root cause:
This Code Profiler test case checks whether an RFC-enabled function module fails to perform specific authorization checks for its business logic.

Solution:
SmartChange coding has been enhanced to perform additional authority checks on the calling user for the RFC-Enabled Functions. The user must have the authority to execute specific SmartChange function modules - Authority Object ZRTC_COM, Activity RF - Remote SmartChange FM execution (authority field /RTC/SC_AC).

Security

SC-529

Code security enhancement for Code Profiler test case "Missing AUTHORITY-CHECK in Reports"

Issue:
Code profiler tool highlights the following security issue in the SmartChange coding:
"Missing AUTHORITY-CHECK in Reports"

Root cause:
This Code Profiler test case identifies reports that do not have an explicit AUTHORITY-CHECK.

Solution:
SmartChange coding has been enhanced to perform additional authority checks. The user must have the authority to execute specific SmartChange reports - Authority Object ZRTC_COM, Activity RX - SmartChange Report Execution (authority field /RTC/SC_AC).

Security

SC-565

Shortdump GETWA_NOT_ASSIGNED when expanding the collision tree in TM Monitor>Quality Assurance popup

Issue:
When trying to approve a transport request in TM Monitor, possible collisions with other requests are displayed in the Quality Assurance popup. By trying to expand the collisions tree further to see more details, the program ends with the short dump GETWA_NOT_ASSIGNED (ABAP Program /RTC/SAPLTM_QA).

Root cause:
There seems to be a miscalculation of the collisions sometimes while adding an external transport into TM. Therefore, the program is trying to display inconsistent data and it dumps.

Solution:
If this situation occurs, a correction of the calculation is necessary achieved by re-running the collisions checks.
Two ways are available:

• Online (QA->collisions)
• Offline (schedule job /RTC/TM_RECALC_COLLISIONS without parameters).
  It is recommended to perform this step while the TM is low loaded. While the calculation of the collisions is running, restrictions on approvals may occur.

Also, the program has been corrected to catch the error. The user will receive the error message "Error retrieving data. Please recalculate the collisions" with additional long text information on how to proceed for the recalculation.

Approval, Quality Assurance

SC-578

Wrong Notes-Symbol in TM Workflow Monitor for external transports

Issue:
When manually adding a transport request in the TM Workflow Monitor, the wrong symbol is displayed in column 'Notes'.
The external transports appear to have Notes assigned to them, even if they don`t have any.

Root cause:
Programming error.

Solution:
The program has been corrected.

UI

SC-368

TM Monitor >"RC Final" column displays red icon, when no final return code value exists

Issue:
In the TM Monitor, if the value for column "RC Final" is empty, then the icon red is displayed.

Root cause:
Programming error - the empty value was not taken into consideration.

Solution:
The program has been corrected. If 'RC Final' is empty, no icon will be displayed.

UI

SC-570

Transaction /RTC/TM_INI in client 000 does not consider the checkboxes on the selection screen

Issue:
In transaction /RTC/TM_INI, in client 000, some input fields like SID, System number, Hostname are mandatory even if the checkbox "Create RFC destination" for which they are needed is unchecked.

Root cause:
Programming error

Solution:
The program has been corrected.

UI

SC-572

TM/SM integration - External TR's selection on TM is not working when checking SyM

Issue:
In the TM Monitor, with TM/SM integration configured, external TR's selection is not working when checking SyM.

Root cause:
The check was done on the first three letters of the transport request. External TR without that SID configured as SyM pair shows 'No systems pairs to analyze this request'.

Solution:
Once the SID of TR is not found as pair, display all the system pairs available on the screen to choose the pair to be analyzed.

Synchronization, UI

SC-582

Update Logo in transactions for SmartChange 2019

Issue:
With SC2019 the Realtech logos have changed. These have not yet been included in the following transactions:
/RTC/TM_CUST
/RTC/TM_LIB_REPORTING
/RTC/SA
/RTC/TM
/RTC/TMC
/RTC/TMCADM
/RTC/TMCRSCHED
/RTC/TMR

Root cause:
Programming error.

Solution:
All logos have been replaced.

UI

SC-546

Wrong User (RequestOwner) shown in the Sync Request Tree

Issue:
Owner of the Rollout request does not get updated on SYM if the owner of the TR is changed in standard transactions.

Root cause:
No checks on the owner of the TR were done.

Solution:
Include a validation for the owner of the TR.

UI

SC-579