Creating a maintenance version

  1. Start the Maintenance Versions (ttcmt1100m000) session.

    A maintenance version represents a version of the Infor LN software that requires maintenance. It may include different versions of the standard software, localizations, extensions, or customizations. Examples are: 41b, B5bsch, B6abcl. This session is needed for recording Update Sets.

  2. Start the Merge Code by User (ttcmt1101m000) session.

    This session is used to register a merge code for each user. CMT requires a merge code to merge scripts. This code is automatically generated during script updates and ensures that concurrent update actions using the same merge code do not interfere with one another.

  3. Start the Update Sets (ttcmt1110m000) session.

    An Update Set contains sources that have been modified, typically for a specific change such as a customization or bug fix. These sources are linked to the update set. When a source has been fixed in a version, an update set must be created before the modified version can be copied over the original version. Only update sets associated with maintenance versions in the current environment are displayed.

  4. Start the Connect Scripts to Update Set (ttcmt1210m000) session.

    This session saves the two versions of the sources in the “Directory for Update Sets”.

  5. Start the Update Script using Update Set (ttcmt1220m000) session.

    This session automatically applies the modification to another version. It can only run if the update set was created from the maintenance version where the modification originated. Additionally, a merge code must be registered for the user performing the merge.

    This ends the process of running a merge with an update set. If you want to replicate update sets between different BSE environments, use the Replicate Maintenance Versions (ttcmt1200m000) session.