Software Component Versions 

Definition

A software component version is a shipment unit for design objects in the ES Repository (these objects are therefore also known as Repository Objects). A software component version can be used in different product versions.

You can access SAP software components (and products) from the software catalog of the System Landscape Directory (see: Software Catalog).

It is also possible to structure software component versions using other software component versions. A software component version upon which another software component version is dependent is called an underlying software component version.

See: Underlying Software Component Versions

If you want to create objects locally purely for testing, you can define a local software component version for this purpose. A local software component version is not based on data from the System Landscape Directory.

See: Creating a Software Component Version

Use

To use an SLD based software component version, import it from the System Landscape Directory into the Enterprise Services Repository (see: Importing SLD-based Software Component Version).

You can define a local software component version freely in the Enterprise Services Repository (see Creating a Local Software Component Version). Local software component versions are intended for temporary development of local objects in an ES Repository only. Consequently, you cannot use any local objects in a configuration in the Integration Directory, and subsequently cannot perform any runtime tests with these objects. You also cannot transport any local objects by using the Change Management Service (CMS).

While you require software component versions to develop in the ES Repository, you do not need them to configure A2A or B2B scenarios in the Integration Directory. Integration Directory content is not shipped and must be configured at the customer site.

Structure

When you have imported a software component version, the Key tab page displays attributes from the System Landscape Directory. You can use the following attributes on the Definition tab page:

●      Importing Interfaces

Here you can define whether the import of RFCs and IDocs is permitted for the software component version. If it is, then you must specify an SAP system from which these interfaces are to be imported. You can only specify one such SAP system for each software component version.

See: Connection Using Adapters and Imported Interfaces

●      Namespaces

Using namespaces you can further subdivide the software component version into semantic units. You require them to create design objects in the ES Repository (that is: integration scenarios, service interfaces, business objects, mappings).

See: Namespaces, Design Time

●      Object Properties

Use these two attributes to define the properties for all objects of the software component version:

○       Objects Are Original Objects:

The objects of the software component version are the original objects in the repository belonging to the ES Builder, and should only be modified in this repository. There can only be one original object, in other words, you must not set this attribute for multiple software component versions of other ES Repositories simultaneously.

○       Objects Are Modifiable:

When set, this attribute enables you to change objects in the software component version. Use this attribute to lock all objects against changes, if required.

See also: Versioning in Transports

The latter two attributes are typically used as follows:

Attribute Set	Application
(a) and (b) set	The objects in this repository are the originals and can be modified. Use this setting for the repository in which the cross-system process is being developed.
(a) and (b) not set	The objects in this repository are not the originals and cannot therefore be modified here. Use this setting for repositories where the originals from a different repository have been imported. More information: ESR Content Transports
Only (a) set	The original objects are temporarily locked against modifications, for example to ‘freeze’ the development status.
Only (b) set	Normally you do not change objects in a repository where the objects are the not the originals. However, use this attribute for temporary changes, for example when you do not want to wait for the next import before making an emergency correction. These changes are lost when the next import takes place (due to the conflict resolution function).

Editing Software Component Versions describes using additional object properties.

Integration

The navigation tree in the ES Builder then provides you with an overview of all software component versions that use design objects within cross-system applications. To ensure that design objects that belong together within a software component version are shipped together, the ES Builder restricts the references that are possible between objects in the ES Repository (also see: Object References).