Background documentationTransferring Data with SAP Landscape Transformation Replication Server Locate this document in the navigation structure

 

Using SAP Landscape Transformation Replication Server (SLT) you can provide real time data for SAP NetWeaver BW. The Web service interface in BW is used to transfer data. SLT 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. The trigger-based replication allows delta processes to be used for tables that do not have any delta-enabled fields. For example, you can use delta processes for extractors (DataSources) without delta logic. If you are working with large master data tables without delta logic that are only changed very infrequently, you can significantly reduce the administration effort for frequent full processes by using SLT trigger-based replication as the transfer method.

SLT offers a useful alternative for data transfer to BW in the following cases:

  • The tables in the source are simple tables without joins or transformation logic.

  • The DataSources (extractors) are DataSources on simple tables/views that do not provide a delta mechanism and only contain minimal extractor logic.

Caution Caution

Note the following when using this transfer method for extractors:

  • Many extractors contain extractor logic (associations and content logic) that is very complicated to reconstruct in the BW system.

  • Many extractors can guarantee a consistent delta transfer to the BW system by using the delta queue.

Therefore we recommend that you only replace complex extractors with SLT in exceptional cases.

End of the caution.
Prerequisites

  • Note the licensing conditions when using SAP Landscape Transformation Replication Server.

  • You have implemented SAP Note 1808251 in the SAP NetWeaver BW system.

  • The SAP LT Replication Server (SLT system) has release version DMIS 2011 SP04 or DMIS 2010 SP09 (or higher versions). You have implemented SAP Note 1810627 in the SLT system.

  • The DMIS add-on (minimum DMIS_2011 SP02 or DMIS_2010 SP07) is installed on the SAP NetWeaver BW system and installed as the source in the SAP source for SAP systems.

Process

To configure the connection between a source and SAP NetWeaver BW and to configure the data transfer, proceed as follows:

  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 an RFC destination for the BW system using transaction SM59.

  3. To connect the data transfer source and the BW system using the SAP LT Replication Server, create a configuration in SAP LT Replication Server using transaction LTRC. 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.

  4. To make a Web service source system known in the SAP LT Replication Server, create an entry in table IUUC_BW_LOGSYS by entering the mass load ID of the configuration and the logical system name of the Web service system from the BW system.

  5. 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.

  6. 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 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 Note1733714.

      • 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 the field 0RECORDMODE. 0RECORDMODE is automatically mapped to the SLT operation modes. This means it possible to track changes made to the data records in the DataSource, in comparison to direct changes in database tables (INSERT, UPDATE, DELETE).

      End of the note.

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

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

  7. In the BW system, configure the data update from the PSA. If you access the data frequently and want the data to be refreshed once an hour up to 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).

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.

This graphic is explained in the accompanying text.

Note 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.

End of the note.

More Information

Transferring Data Using Web Services

Real-Time Data Acquisition

For information on installation and data transfer with the SAP LT Replication Server, see SAP Note 1826585.