Show TOC

Procedure documentationTransferring Transaction Data Using Web Services Locate this document in the navigation structure

 

If you want to use data for operational reporting that is not available in SAP source systems, use a Web service to transfer the data to the BW system.

Procedure

  1. Create a Web service DataSource.

    More information: Creating DataSources for Web Services

  2. Implement the Web service in your application.

  3. Specify an InfoProvider as the target of the real-time data transfer. This can be a HybridProvider, a DataStore object that is not being used as part of a HybridProvider, or an InfoObject (texts, attributes).

    Note Note

    The procedure describes the data transfer to a standard DataStore object. There are no activation steps or activation request for write-optimized DataStore objects.

    End of the note.

    More information: Creating HybridProviders,

    Creating DataStore Objects, Creating InfoObjects

  4. Create a transformation with the DataSource as the source and the InfoProvider as the target.

    More information: Creating Transformations

  5. If you want to process the data further after the real time data acquisition process, and want to update further InfoProviders, create the appropriate InfoProviders and transformations.

  6. Create an InfoPackage for real-time data acquisition for the DataSource.

    Note Note

    PSA requests for Web services remain open across several load processes. When you transfer data using Web services, you use this type of InfoPackage to define the size of the request or the time lapsed before the request is closed.

    End of the note.

    When you save the InfoPackage the InfoPackage and the related DataSource are visible in the monitor for real-time data acquisition (transaction RSRDA) in area Non-Assigned Objects.

    More information: Creating InfoPackages for Real-Time Data Acquisition

  7. If you want to connect the further processing and updating processes with Real-Time Data Acquisition, and you have created the relevant objects in step 5, create an appropriate process chain. In the start process of the chain choose the scheduling option Using Meta-Chain or API, activate and schedule the chain.

    More information: Creating Process Chains

  8. Create a data transfer process for real-time data acquisition with the DataSource as the source and the InfoProvider as the target.

    More information: Creating Data Transfer Processes for Real-Time Data Acquisition

  9. Switch from the DTP to the monitor for Real-Time Data Acquisition.

    In DTP maintenance, on the Execute tab page, choose Assign (Assign).

    The monitor for real-time data acquisition appears. The DTP is displayed in area Non-Assigned Objects under the DataSource for which you created the InfoPackage, and is therefore assigned to the DataSource.

    Note Note

    You can update the data from the DataSource into multiple DataStore objects. In this case, assign the corresponding data transfer processes created earlier to the daemon (using the DataSource). In the context menu for the DataSource, choose Assign DTP.

    End of the note.

  10. Choose Create Daemon (Create Daemon) to define a new daemon.

  11. Assign the DataSource (and the InfoPackage and DTP) to the daemon.

    In area Non-Assigned Nodes select the DataSource, in the context menu of the DataSource chooseAssign Daemon, and assign the required daemon number. The InfoPackage and the DTP are now available for the daemon to process.

  12. Assign the process chain created earlier to the data transfer process.

    In the context menu of the DTP choose Assign Subsequent Process Chain.

    Note Note

    You can assign more than one subsequent process chain to a data transfer process.

    End of the note.

  13. In the monitor for real-time data acquisition, start the daemon.

    In the context menu for the daemon, choose Start Daemon with All InfoPackages.

    The daemon waits for a free background job.

Result

When the Web service returns data to the BW system, it is updated to the PSA table.

While the background job is running, the daemon checks the PSA at regular intervals.

Once the data has been successfully updated to the PSA, the daemon starts the data transfer process for real-time data acquisition. This updates the data from the PSA table to the InfoProvider. For DataStore objects (of the HybridProvider) the changes are logged in the change log request belonging to the object. The request that transfers the data to the PSA table (PSA request), the data transfer process request and the change log request for each DataStore object have a 1:1 ratio to each other. The data is activated automatically and written to the change log. This allows you to skip an additional activation step in the DataStore object. Data is not written to the DataStore object's activation queue.

The data is now available for analysis and reporting purposes.

If you have assigned a subsequent process chain to the data transfer process, start this process chain when the daemon closes a request.

Note

You can also use the data transfer with Web services without any processing from the daemon, and then update the data from the PSA using a standard DTP. You can also transfer master data to the BI system with a Web service in this way. More information: Transferring Data Using Web Services (Standard).