ActiveControl includes the ability to create Transport of Copies (TOC) of existing transport(s) to push to their test systems. This avoids the need to release the original transport until testing is complete, and can significantly reduce the number of transports moving beyond your test system to Production.

To enable the automated TOC functionality within ActiveControl requires the following configuration in the Domain Controller:

Step Details
1. Use table /BTI/TE_TOCONFIG – add a configuration entry depending on your requirements.

The configuration flags are as follows:

  • CREATELEVEL allows you to dictate at what level the TOCs are created at. E.g. if you have two Transport Forms that are part of two different Projects, configuring CREATELEVEL = P will result in two separate TOCs being created.
  • SELECTLEVEL
  • REMOVEONOVERTAKE
  • DELETE_EMPTY will remove any SAP Tasks which contain no objects.
  • AUTO_RELEASE will automatically release any unreleased SAP Tasks that are included in the Transport(s) that you are creating a TOC for.
  • OPEN_NEW_TASKS will automatically create new SAP Tasks assigned to the same consultant as those included in the Transport(s) that you are creating a TOC for.
  • STOP_TOC_IN_TOC will prevent a TOC being created of a TOC
  • COPY_CUSTFS will result in any custom field values on the source Transport Form being copied across in the TOC, when a TOC is being created of a single source Transport
2. Use table /BTI/TE_VAUTOCON to set up the conditions in which your TOCs are created, either automatically or manually by ActiveControl.

Numerous online Knowledge Articles detail various common configuration examples, including: <>BR
  • TRAVEL trigger – Configuration example available here
  • APPROVE trigger – Configuration example available here
  • MANUAL trigger (against individual SAP Tasks) – Configuration example available here
  • RULES ENGINE filtering – Configuration example available here


p(banner tip). Further information – including configuration screenshots – on setting up ActiveControl TOCs can be found in this online Knowledge Article.


TOC object splitting

As part of the ActiveControl ‘Transport of Copies’ functionality, it is possible to split out the original transport into several separate TOCs based on the objects contained within the original transport. Setting up this object splitting is a two step process, as follows:

Step Activity
1 Create Groups for each of the TOCs that you want to create by populating table /BTI/TE_TOCOBGRP



In above screenshot, we intend to split out each transport into two TOCs, one for BRF objects, and one for everything else

2 Allocate what objects you want to allocate to each groups by populating table /BTI/TE_TOCOBJ



In above screenshot, we intend to create one TOC for the various BRF related objects, and one for everything else



Changing the naming convention of TOCs

When a TOC is created, the default TR description of the TOC will match that of the original SAP Transport. It is possible to change the convention (eg to include the word “TOC” or suchlike at the start of the description. Please refer to this online Knowledge Article for details on how to do this.

Manual TOC creation

The typical process for Transport of Copies within an ActiveControl workflow is that the first TOC of an original unreleased transport is created automatically, and then subsequent TOCs to incorporate fixes are created either manually or automatically.

Transport of Copies can also be manually be created via the individual Transport Form or the Global View within the ActiveControl Web Platform.

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment