No match

In the case when the amendment was initiated from a version structure, and the version is the only version of the parent, and there are no parent matches to the modified structure, the PCN will be kept for the modified structure.

Exact match

Independently from which level of the tree was the amendment initiated (parent, version or lot level), if there is an exact parent match, a the match list with the match(es) will appear. Even though it is possible to have a match list with several matches, the exact match will be the very first in the list. In this case only the Accept option (no other options at the rest of the matches) will be available at the exact match, or the amendment process can be cancelled by closing the match list.

If the exact match is accepted, a Summary window appears reporting the eventual creation of a new version and the movement of all the lots from the original tree to the accepted tree. If the accepted PCN doesn't contain the version from the original tree, a new version will be created and all the lots from the original tree will be moved under it. The original tree will be kept the empty version (containing no lots).

2D, tautomer and 2D&tautomer match

In case of 2D, tautomer or tautomer&2D matches (if exact match is not available), three options will be available: unique, accept and replace.
E.g when amending a compound on version level to (5S)-5-methylpiperidin-3-one, having (5R)-5-methyl-1,2,5,6-tetrahydropyridin-3-ol (CXN29) as a tautomer&2D match, unique, accept and replace options are available (Figure D2).

Figure D2. Match list with three match actions in case of VLA