Creating a Software Component Version

Prerequisites

You have created a transport package for the SWCV.

More information: Transport Organizer (BC-CTS-ORG)

Context

This procedure allows you to create a software component version (SWCV), which is a shipment unit for design time objects in the Data Orchestration Engine (DOE) repository.

A SWCV is a part of the software catalog in the System Landscape Directory. You must create SWCVs before you can create data objects. Data objects from one software component version are transported and shipped together. It is possible to join multiple software component versions for the version of a product and ship them together.

The metadata information for an SWCV contains the metadata information of all the data objects, distribution models and the back-end adapters that are contained in that SWCV.

Procedure

Log on to the SAP NetWeaver AS and choose Data Orchestration Engine Development Data Orchestration Workbench.
Choose Create SWCV .

The fields in the SWCV Creation dialog box are activated.

Enter the following details in the appropriate fields:

Field Name	Description	User Action and Values	Comments
Name	Indicates the name of the software component version	Enter a name for the SWCV.	The name must not contain any spaces or special characters.
Vendor	Indicates the vendor name	Vendor: example.org	While creating a Software Catalog in SLD we give a name in the vendor column as required.
Version	Indicates the version of the SWCV	Enter a version for the SWCV.	This allows you to define different versions of the same project so that you can decide later which version you want to release.
Element ID	Indicates the Element Type ID.	Enter a numeric value.	For SWCVs shipped by SAP, the Element Type ID is identical to the PPMS number. (The PPMS number is a numeric key that uniquely identifies the SWCV maintained in the PPMS.)
Destination	Indicates the back end destination from where the data objects created in the SWCV obtain the data. For each data object, you can specify the back end from which the data object can obtain its values. If you do not specify a back end for a data object, the DOE obtains data from the back end specified for the SWCV, that is, the Destination value.	Enter the back end destination	If a majority of the data objects in the SWCV obtain values from a particular back end, you specify that back end destination, here. You then do not have to specify the back end when creating these data objects. You should specify the back end for data objects that should obtain data from the back end that is different from the one specified.
Data Object Package	Indicates the package for storing the data objects created in the SWCV. This package is only for storing the data objects of the SWCV, and not the SWCV itself. You specify the package for the SWCV in step 8.	Enter the package for the data objects.	In case of storing the data objects locally, you specify $TMP as the package; and this is not transported. If you want to transport the data object at a later point in time, you can assign the locally saved data object to a transportable package

Note

You select the option Uses Application based on NW04/ NW20004s MI only if you are migrating the SyncBOs defined in MI to the current DOE.

Choose Save .
In the Package field, enter the name of the transportable package and choose Continue .
Enter the transport request and choose Enter .

Note
To create a transport request, choose Create request .
Choose Copy .
Choose Save .

Note
To save the data object locally, choose Local Object . In this case, the data object becomes part of the $TMP package and is not transported. If you want to transport the data object at a later point in time, you can assign the locally saved data object to a transportable package.

To view the metadata information of the SWCV, click the SWCV with the secondary mouse button and choose View Metadata .