Resolving Naming Conflicts

Use

There can be no object types with identical names, for example models and data types, within a hierarchy of software components.

For this reason, the following activities, which involve the participation of connector models, include an automatic check for identical names by default:

Assigning or changing the name of object types, such as models, nodes, node fields, data types, data sources, query fields, and response fields
Including and nesting software components
After importing changed software components and their objects
Creating connectors that are located in different software components if they are selected for the same logical system

If a name is already being used, a message asks you to change the name.

The system automatically renames some technical objects and background functions: In such cases, a message appears to inform you that the system has changed the object name. By default, the name is given the suffix _<number>.

Procedure

After an import, proceed as follows to solve potential naming conflicts in a software component:

Launch the modeler.
Choose Actions Display Models.
Select the software component that you want to check.
Choose Actions Resolve Conflicts.

The naming conflicts are displayed.
Select an entry and choose one of the following activities in the Conflict Resolution Strategy column:
- Keep original name as alias and rename: We do not recommend this because it shifts the naming conflict to the back-end system.
- Rename:
  
  You can rename the entry if the object type is located in a software component that allows changes.
  
  You can see the new name in the Renamed ID column. By default, the system suggests a name that adds the suffix _<number> to the original name. Alternatively, you can use any other name that is not already in use in the hierarchy.
  Note
  
  You should note that you also have to rename the object type in all other places where it is used. This is necessary if the object type uses data extraction logic on the back-end side that is based on the name of the object type.
  
  Examples of this are:
  - The object type uses BADI-based extractors from the BADI_ESH_IF_OBJECT_DATA enhancement spot. You have to change the BADI filter.
  - The object type implements data provider interfaces, such as IF_ESH_IF_DATA_PROVIDER, IF_ESH_IF_DATA_PROVIDER_MULTI, or IF_ESH_IF_DATA_PROVIDER_XSYS. These interfaces are then launched using the new name of the object type (import parameter IV_OBJECT_TYPE_ID).
- Delete: If you no longer require the object, you can select it for deletion, for example because it is a copy of the original.
Repeat step 5 for all naming conflicts in the list.
Choose Resolve to use the chosen strategy to solve the selected entries with naming conflicts.