Production TOC’s

ActiveControl 7.00 introduces the ability to create Transport Of Copies (TOC) for deployment to Production.

This is something that customers have requested, as it was something they were doing previously at an SAP level to reduce the number of transports deployed in production, and by extension, to reduce the time window required for Production import.

Production TOCs are created in the TE Windows GUI. This is done by right-mouse clicking on the required transport(s) and selecting “New Transport of Copies” > “For Production”.

The new Production TOC behaves quite differently from the other TE TOC capability. Key points of note:

1. the TOC will be put in the same location as the original transports
2. the original transports are deleted from the location
3. if there is no user exit, a Transport Form is created automatically, which (i) ignores the task selections made in the GUI (ii) assigns the tasks of the original transports (iii) takes the TE Group and Type coming from /BTI/TE_TOCONFIG DEPLOYTYPEID and DEPLOYGROUPID
4. If there is a user exit, then creating and moving the TF will be handled by the exit
5. When a TOC Transport Form is deleted completely without being completed, the original transports are added back to the original location

This functionality is intended only for Production deployments, and will only work if all the transports imported in QA but not in Production are merged into a single TOC. Side effects could happen if the TOC is created earlier in the path or some transports are excluded from the TOC (and also many of the TE analysers will not work correctly)

Configuration Steps
To configure Production TOC functionality, two things are needed:

1) a couple entries must be added in table /BTI/TE_TOCONFIG in the TE Domain Controller

DEPLOYTYPEID: The “Type” to be used for the TOC Transport Form (from /BTI/TE_TYPE)
DEPLOYGROUPID: The “Group” to be allocated to to the TOC Transport Form (from /BTI/TE_GROUPS)

2) the system in which the TOC will be created as a valid source system in the path.

3) user performing the Production TOC in the Windows GUI needs to have CREATETOCDEPLOY authorisation activity.