The product versions of systems in a logical component can differ during an upgrade, making the logical components inconsistent.
Recommendation
You should only increment the product version when upgrading a logical component in the Solution Manager System Landscape (SMSY), when you have upgraded all production systems.
Case A:
The product versions of the system and the logical component do not match
Check that the product version is correct.
There are the following cases:
The system is being upgraded:
Ignore the inconsistency until after the upgrade, and then resolve the inconsistency
The system is not being upgraded:
To resolve the inconsistency, assign the same product version to the logical components and all systems used in it.
Case B:
The logical component is internally inconsistent
A logical component can be inconsistent if not all main instances exist in all product versions.
Note
Existing main instances have the Main Instance Exists flag in the product version possible entries help.
Example
The main instance E-Selling for product SAP CRM exists only in the product version SAP CRM 4.0. If a logical component contains the main instance E-Selling with another product version than SAP CRM 4.0, z.B. SAP CRM 3.0, this logical component is inconsistent.
Use another logical component, with a main instance which exisits in this product version:
Create a logical component
Choose an existing main instance for this logical component.
Generate a where-used list for the old, inconsistent logical component.
The Solution Manager shows in which system groups of projects and solutions the logical component is used.
Replace the old logical component with the new one in these system groups, with Replace Logical Component.
Delete all systems from the old, inconsistent logical component.
The old logical component is no longer used. The inconsistency flag in the overview tree (exclamation mark) disappears.
No comments:
Post a Comment