Names in HOPEX SAP Blueprint
Object names are managed through two different attributes:
• HOPEX Name
• SAP Name
Managing two attributes in HOPEX:
• Facilitates keeping SAP names and using different names in HOPEX
• Follows the rule of name uniqueness in HOPEX. If this rule is not followed for objects coming from SAP Solution Manager, the names of these objects are automatically modified in HOPEX.
When you change one of these attribute values, this does not affect the other.
When projects and their data are imported/exported into/from HOPEX, the SAP name does not change.
When exporting from HOPEX to SAP Solution Manager:
• If a SAP name is specified for an object in HOPEX, the SAP name remains the same in SAP Solution Manager.
• If no SAP Name is specified for an object in HOPEX, the HOPEX name (Local name) is taken into account in the export and becomes the name of the object in SAP Solution Manager.
Namespace rules
When naming objects in HOPEX a particular namespace rule applies for the SolMan metamodel.
According to this rule, no two objects of the same MetaClass can have the same name.
If you try to give an object a name that is already assigned to an object of the same MetaClass:
• the name is automatically modified.
• The string "-1" or "-[n]" is added to the name, where [n] is a number that makes the name unique.
The value of n is incremented by 1 each time you try to the name.Example
Two SolMan Processes exist in a SolMan Scenario and are called "P" and "P-1". If you try to give a new SolMan Process the name "P", the name "P-2" will automatically be assigned to the new object.
This automatic behavior occurs when SolMan projects are imported into HOPEX.
