Using Query Extract to Export Data from Business warehouse, With Pros and Cons Analyzed

Applies to:
SAP BW 3.X & BI 7.0. For more information, visit the Business Intelligence homepage.

Summary
This article summarizes the methodology, advantages & limitations of using query extract vs Infospoke for exporting data from BW environment. Author: Ravi Ramasamy

Company: IBM India Pvt Ltd., Created on: 20 December 2008

Author Bio
Ravi Ramasamy works as a BI Consultant at IBM India, Bangalore. He has 3.5 years of experience in IT industry out of which 3 years are as a SAP BI Consultant. He has also worked on relevant SAP technical areas like BW-BPS & ABAP.

SAP COMMUNITY NETWORK 2008 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 1

Using Query Extract to Export Data from Business warehouse, With Pros and Cons Analyzed

Table of Contents
Introduction .........................................................................................................................................................3 Query Extract An overview ..........................................................................................................................3
Step 1: .........................................................................................................................................................................3 Step 2: .........................................................................................................................................................................3

Automation of Query Extract:..........................................................................................................................4 Query Extract vs Infospoke Head to Head: .................................................................................................4 Outlook:...........................................................................................................................................................4 Related Content..................................................................................................................................................5 Disclaimer and Liability Notice............................................................................................................................6

SAP COMMUNITY NETWORK 2008 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 2

Using Query Extract to Export Data from Business warehouse, With Pros and Cons Analyzed

Introduction
In cases where data from BW environment is to be exported to a third party system, so often Infospoke is sought & considered as the unique chap for the job. But there are a few functionalities provided by SAP, which could serve the purpose better (depending on the scenario). In this article, I have taken the approach of RSCRM_BAPI - using query as a source of extract for exporting data and I have analyzed the advantages and limitations of this approach vs the infospoke. Also this article outlines a set of guidelines to pick the best suited approach for a given scenario. Query Extract An overview RSCRM_BAPI is a BW Transaction, where an extract structure (query view) can be built on a BEx query, by means of which the data export can be configured & achieved to a third party system (through the application server) or a DB table. An extract structure is nothing but replica of a query and it reflects all the query definitions such as rows, columns, slicers (free chars), variables, etc. Step 1: T-Code RSCRM_BAPI Choose the Bex query & initialize creation of an extract structure (view) Step 2: Modify the structure (if needed as per the scenario). Filters, Variables or even Conditions can be specified. This view can be executed to preview the data before scheduling the extract.

Note: The filter restrictions we can make on this view are inbound within in the querys definition (since the query is the source for this extract). Step 3: Save the extract structure with an appropriate name. Step 4: Configure the target destination (table / file path) for the extract with a Start condition and schedule the Extract

----------This extract can be scheduled just like an infopackage or a process chain. The start condn can be immediate / periodically from a date or time / after the completion of a job or an event.

SAP COMMUNITY NETWORK 2008 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 3

Using Query Extract to Export Data from Business warehouse, With Pros and Cons Analyzed

Automation of Query Extract: If you want to automate the query extract using a process chain, all you need to do is just create an event, specify the start condition of the query extract as after event and use a Z-Program in your process chain to raise the event by calling the FM RSSM_EVENT_RAISE and passing the event name & parameter, which in turn will trigger the extract. Query Extract vs Infospoke Head to Head: a) Advantages: An Infospoke can be built only on Data Targets - Infocube, ODS & InfoObject (Texts/Attributes), whereas the query extract can work for all the Info-providers (including Multiproviders & Infosets). In cases, where we have to export homogeneous data from more than a Cube / ODS, either we have to build two infospokes or employ a single infospoke on one of the cubes, append its structure & populate the fields from other cube(s) using complex BAdi Transformations. But this would be a very simple & straight forward approach with query extract, provided a Multiprovider comprising all the targets and a query on it are already in place. Query Extract also possesses delta extraction similar to infospoke Query Extract gains greater flexibility & ease of change and will have minimum dependencies / cross-impacts, when compared with Infospokes. b) Limitations: Even if there is any change in the source querys structure, it will not be reflected in the query extract (view). It will be still pointing to the version dating back to pre-change of query. So if there is any major change such as removal / addition of a field in the source query, then a new query extract should be created to reflect the changes. Query Extract primarily encompasses the front end features and unlike Infospoke, data transformations (ABAP routines) are not possible with query extract. Outlook: To sum up, Infospoke will be a good option if the data to be exported has to undergo some transformations or the source data is more dynamic of nature. For other cases, query extract can serve the purpose with equal effectiveness and greater flexibility.

SAP COMMUNITY NETWORK 2008 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 4

Using Query Extract to Export Data from Business warehouse, With Pros and Cons Analyzed

Related Content
SAP Service Marketplace SDN BW 3.5 Help For more information, visit the Business Intelligence homepage.

SAP COMMUNITY NETWORK 2008 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 5

Using Query Extract to Export Data from Business warehouse, With Pros and Cons Analyzed

Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.

SAP COMMUNITY NETWORK 2008 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com 6