Object Reference Types (SAP Library - SAP NetWeaver Exchange Infrastructure)

Object Reference Types

Properties

There are different types of object references in the Integration Repository. The semantic conditions of the object types involved determine 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

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. Note that the properties of an absolute object reference can change if you reference an object in an underlying software component version (see: Underlying Software Component Versions).
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 Integration Builder, you try 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.

List of Possible Object References

Object References for Integration Scenarios and Integration Processes

Referencing Object	Referenced Object	Object Reference Type
Integration scenario	Internal action (in an application component of type Product or Main Instance)	Absolute object reference
Integration scenario	External action (in an application component of type Template )	Relative object reference
Integration scenario	Integration process (in an application component of type Product or Main Instance)	Absolute object reference
Integration scenario	Integration process (in an application component of type Template )	Relative object reference
Integration scenario	Message interface (within a connection if the application component is of type Product or Main Instance)	Absolute object reference
Integration scenario	Message interface (within a connection if the application component is of type Template)	Relative object reference
Integration scenario	Interface mapping (within a connection)	Absolute object reference
Integration process	Message interface	Relative object reference
Integration process	Interface mapping	Relative object reference
Action	Message interface	Relative object reference

Object References for Interface Objects

All object references between interface objects are relative object references.

Note

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
Interface mapping	Message interface	Automatic object reference
Interface mapping	RFC, IDoc	Automatic object reference
Interface mapping	(Fault) message type, external message, RFC message	Automatic object reference
Interface mapping	Message mapping	Relative object reference
Interface 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
Mapping template	Data type	Automatic object reference
Mapping template	Complex type (RFC, IDoc, external definition)	Automatic object reference

Examples

Referencing Object	Referenced Object	Object Reference Type	Note
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 integration scenario (see Integration Scenario).
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 integration scenario (not necessary in the same namespace) (see Integration Scenario).
Integration scenario	Interface mapping (within a connection)	Absolute object reference	The software component version of the interface mapping is not dependent on the software component version of the Integration Scenario (see 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.
Interface mapping	Mapping program	Relative object reference	The mapping program must be in the same software component version and in the same namespace as the interface mapping (see Interface Mappings).