Creating Partner Content in the OLTP System 

Purpose

Creating DataSources and an application component hierarchy in your own namespace enables you to deliver Business Content in the OLTP system.

Prerequisites

·        You have applied for the namespace for the development and generation of objects, released it in the OLTP system and set it to changeable. You can find additional information here: Using a namespace for the development of BW Objects.

·        You have already made system settings in the OLTP system.

Process

Creating a Partner DataSource

You can create a generic DataSource as a partner DataSource. You can find information about this procedure here: Maintaining Generic DataSources.

When creating a DataSource in a Content development system, the system creates an A and D version. The DataSource is stored in identical form in both the A and D versions. There is only one version for the extract structure of the DataSource.

When you generate a DataSource, and in turn an extract structure, the system writes the following transport objects to a transport request:

Transport object	Description
R3TR OSOD /<Namespace>/<DataSource> /ABC/DATASOURCE1	D-version of DataSource
R3TR TABL /<Namespace>/ES<DataSource><four-character counter> or R3TR TABL /ABC/<freely-chosen name of extract structure> /ABC/DATASOURCE1	Extract structure

The active version of the DataSource (object type: OSOA) is not linked with the transport system and is not delivered.

SAP supports the creation of partner DataSources, which extract using database tables and views or using a function module.

When extracting using a view/table, note the following:

When extracting using a view/table, the system generates a proposal for the extract structure name when you enter a name for the DataSource: /<Namespace>/ES<DataSource><four-character pointer>, z. B. /ABC/ESDATASOURCE10001.

You can change the name of the extract structure.

This is important when you want to make incompatible changes to the extract structure (such as changing a field type) and the productive scenario is to remain in place in the delivered system. In the screen to create a DataSource, enter a new name for the extract structure.After generating the changed DataSource, the extract structure is regenerated under this name.

When extracting using a function module, note the following:

In this case, the system does not generate a proposal for the extract structure. Enter the name of the extract structure that you have previously created in your namespace in the ABAP Dictionary.

If you choose to make incompatible changes to the extract structure (such as changing a field type), create an extract structure with a new name in the ABAP Dictionary (as a modified copy of the old structure). In this way, you also ensure that the productive scenario remains in place in the delivered system and that the extract structure is not overwritten.

Creating a Partner Application Component Hierarchy

...

       1.      Enter transaction code rsa8 in the command field.

The Selection of a Hierarchy dialog box appears.

       2.      Enter the name of the hierarchy if not already proposed.

       3.      Choose Create.

       4.      Choose Create. Other information about editing application component hierarchies can be found under Editing DataSources and Application Component Hierarchies.

After saving the hierarchy, the system writes the transport object R3TR DSAD /ABC/<Application component hierarchy> to a transport request.

Upon saving the system creates a D version and an identical A version for the application component hierarchy, which can only be transported in its entirety, as was the case for DataSources.

If you only want to deliver individual DataSources, you do not need to have your own application component hierarchy. Check whether an existing application component is suitable for the grouping and delivery of your DataSources. DataSources that have not been assigned to an application component appear in the application component hierarchy under the node NODESNOTCONNECTED. They can be edited and used in the standard way.

If, when changing a system for example, you want to keep the D version of a hierarchy, you need to execute report RSA1APDC before editing the hierarchy. This report generates an A version from the imported D version.

Result

The D versions of the generated DataSources and application component hierarchies, as well as the extract structures and, where applicable, function modules, appear in a transport request. These can be transported into the Content test or –delivery system and from here delivered to partners or business areas.