Ansicht
Dokumentation

AIC_CM_72_POST_MIGRATION - Postmigration for Projects in the context of ChaRM

General Data in Customer Master   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Purpose

You can use this report to perform a content activation for a single project in the context of Change Request Management.

You might have missed to select the project to be In Scopefor activation in the context of Change Request Management. For you to be able to continue working with open change documents in this project in SAP Solution Manager 7.2, you can use this report to proceed.

The content activation of the project is done in the same way as the projects in the guided procedure of the Solution Documentation Content Activation. The difference is that this post migration feature does not have the context of the solution and the branch. You must enter the branch in the selection screen using the value help. The solution is then determined from the selected branch. Furthermore, you do not find logs for this activated project in the guided procedure of the Solution Documentation Content Activation. However, you can find logs in table AIC_SM72_CM_LOG.

The report checks:

• if the product systems of the logical components assigned to the project can be converted into technical systems

• if the branch exists

• if the branch is a changeable branch, which means no production branch

• if the project has an open change cycle and an open task list

• if the project has not already been activated

The report does NOT check:

• if the technical systems are assigned to a logical component group(s) in SAP Solution Manager 7.2

• if the logical component group(s) is assigned to the solution in which the project is to be activated

• if the selected branch fits to the assignment of the technical systems within the logical component group(s)

Note that these three checks must be performed manually before the post-migration report is executed. You can execute the check for the technical systems and the maintenance of the technical systems using transaction LMDB. You can maintain the logical component group(s) in the solution administration user interface, which is called from SAP Solution Manager Fiori Launchpad. Ensure that the relevant master data is maintained accordingly.

Potential issues with solution documentation integration into Change Request Management can occur in the following case:

• If you enabled change controlfor your branches, you must make all changes to solution documentation elements in this one branch, which will be referenced at the activated change documents of this project.

• If you have a dual landscape, you must select either the maintenance branch or the development branch. Ensure that the selected branch fits to the content of the transports of your change documents to avoid that you perform your software changes and your changes in solution documentation in different branches.

Also note that your project might have logical components assigned that were not migrated into logical component groups for the new solution in 7.2. In this case, a new change control landscape will be created for the activated change cycle, which does not have any logical component groups assigned. The assigned change documents of this cycle can be processed without issues. Also, the change cycle can be processed without problems. Yet, what does not work in this case at the change cycle is the feature "Redefine Landscape". If you want to use this feature in such activated project, please maintain afterwards a logical component group with the respective technical system(s) and assign this newly created logical component group to the change control landscape.

Integration

Prerequisites

Features

Selection

Standard Variants

Output

Activities

1. Select the project.
2. Select the branch.
3. Choose Execute.
   The report displays the result of the content activation for this project.

Independent of the activation result, the activation for this project is logged in table AIC_SM72_CM_LOG like all other projects that are activated in the regular content activation.

Example

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 4770 Date: 20240531 Time: 040933     sap01-206 ( 100 ms )