There are different types of object references in the Enterprise Services Repository. The semantic conditions of the object types involved determines which object references are used. This cannot be altered by the user. Nevertheless, it is important to note the differences between the individual object reference types because they can behave differently when you copy an object.
The following types of object reference exist:
Object Reference Types in the Enterprise Services Repository
Object Reference Type |
Description |
Absolute object reference |
Software component version of the referenced object is not dependent on the software component version of the referencing object. After it has been copied to a new software component version, the referencing object references an object in the original software component version. The object reference is not damaged by the copying procedure because the referenced object already exists in the original software component version. In the case of absolute object references, you can select the software component version of the object used when you create the reference. |
Relative object reference |
Software component version of the referenced object is identical to the software component version of the referencing object. This also applies when the referenced object is located in a software component version on which the software component version of the referencing object is structured. After it has been copied to a new software component version, the referencing object references an object in the new software component version. Since the referenced object is not copied as well, the object reference initially cannot be followed. If, in the Enterprise Services Builder, you want to navigate to the referenced object from the copy of the referenced object, the system displays a message to this effect. So that the object reference becomes valid again, you must copy the referenced object with the same name to the new software component version SWC2 as well. The namespace of the copied referenced object must be the same as the namespace of the object that was originally referenced. In the case of relative object references, the software component version of the referenced object is fixed when the reference is created and cannot be selected. |
Automatic Object Reference |
If the software component version of the referenced object is identical to the software component version of the object to be referenced, then the automatic object reference acts like a relative object reference. Otherwise, the automatic object reference acts like an absolute reference. |
Object References for Process Integration Scenarios and Integration Processes
Referencing Object |
Referenced Object |
Object Reference Type |
Process Integration Scenario |
Internal action (in an application component of type Product or Main Instance) |
Absolute object reference |
Process Integration Scenario |
External action (in an application component of type Template ) |
Relative object reference |
Process Integration Scenario |
Integration Process (in an application component of type Product or Main Instance) |
Absolute object reference |
Process Integration Scenario |
Integration Process (in an application component of type Template ) |
Relative object reference |
Process Integration Scenario |
Service interface (within a connection if the application component is of type Product or Main Instance) |
Absolute object reference |
Process Integration Scenario |
Service interface (within a connection if the application component is of type Template) |
Relative object reference
|
Process Integration Scenario |
Operation mapping (within a connection) |
Absolute object reference |
Process Integration Scenario |
Service Interface |
Relative object reference |
Process Integration Scenario |
Operation mapping |
Relative object reference |
Action |
Service-Interface-Operation |
Relative object reference |
Object References for Interface Objects
All object references between interface objects are relative object references.
Interface objects are only complete when they are together with the objects that they reference and must therefore always be shipped together.
Object References for Mapping Objects
Referencing Object |
Referenced Object |
Object Reference Type |
Operation mapping |
Service-Interface-Operation |
Automatic Object Reference |
Operation mapping |
RFC, IDoc |
Automatic Object Reference |
Operation mapping |
(Fault) message type, external message, RFC message |
Automatic Object Reference |
Operation mapping |
Message mapping |
Relative object reference |
Operation mapping |
Mapping program (Java class, XSL) |
Relative object reference |
Message mapping |
Fault message type |
Automatic Object Reference |
Message mapping |
IDoc |
Automatic Object Reference |
Message mapping |
RFC message |
Automatic Object Reference |
Message mapping |
External message |
Automatic Object Reference |
Message mapping |
Mapping template |
Automatic Object Reference |
Message mapping |
Function library |
Relative object reference |
Message mapping |
Imported Archive |
Relative object reference |
Mapping template |
Data type |
Automatic Object Reference |
Mapping template |
Complex type (RFC, IDoc, external definition) |
Automatic Object Reference |
Mapping template |
Mapping template |
Automatic Object Reference |
Mapping template |
Function library |
Relative object reference |
Mapping template |
Imported Archive |
Relative object reference |
Function library |
Imported Archive |
Relative object reference |
Referencing Object |
Referenced Object |
Object Reference Type |
Comments |
Process Integration Scenario |
Action (in an application component of type Product or Main Instance)
|
Absolute object reference
|
The software component version of an action within an application component of type Product is based on the product version (the application component) and is not dependent on the software component version of the process integration scenario (see Process Integration Scenario). |
Process Integration Scenario |
Action (in an application component of type Template )
|
Relative object reference
|
Actions within an application component of type Template must be located in the same software component version as the process integration scenario (not necessary in the same namespace) (see Process Integration Scenario). |
Process Integration Scenario |
Operation mapping (within a connection) |
Absolute object reference
|
The software component version of the operation mapping is not dependent on the software component version of the process integration scenario (see Process Integration Scenario). |
Message type |
Data type |
Relative object reference |
Message type and data type must be in the same software component version. Both objects are shipped together. |
Operation mapping |
Mapping program
|
Relative object reference
|
The mapping program must be in the same software component version and in the same namespace as the operation mapping (see Operation Mappings). |