Content Delivery by Customers 
Purpose
1. Scenario
The simplest scenario is made up of the following processes:
· You develop your own Content.
· You do not use Business Content delivered by SAP or only in an unchanged form.
· You deliver only your own Content to your customers.
2. Scenario
You also changes the Business Content delivered by SAP and deliver the modified Business Content to your customers. However, this more complex scenario requires additional manual work.
We recommend that you change no objects or very few of them (see Object Changeability in a Customer Content System).
Prerequisites
· You have set up the customer system as a Content development system (see System Settings in the BW System).
· You have transferred all required SAP Business Content objects from Content with the special user. (See System Settings in the BW System).
Process
1st Scenario: Developing Your Own Customer Content
You need to follow the following procedure when delivering customer Content you have developed yourself.
...
1. Create the required objects in your Content development system and activate those of which are firstly created in the M version (1. M-Version ® 1. A-Version). The system copies the activated objects automatically into the D version (1st D-Version).
If you want to transport the objects that you have already created before you have set the system setting for your BW system to content system, all you have to do to is activate them by copying them to the D version.
2. The system wrote your Content objects to the transport requests as the standard transport system has been activated. Release these requests. Your Content objects are transported from the Content development system into the Content test system.
3. Deliver the objects in the D version from the Content test system with a delivery transport (see System Environment). Make sure that no A-TLOGO objects are transported. Additional changes (2nd M Version) do not affect the delivery as long as these objects are not activated.
The following graphic illustrates this process:
The following graphic illustrates the delivery of customer Content that was developed in an individual customer namespace /ABC/ (see Using a Namespace for the Development of BW Objects). The objects are exported in the D version. The InfoObject 0MATERIAL are only used, and not delivered.
2nd Scenario: Adapting SAP Business Content
In many cases, it is more effective to use/adapt Business Content delivered by SAP instead of using one’s own Content as a basis. Within customer Content, you can deliver the adapted Business Content to your customers.
The delivery procedure is very much the same as described under scenario 1. However, you also need to change the objects you want to adapt to changeable in table RSOCONTCHNGABLE (see Object Changeability in a Customer Content System).
Delivering Modified Business Content after Importing an SAP Support Package or after an Upgrade
Note that after upgrading again or after importing an SAP support package, changes you made as a customer to any BC object delivered by SAP are lost when SAP delivers this object again.
We recommend the following procedure:
...
a. Import the SAP support package into your Content development system.
b. Build a correction-delivery transport.
c. As quickly as possible after importing the SAP support package, deliver your correction-delivery transport from the Content system into the junior systems.
The following graphic looks at the recommended procedure in detail:
...
The procedure depicted in the graphic is made up of the following steps:
1. Activate all Business Content objects delivered by SAP (1st A version).
2. Make the required changes (2nd M version).
3. Activate the changed objects (2nd A version). The system copies the activated objects automatically into the D version (1st D-Version).
4. You can deliver your customer Content in the D version (2nd D version).
5. If SAP chooses to redeliver Business Content in a support package or in an upgrade (3rd D version), you need to reproduce your objects in the D version.
In the Business Content function area of the Administrator Workbench, choose the view Objects in BW Patch. Check to see which objects SAP has delivered in the current support package. Within an upgrade, it is probably the case that most of the objects are delivered again.
To reproduce your objects in the D version, you can proceed in various ways:
¡ Without Merge
Usually, the customer only needs his own version (2nd version). In this case, all that is required is to reactivate the objects (with a normal user). As a result, the D version delivered by SAP is automatically overwritten (this is the 3rd D version). However, using this procedure means that all enhancements made by SAP are lost.
¡ With Merge
If you want to keep enhanced made and delivered by SAP, you can merge the new Content version (3rd D version) with the active version (2nd A version). This is then the 4th M version. Check which objects SAP has just delivered. You only need to include an object in your correction request when you have made changes to it.
The following table gives you an overview of the object types for which merge is automatically available. If automatic merge is not available, you need to manually compare the two versions (2nd A version and 3rd D version) and adapt them where necessary.
Availability of Automatic Merge for Object Types
With Automatic Merge |
Without Automatic Merge |
Report-report interface, RRI recipient of the InfoCube, RRI recipient of query. |
Aggregate |
DataSource / FileSource |
Application components |
InfoCube |
Crystal Report |
InfoObject |
Query element: Query, structure, restricted and calculated key figures, variables |
InfoObject Catalog |
Update rules |
Data Mining: Mining model, Model source |
InfoArea |
MultiProvider |
InfoPackage |
ODS Object |
InfoPackage Group |
Process Chains |
InfoSet, Classic InfoSet |
Transfer rules |
InfoSet query |
|
InfoSource |
|
Source system |
|
Query view |
|
Reporting Agent: Reporting Agent scheduling package, reporting agent setting |
|
Role |
|
Currency translation type |
|
Web item |
|
Web template |
|
Workbook |
Note: You need to merge the versions with the preferred user for which the system is not a Content system and the standard transport system has been deactivated (see System Environment). If objects are to be written not to package $TMP but to another transportable package, the requests for this user are not released and transported.
Afterwards, you need to once more activate the Content with a normal user, so that the objects are copied into the D version. If the activation is not to take place as no changes were made, you may need to make a pseudo change to the objects.
6. Upon activation, objects are written to tone or more transport requests. Transport the transport request(s) into the test system, and create a correction delivery transport from it.
7. Deliver your correction delivery transport to all junior systems as quickly as possible after the SAP support package has been installed.