Scope of import
The figure shows the possible options for "Scope of import"
The following table describes the individual options for "Scope of import".
Undefined | Default settings are used. In case of Conigma import containers this is "Relevant parts of request list and relevant overtakers (OLA)". |
Relevant parts of request list | Transports contained in the request list that have not yet been successfully imported into the target system are imported. Overtakers are not considered. |
Full request list | All requests contained in the request list are imported. Overtakers are not considered. |
Relevant parts of request list and relevant overtakers (OLA) | Transports contained in the request list that have not yet been successfully imported into the target system are imported together with relevant newer (already imported) transport requests for the same objects. (Overtakers are taken into account) Overtakers covered by newer overtakers are not imported. |
Full request list and relevant overtakers (OLA) | All requests contained in the request list are imported together with relevant newer (already imported) transport requests for the same objects. (Overtakers are taken into account) Overtakers covered by newer overtakers are not imported. |
Full request list and all overtakers | Transports contained in the request list that have not yet been successfully imported into the target system are imported together with all newer (already imported) transport requests for the same objects. (Overtakers are taken into account) |
Available request list and relevant overtakers (OLA) | All requests in the request list that still have the appropriate status in the import queue of the target system are imported together with newer relevant (already imported) transport requests that affect the same objects. (Overtakers are taken into account) Overtakers covered by newer overtakers are not imported. |