Defining Targets

Transport Expresso is designed to import transport requests into all relevant clients of an SAP system in a single action.

In Transport Expresso, each group of clients within an SAP system is called a target; the properties of a target specify the following:

• The SAP system and clients that changes will be imported into.
• The behaviour of imports into the target.
• The team members who are authorised to approve changes into or out of the target.
• The properties of a target do not determine whether changes must be approved into, approved out of or tested in the target; those settings are made for each transport path. By enabling a target’s inbox on a per transport path basis, you have the flexibility (for example) to require your implementation’s changes to be approved before they are imported into a target, but to import changes from a central, global SAP development team automatically.
• The automated analysers that will run automatically (or manually) in the configured control points (ie Inboxes, Import Queues, Test Queues, Outboxes) in that target.

Targets are created and edited by ActiveControl Administrators via the Windows GUI screen configuration screen. [on the Targets & Transport Paths tab].

It is also possible for ActiveControl Administrators to open the Target directly from the Windows GUI main screen, by double-clicking on the Target.

Notes

(i) The same actual SAP system can be defined as more than one Transport Expresso target system. This can allow different processes to be controlled for the same systems. For example, if the same SAP systems are used for BAU and project changes it’s a good idea to have a separate transport path for each which then uses a different set of target systems. This enables greater control and different approvers to be setup for each process.

(ii) It is not possible to add the same Target to more than one Transport Path.