|Require transport forms to be assigned to related tasks|| When a transport form is completed for a transport request, it is always possible to assign the transport request to one or more tasks, such as a request for a new report or a logged production support problem.
Tasks provide greater visibility of related transport requests and associate technical changes with business requirements. Tasks are necessary if test results are to be entered.
Enable this option to prevent a transport form from being saved if the related tasks section has not been maintained.
|Allow team members to delete transport forms of transport requests that have been imported||By default, in order to avoid losing transport history, only an administrator may delete the transport form of a transport request if the transport request has already been imported into some target systems. Enable this option to override this behaviour.|
|Configured testers only to complete testing|| When this option is enabled Transport Expresso will only allow users allocated as testers in the Task to “Save and Approve” testing. This will also validate testers assigned to specific systems and system roles.
If not set anyone can complete the testing for a task.
Note: In all cases users must be allocated with the TESTAPPROVE activity (Authorisation Object: Y_TE_TASK – Task Activities) to allow them to “Save and Approve” testing.
|Enable “Add to Control Point” function|| This option switches on the “Add to Control Point” functionality that allows transport forms to be assigned to control points in the transport path. This can be an inbox, outbox or test queue as required.
This is used when a re-approval is required for the relevant transports.
|Cache remote transport data|| This option enables the caching function that stores details of remote transports on the domain controller. This means that Transport Expresso does not have to make RFC calls to the remote systems to obtain the transport data.
Performance is therefore improved when accessing transport requests without a transport form and also when viewing transports in control points.
Note: Once switched on the Transport Expresso GUI will need to be closed and re-started for the caching to take effect.
|Hide Transport originating in ‘hidden’ systems||This option will not show transports if the target is set as hidden|
|Request password re-entry on Approval||This option allows TE customers to specify whether password must be re-entered during any approval,. for increased security|
|Automatically delete SAP transport buffer after transport import||This option can be used by those customers that do not want to leave the SAP transports in the STMS import buffer after they have been imported via Transport Expresso|
|Auto-generate Task Reference with prefix:||This option can be used by customers that want TE Business Tasks to be given an automatically generated Reference – preceeded by the configured three character prefix|
|Analysis Mode|| Select whether you want to
(i) Disable cross path conflict checks
(ii) Enable cross path conflict checks for non-hidden Targets
(iii) Enable cross path conflict check for all Targets
This is where you specify whether you want the TE Conflict Analysis Checks to only look down the path in which you are doing the analysis, or alternatively analyse all paths (based on the system you are in and its allocated target role etc). The default value (and generally what it should be set-to for most TE customers) is: “Enable cross-path conflict checks for all targets”. This ensures that any conflicts are picked up in the situation where multiple TE paths are being used by a TE customer for the same SAP system, and also when a user has manually set cross-system/path dependancies (e.g. a BW transport on an ECC transport etc.). Customers that have a lot of hidden/legacy systems/paths set up in TE might want to exclude the hidden systems to help the performance of the analysis checks, but as a general rule, no TE customer should ever really need to disable the cross path conflict checks completely.
|Planning Status Calculation||If more than one planning status could be applied to a task, this configures which one the system should assign. Either the one with the earliest sequence or the one with the latest sequence|
|Deployment Status Calculation||If more than one deployment status could be applied to a task, this configures which one the system should assign. Either the one with the earliest sequence or the one with the latest sequence|
Non-SAP Deployment and Manual Activities
|Non-SAP Deployment and Manual Activities||Specify what system where empty ‘dummy’ transports for Manual Activities are created. These transports will not be imported anywhere|
|Currency||Allows TE customers to specify the primary reporting currency within the organisation, for some optional meta-data / reporting|