Many Basis Technologies customers use ActiveControl Merge to synchronise parallel N+n development tracks, or to get relevant ECC change into S/4HANA as part of a S/4HANA brownfield migration.
Over the years, increasing numbers of these customers requested that it be possible for any hardcoded transport dependencies defined in the Advanced Options tab of a Transport Form to be copied across as part of the 1:1 Merge process, to ensure correct sequencing when deploying Merge TOCs.
Configuration Steps
Enable the For 1:1 merges, copy over dependencies to merge Transport Form configuration option if you want to benefit from this new optional capability as part of 1:1 Merge.
Figure: New option to bring across Transport Dependencies into the Merge TOC Transport Form, as part of 1:1 Merge.
Post your comment on this topic.