Detection of missing predecessors
Basics
As already mentioned in the chapter Detection of overtakers , Conigma usually automatically identifies overtakers and adds them to the import scope, to ensure that an older development does not overwrite a more recent development.
In this chapter, the terms overtaker and missing predecessor were defined as follows: An and Am are transport requests whose object lists overlap and that are located in a queue at the positions P(An) and P(Am), where P(An) < P(Am) applies. If Am is imported before An, Am is an overtaker of An and An a missing predecessor for Am.
Identification of missing predecessors
M is the set of all transport requests that are imported into a target system as part of an import container. This means that the following criteria apply to missing predecessors Al:
Ak is a transport request contained in M
Ak overlaps with a non-imported request Al, which is not contained in M and which is located further up in the queue, so for the queue positions P(Al) < P(Ak) applies
The standard behavior of an import container is that if there are missing predecessors, the import container is stopped and an email is sent to a relevant group of people, e.g. SAP Basis, Change Manager, developers, etc. In this case it should be clarified whether the preliminary import was desired or unintentional and depending on this, the follow-up activities should be planned. For example, the change request with the missing predecessor could be added to the import container, the CR with the overtaker could be removed from the import container, or the import of both requests could be performed within the same maintenance window.