Show TOC

Transferring Data from SLT Using Web ServiceLocate this document in the navigation structure

Configure the connections for transferring data between the relevant systems. When the replication process is started in SAP LT Replication Server (SLT), the required SLT components and BW objects are generated and data transfer begins.

Prerequisites

  • Note the licensing conditions when using SAP LT Replication Server.

  • The SAP LT Replication Server must have one of the following minimum release versions: DMIS 2011 SP04 or DMIS 2010 SP09. You also have implemented SAP Note 1810627 Information published on SAP site in the SAP LT Replication Server.

    Note If you are using DMIS 2011 SP05 or want to update from SP04 to SP05, implement SAP Note 1817467 Information published on SAP site (before performing the update).
  • In SAP sources, add-on DMIS_2011 SP02, DMIS_2010 SP07 or higher is installed.

  • In the BW system, add-on DMIS_2011 SP02 or a higher version is installed.

    Note We also recommend using add-on DMIS_2011 for the SAP LT Replication Server and the SAP source.
  • The data transfer is possible for simple tables.

Context

Using the Web service interface and trigger-based replication of SAP LT Replication Server, you can transfer data to the BW system in real-time. SAP LT Replication Server replicates data in a Web service DataSource. Here the data is available for further processing with real-time data acquisition. With SLT you can replicate non-SAP sources, SAP sources and customer-specific tables.

Procedure

  1. In the BW system, create a source system (source system type Web Service) for each source. This ensures that source tables or source DataSources with the same name from different sources are loaded into different Web service DataSources.
    The source system is needed so that the SAP LT Replication Server can create DataSources for this logical system.
  2. In the SAP LT Replication Server, create a connection (RFC or database connection) to the source.
  3. In the SAP LT Replication Server, create an RFC destination for the BW system using transaction SM59.
  4. To connect the data transfer source and the BW system using the SAP LT Replication Server, create a configuration of scenario type Replication to BW-PSA in the SAP LT Replication Server using transaction LTRC or LTR. Enter the connection to the source and the RFC destination to the BW system. The system assigns a 3-digit mass load ID for the configuration.
  5. Run transaction SE16 in the SAP LT Replication Server and specify parameter trg_scenario with entry PSA for the mass load ID in table IUUC_BW_LOGSYS.
  6. To start data provisioning for an application table or DataSource in the source, choose Data Provisioning in transaction LTRC in the SAP LT Replication Sever.
  7. For a continuous data transfer (initial loading and delta provisioning), choose Start Replication.
    The required SLT components in the source and the relevant BW objects are generated.

    The following items are automatically generated in the source:

    • a logging table for the application table

    • DB triggers that automatically write information on changed records to the logging table.

    The following items are automatically created in the BW system:

    • a Web service DataSource with the structure of the source table/source DataSource (naming convention: SLT_<name of source table/source DataSource>)

      Note
      • Source string fields must be mapped to PSA-capable data types in the Advanced Replication Settings in the SAP LT Replication Server. For more information on the advanced replication settings, see SAP Note 1733714 Information published on SAP site.

      • Amount and quantity fields are only given the data type QUAN or CURR if the references to the currency fields and unit fields are also in the DataSource or in the same source structure as the amount and quantity fields. Otherwise the amount fields and quantity fields in the DataSource are created with the data type DEC.

      • The DataSource is also given field 0RECORDMODE. 0RECORDMODE is automatically mapped to the SLT operation modes. This makes it possible to track changes made to the data records in the DataSource, in comparison to direct changes in database tables (INSERT, UPDATE, DELETE).

    • an InfoPackage that transfers source data to the Web service DataSource

Results

Firstly, all the data from the source table is transferred to the Persistent Staging Area (PSA), and then the delta is transferred automatically.

Example

The following graphic illustrates the real-time data transfer from an application table of a non-SAP source. In the BW system, the data is updated by RDA.



Figure 1:
Note

If the data transfer source is an SAP system, the read module is located in the source and not (as shown in the graphic) in the SAP LT Replication Server.

Next Steps

In the BW system, configure the data update from the PSA. If you access the data frequently and want the data to be refreshed somewhere between once an hour and once a minute, use real-time data acquisition (RDA daemon) to update the data to an InfoProvider. If it is sufficient for your analysis and reporting requirements to refresh the data using longer time intervals, you can use a standard data transfer process to perform the update.

For information on updating from the PSA with real-time data acquisition (RDA), seeTransferring Data Using Web Services (RDA).

For information on updating from the PSA with a standard data transfer process, seeTransferring Data Using Web Services (Standard).