Start of Content Area

Component documentation Customizing Extractors  Locate the document in its SAP Library structure

Purpose

The BW Service API (SAPI) is a technology package in the SAP source system that enables the tight integration of data transfer from SAP source systems into the BW system.

The Service API allows you to

        make available SAP application extractors as a basis for data transfer into BW

        carry out generic data extraction

        implement intelligent delta methods

        access data in the source system directly from BW (RemoteCube support).

Customizing extractors comprises all activities required for extracting and transferring data between an SAP source system and BW.

A distinction is made between data transfer from

        OLTP- / R/3 systems,

        BW systems as source systems and

        other SAP source systems.

Irrespective of the type of source system, Customizing for extractors comprises activities that belong to the scope of SAPI:

        General settings for data transfer from source systems into BW.

        the option of installing Business Content delivered by SAP.

        the option of maintaining generic DataSources

        the option of post-processing the application component hierarchy and DataSources on a source system level

You can access Customizing for extractors from the context menu for any source system in the Administrator Workbench (transaction SBIW).

Integration

Alongside the activities that belong within the scope of SAPI, Customizing for extractors contains settings for OLTP and other SAP source systems / source-system specific settings for application-based DataSources.

Functions

General Settings

These include the following:

        Maintaining Control Parameters for Data Transfer

        Restricting Authorizations for the Extraction

        Checking the Delta Queue

Installing Business Content Delivered by SAP

DataSources delivered within Business Content and those delivered by partners appear in a delivery version (D version). If you want to use a partner or Business Content DataSource to transfer data from a source system into a BW, you need to transfer this DataSource from the D- into the active (A-) version.

In the source system, the DataSources are assigned to specific application components. If you want to display these DataSources in the source system view within BW Administrator Workbench modeling as a part of this application component hierarchy, you need to transfer them from the D version into the A version.

The following section of Customizing for extractors explains how you can transfer the application component hierarchy and DataSources delivered with BW Business Content / Partner Content into the active version.

Note

Transferring Data from an OLTP System or Other SAP Source Systems

Note: You need to make some settings in advance for some Business Content DataSources before you can transfer data into a BW. You can find these settings in the section Settings for Application-Specific DataSources within Customizing for extractors. (You can only find this section in those SAP source systems for which it has pertinence)

The following activities are associated with the transfer of Business Content:

        Transferring the Application Component Hierarchy

        Installing Business Content DataSources

Generic DataSources

Regardless of the specific application, you can use generic data extraction to extract data from any transparent tables, database views or SAP query InfoSets. You don’t need to program in ABAP. You can also use function modules for generic data extraction.

In this way, you can use your own DataSources for transaction data, master data attributes or texts. The data for such DataSources are read generically and then transferred into the BW.

Generic DataSources allow you to extract data which cannot be supplied to the BW either with the DataSources delivered within Business Content or with customer-defined DataSources of the application.

You can find additional information under Maintaining Generic DataSources.

Post-Processing DataSources

You can find additional information under Editing DataSources and Application Component Hierarchies .

 

 

 

End of Content Area