Importing SAP Content

The transport requests provided by SAP with content for the SAP Knowledge Warehouse are delivered in two ways:

The majority of the transport requests are delivered on various DVDs, which either contain SAP documentation or SAP training material and templates for a Quality Management manual.
Training DVDs are only delivered to customers who have a license for training contents. For more information about the contents delivered on DVD, see the letter enclosed with your SAP Knowledge Warehouse installation package.

Note

You can view all customer letters for the content updates delivered up to now from the areas Documentation and Training on the SAP Service Marketplace under the QuickLink kwcontent (http://service.sap.com/kwcontent).

End of the note.

Caution
There is a separate SAP Note with any special features or problems for each of the content updates. This SAP Note is specified in the customer letter in each case, and you should read it before starting the import of the relevant content update.

End of the caution.
There are also transport requests with SAP content (for example, for content templates), which are only available as attachments to SAP Notes.

This section describes how you can import transport requests delivered by SAP through the different delivery methods into your local SAP KW system.

Transport Request Types

To help you select the correct procedure for transport requests,

the different types are first explained:

Transport request type	Description
SAP Upgrade Piece List	Naming convention: Always starts with SAPK*; Example: SAPK059LDE Components: Information that must be imported into the SAP NW ABAP system (contained in the data and cofiles). Special metadata for identifying the content and its relationships. Example Name of the Cofile: K059LDE.SAP Name of the Data File: R059LDE.SAP End of the example. Content that must be imported into the SAP Content Server (I files). This type of data files contains the actual files of the content objects (for example, Microsoft PowerPoint/Microsoft Word/Microsoft Visio). Name of the Data File: I059LDE.SAP
Standard SAP KW Transport with Content Objects	Naming convention: Does not start with SAPK*, but rather with the <SID> of an SAP KW system from which the transport was generated. Example IDTK000055 End of the example. Components: No differences to the transport request of type SAP Upgrade Piece List (two data files exist: R and I files). Example Name of the Cofile: K000055.IDT Name of the Data Files: R000055.IDT / I000055.IDT End of the example.
Standard SAP KW Transport with Purely Administrative Data (such as enhancements for the SAP namespace)	Naming convention: Does NOT start with SAPK*, but rather with the <SID> of an SAP KW system from which the transport was generated. Example KWEK000153 End of the example. Components: Unlike the transport requests of types SAP Upgrade Piece List or the Standard SAP KW Transport with Content, there is no I file here that needs to be imported into the SAP Content Server. There are only the normal cofile and data file (R file). Example Name of the Cofile: K000153.KWE Name of the Data Files: R000153.KWE End of the example.

Prerequisites

To import transport requests provided by SAP (for example, containing training courses/documentation/content templates) into your SAP KW, the SAP Content Server must already be installed and configured.
The SAP system underlying the SAP KW must also have been set up with the appropriate settings, such as repositories. More information: Configuration for Storing Content.
The SAP Content Server uses MaxDB/SAP DB to store content files. Since large quantities of data are involved in importing the transport requests provided by SAP, you should check, and if necessary change, the log mode before the start. More information: Checking the Log Mode.

Caution Caution

When importing the content into your SAP Knowledge Warehouse, make sure that the log modes of the SAP database and the database of the SAP Content Server (MaxDB/SAP DB) are identical, that is, either back up the logs in both databases or overwrite them without back up in both databases.

End of the caution.

Note Note

The SAP Knowledge Warehouse is not usually being used in production operation when content provided by SAP is first imported. The SAP system database and SAP Content Server logs can therefore be discarded without being backed up first (for example, Oracle: No archive Mode No archive Mode, MaxDB: auto overwrite, SAP DB: DEMO). For more information about log modes refer to the database documentation.

If this is not intended, you need to schedule the relevant log backup in both databases to avoid delaying the imports.

End of the note.

Procedure

The following describes how to import the different transport request types:

Importing Transports of Type SAP Upgrade Piece List

Creating an RFC Destination for Direct Import
If the SAP NW ABAP system and the content server are on different servers, you need to create an RFC destination (such as SAPKPROTP_GW) to import the content into the Content Server.

If the content server is on the same server as the SAP NW ABAP system, you can use the automatically-created RFC destination SAPKPROTP for imports.

Caution

If there is no other SAP instance with a gateway on the server on which the SAP Content Server is running, you need to install a separate gateway instance.

End of the caution.
Importing Transport Requests into the ABAP System
For the transport requests to be imported, place the associated cofiles and data files (R files) in the relevant transport subdirectories (cofiles / data) of the SAP NW ABAP system and use STMS to import them.
Import Associated Content Files (I Files) into the SAP Content Server
Transfer the I files to the content server. After you have successfully completed the imports into the SAP NW ABAP system, for certain transport requests, you can start the import of the contents into the content server using report RSIRTRIM.

Importing Transports of Type Standard SAP KW

Unlike the SAPK* imports, the procedure is simplified in that the special postprocessing of the I files using report RSIRTRIM is not necessary. Therefore, with transports of this type, you can place both the R file and the I file into the data directory of the transport system. When you import a request of this type with STMS, the system automatically imports the content into the content server.

For the rest of the procedure, see Importing Transport Requests into the ABAP System.