‘Transport Import Date Analysis’ (0072) is an informational analyser that aims to provide Change & Release Managers with an indication of when Transports could be deployed into Production, based on the object contents and the usage of the top level objects (ie Transactions, Programs) to which those objects roll up.
The output of the Analyser will present three suggested time windows for deploying the Transport(s) in the following 7 day period, based on when the top level objects were not used in a previous time period (eg 30 days) as indicated by a production usage data retrieval program.
Ultimately, the aim of this Analyser is to help SAP Teams move to more Agile deployments – where transport deployments can be done more frequently based on actual usage of the top-level objects impacted by the objects in the transports to be deployed – and not just based on the more traditional time-window based deployment process (ie where it is not expected that Business users will be on the system).
|(Optional) Can be used to exclude certain day(s) from the results. Ie if Customer does not want the Analyser to propose deployments on Weekends for example. This is done via a new 00NN_EXCLUDE_DAY parameter in table /BTI/TE_TVARV in the Domain Controller.
|(Optional) Can be used to exclude certain objects from the calulation. These are configured in existing /BTI/TE_ANLEXC table also being delivered as part of ActiveControl 9.00.
|(Optional) Can be used to exclude certain time windows from the results. Ie if Customer has a policy of never deploying between certain hours (eg 09:00 – 13:00) then this can be defined. This is done via a new 00NN_EXCLUDE_TIME parameter in table /BTI/TE_TVARV in the Domain Controller.
|(Mandatory): Enter the number of levels that the calculation should roll up to see the Top Level Objects.
|(Mandatory) Target Number for the production target ID (where the usage data is to be retrieved from)
More information on this new Analyser – and instructions on how to configure it – can be found in this online Knowledge Article. The original Change Notes for this new analyser can also be found here and here.