Underlying Software Component
Versions
Use
In some cases, an existing software component version is a prerequisite for a software component version because, for example, you need to reuse part of the software. In this case, the software component version upon which the other software component version depends is referred to as the underlying software component version. The software component version is only complete with the underlying software component version upon which it is based.
You define the corresponding software dependency (“based-on” relationship) in the System Landscape Directory (see: Software Dependencies).
Objects of an underlying software component version are displayed in two places in the navigation area of the Enterprise Services Repository (Objects tab page).
...
1. In the Basis Objects subtree of the software component version that is based on the underlying software component version.
2. In the subtree of the underlying software component version (at the same level as all other software component versions).
This relationship is shown in the figure. In the case illustrated, the software component version Based-On Component 1.0 is based on the software component version Basis 1.0.
Display of Objects of an Underlying Software Component Version
Multi-level software dependencies are also supported. The objects of all the underlying software component versions are always visible in a software component version.
Prerequisites
You must define the dependency between two software component versions in the System Landscape Directory.
See:
Defining Additional
Software Dependencies
Features
Modifying Objects
If you want to enhance or modify SAP objects (as part of a customer development, for example), you define a software dependency between the software component version in which you want to make your development and the software component version containing the SAP objects used.
See: Modifying an Object.
Object Reference to an Object in the Underlying Software Component Version
You can reference objects in an underlying software component version.
If you want to set an absolute object reference, you have two options:
● Set the reference to the target object in the Basis Objects subtree.
In this case, the absolute object reference becomes a relative object reference.
If, after a release upgrade, the software component version of the source object is based on a newer version of the underlying software component, the object reference now automatically points to the target object in the current software component version.
● Set the reference to the target object in the subtree of the underlying software component version.
In this case, the object reference remains an absolute object reference.
In this variant, you set the reference to the original object in the original software component version. If, after a release upgrade, the software component version is based on a new version of the underlying software component, the object reference still always points to the original object. Choose this variant if you want to ensure that the object reference always points to the original object.
See also:
Examples
For examples of the use of underlying software component versions, see the document Guide for Customer Developments and Modifications in the Integration Repository .
This guide is on the SAP Developer Network (SDN) at http://www.sdn.sap.com/irj/sdn/pi-design.