Object Reference Types 

Object Reference Types for Design Objects

There are three different types of object references for design objects. 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.

·        Absolute object reference

The software component version of the referenced object is not dependent on the software component version of the referencing object.

The software component version of an action that is used in a Business Scenario 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 Business Scenario.

After it has been copied to a new software component version, the referencing object references an object in the original software component version. Therefore, the object reference is not damaged by the copying procedure because the referenced object already exists in the original software component version.

·        Object reference to an object in the most recent software component version

The software component version of the referenced object is not dependent on the software component version of the referencing object. The software component version of the referenced object is however not fixed (unlike for an absolute object reference). The object reference always refers to the object in the most recent software component version that contains the object.

An interface mapping references an RFC that is located in the software component SWC. Software component SWC also has the software component versions SWCV1, SWCV2, SWCV3. However, the RFC only exists in the software component versions SWCV1 and SWCV2 because it was only imported there. When navigating to the RFC, the object from software component version SWCV2 is displayed.

·        Relative object reference

The 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.

The software component version of a data type that is used in a message type is the same as the software component version of the message interface, because both objects are delivered together.

After it has been copied to a new software component version SWCV2, the referencing object references an object in the same software component version SWCV2. The version context of the referenced object is determined by the version context (in other words, the software component version) of the referencing object. Since the referenced object is not copied as well, the object reference initially cannot be followed. If, in the corresponding object editor in the Integration Builder, you try to navigate to the referenced object, the system displays a message to this effect. So that the object reference becomes valid again, the referenced object must be copied 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.

All object references that occur for design objects are listed and categorized in the table below

Object References for Design Objects

Referencing Object	Referenced Object	Object Reference Type
Business Scenario	Action (in an application component of type Product)	Absolute object reference
Business Scenario	Action (in an application component of type Template )	Relative object reference
Business Scenario	Message interface (within a connection if the application component is of type Product)	Absolute object reference
Business Scenario	Message interface (within a connection if the application component is of type Template)	Relative object reference
Business Scenario	Interface mapping (within a connection)	Absolute object reference
Action	Message Interface	Relative object reference
Message Interface	Message Type	Relative object reference
Message Interface	Fault Message Type	Relative object reference
Message Type	Data Type	Relative object reference
Fault Message Type	Data Type	Relative object reference
Interface Mapping	Message Interface	Object reference to an object in the most recent software component version
Interface Mapping	RFC, IDoc	Object reference to an object in the most recent software component version
Interface Mapping	Fault Message Type	Object reference to an object in the most recent software component version
Interface Mapping	Mapping Program	Relative object reference
Message Mapping	Message Type	Absolute object reference If the software component of the message mapping is the same as the software component of the message type, then the absolute object reference behaves as a relative object reference. This means that the reference to the message type is often lost when copying a message mapping.

Examples

Referencing Object	Referenced Object	Object Reference Type	Note
Business Scenario	Action (in an application component of type Product)	Absolute object reference	The software component version of an action within an application component of type Product, is based on the product version and is not dependent on the software component version of the business scenario (see Business Scenario).
Business 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 Business Scenario (not necessary in the same namespace) (see Business Scenario).
Business 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 Business Scenario (see Business Scenario).
Message Type	Data Type	Relative object reference	Message type and data type must be in the same software component version.
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).
Interface Mapping	Fault Message Type	Object reference to an object in the most recent software component version	The fault message type must either be in the outbound or inbound interface (see Interface Mapping).