Import Schedules

An Import Schedule defines a list of days and times when transport requests should be imported automatically.

When an Import Schedule is assigned to a target, ActiveControl automatically creates a background job in the Domain Controller that will import transport requests that are currently within the target’s import queue.

The name of the automated import job is TE_SCHEDULED_IMPORT_SID_nnnn, where SID is the SAP system ID and nnnn is an internal number for a target. These background jobs should not be maintained or deleted from directly within SAPGUI.

ActiveControl ensures that the background job always executes according to the current version of the transport schedule. This includes deleting the aforementioned background job if the transport schedule is no longer assigned to the target.

Configuration

Transport Schedules are maintained by ActiveControl Administrators via the Import Schedules app tile. There are three steps to creating an Import Schedule:

1. Each Schedule has a description and optionally the user ID that the import should be scheduled under.
2. The timings are allocated to the Schedule, and then dragged to the right-hand window.
3. Any restrictions can be allocated to the Schedule.

Figure: Import Schedule configuration screen.

*Basis Technologies recommend to use a dedicated batch user in your Domain Controller for handing Transport Schedules. This batch user – which we typically call AC_BATCH – needs to have /BTI/TE:CTS_ADMIN_USER, /BTI/TE:CTS_RFC and /BTI/TE:COMP_ADMIN_ROLE roles assigned to it.

*As well as the AC_Batch user, it is also necessary for an RFC to be created in the Domain Controller, that points back at itself. (eg TRANSPORT EXPRESS [SID], where SID is the System ID of the Domain Controller.

!Please note that maximum limit of 64 import schedules can be configured within ActiveControl. This is unlikely to be an issue at the majority of customers, but it is worth being aware that housekeeping should be done to delete Import Schedules that are no longer used, to avoid them building up and potentially reaching the upper 64 limit. Addititional information on the error relating to this can be found in this online Knowledge Article.