Show TOC

Procedure documentationDetermining Structure Changes Locate this document in the navigation structure

 

You can use a background job to determine the changed structure nodes or changes to assigned business content. To do this, select a current structure from a project or a solution and compare this structure with a previous or subsequent version of the structure in the lifecycle.

Note Note

Note that the background job compares the assignment of business content to structure elements. It identifies, for example, copied documents that are assigned to a structure node. Referenced documents or changes to business content itself, on the other hand, are not identified, such as changes to URLs, BC-Sets, and documents, or updates of CATTs/eCATTs.

End of the note.

Prerequisites

You can compare project structures copied as of SAP Solution Manager version 2.20. You can compare solution structures copied as of SAP Solution Manager version 7.0 EhP 1.

Procedure

  1. Start transaction SA_PROJECT_UPGRADE.

    • Project Administration initial screen:   Goto   Comparison and Adjustment  

    • Business Blueprint / Configuration:   Utilities   Compare Project  

    • Solution Directory   Utilities   Compare Solution  

  2. Use the input help to select a project or a solution as the starting point for the comparison.

  3. Specify where the changes are to be highlighted:

    • In the current structure of the selected project / the selected solution

    • In the comparison node of a predecessor or successor version

      If you select an immediate predecessor version as the comparison node, you can copy the attribute values from the comparison node to overwrite the attribute values in the currently-selected structure. Determine which of the following attribute values you want to copy:

      • Structure attributes (SAP and customer attributes)

      • Globale attributes

      • TBOMs of transactions

  4. Define the comparison nodes.

    These following options are available:

    • Comparison node of a predecessor version

      Select a predecessor version of a project or of a solution of an existing lifecycle phase as the source for the comparison node and the status of the business content.

      If you choose the immediate predecessor version or the Business Process Repository for the comparison, you can compare the versions of BPR structure objects, in particular:

      • You can compare the current version of BPR structure objects with the versions that you originally copied from the BPR. The background job performs the comparison using the product versions that currently exist in the project/solution landscape.

      • You can compare the current version of BPR structure objects with the version of another, landscape-dependent product version. If you select Business Process Repository as the source for the comparison node, the Landscape Product Versions pushbutton allows you to branch to a dialog box for selecting the product version. If you select Direct Predecessor and the BPR context is not unique, the system sets the Copied Originally from BPR checkbox automatically and issues a corresponding message. This message is also written to the log for the background job. If you execute the program as a background job and no unique context is found, an error message is written to the log for the background job.

    • Comparison node of a successor version

      Select a successor version as the source for the comparison node and the status of the business content. Identify a unique successor version by selecting a particular project or a particular solution into which structure objects or business content have been copied from the starting project or starting solution.

      If the successor version is not uniquely identifiable because a structure node has been copied more than once into the project or the solution, all successor versions are taken into account for the comparison.

  5. Define which tab pages are to be compared for changes.

    Note that the background job only takes into account tab pages that are marked as visible in the project administration.

    • Structure

    • General Documentation

      Note Note

      End of the note.

      In projects, documents can exist both under General Documentation and under Project Documentation. When copying structure elements from a project to a solution, these documents are summarized in the solution on the Documentation tab page. If you are comparing a solution and a project, you therefore need to explicitly select the tab page to be compared. Documents from the tab page that you have not chosen are marked as new during the comparison.

      When you compare a solution with a project, you can specify whether the comparison is to be made with the General Documentation or Project Documentation tab page for the project. You cannot compare with both tab pages simultaneously. The default setting specifies that the Project Documentation tab page is compared. To allow you to switch the comparison from one tab page to the other, a Switch Document Tab pushbutton is available in the Compare and Adjust dialog box. This allows you to switch between the two document tab pages for the project.

      If you compare a solution with the Project Documentation tab page for a project as a background job, the dialog box displays the differences to the Project Documentation tab page for the project. To run a comparison with the General Documentation tab page for the project, choose Switch Document Tab.

      When you compare a project with a solution, you can specify whether the comparison is to be made with the General Documentation or Project Documentation tab page, or both.

    • Project Documentation

    • Transactions

    • Configuration

    • Development

    • Test Cases

    • Learning Materials

    • End User Roles

    • Business Functions

  6. (optional) Specify users for which comparison mode is to be active.

Result

The system reports when the background job has been completed.

You can use transaction SM37 to display the comparison log with the number of detected changes.

If comparison mode is active, changes to structure nodes and tab pages are highlighted with icons when you call the transactions Business Blueprint (transaction SOLAR01), Configuration (transaction SOLAR02), or Solution Directory (transaction SOLMAN_DIRECTORY).