Open Hub Know How Network May 1, 2003 Bryan Katis Platinum Consultant BW RIG, SAP Labs SAP AG 2003, Open Hub, B. Katis 2 2 Agenda Overview: BW Open Hub Service Open Hub Features InfoSpoke Details Outlook Q&A SAP AG 2003, Open Hub, B. Katis 3 3 The Corporate Information Factory Directly supported components of SAP and SAP BW DSS Applications Departmental Data Marts EDW Marketing AcctgFinance Sales ERP CRM eComm. Bus. Int. ETL Global ODS Oper. Mart Exploration warehouse/ data mining Source:Bill Inmon Staging Area local ODS Dialogue Manager Cookie Cognition Preformatted dialogues cross media Storage mgr Near line Storage Web Logs Session Analysis Internet ERP Corporate Applications Changed Data Granularity Manager Sources mySAP Others APO CRM SEM E-Analytics BW SAP AG 2003, Open Hub, B. Katis 4 4 The Corporate Information Factory BW Open Hub Service DSS Applications Departmental Data Marts EDW Marketing AcctgFinance Sales ERP CRM eComm. Bus. Int. ETL Global ODS Oper. Mart Exploration warehouse/ data mining Source:Bill Inmon Staging Area local ODS Dialogue Manager Cookie Cognition Preformatted dialogues cross media Storage mgr Near line Storage Web Logs Session Analysis Internet ERP Corporate Applications Changed Data Granularity Manager Open Hub Service SAP AG 2003, Open Hub, B. Katis 5 5 Open Data Warehouse Architecture SAP AG 2003, Open Hub, B. Katis 6 6 InfoCubes BW Operational Data Store ODS Objects BW Server BW Server External DataMart Relational Table Flat File ETL Tools Data Provider Flat File Relational DB Link mySAP.com Applications e-Business SAP BW Open Staging and Open Hub Services Master Data ODBO EDW SAP AG 2003, Open Hub, B. Katis 7 7 Open Hub Service - Details Controlled distribution of consistent data Target: file or DB table Central monitoring Select filter criteria and columns Scheduling Full or delta mode InfoCubes ODS Objects BW Server External DataMart... Relational Table Flat File Master Data SAP AG 2003, Open Hub, B. Katis 8 8 Information Distribution - Scenarios SAP BW Analytical Application Sales Data Mart Regional Data Mart Legacy Application Open Hub Service BW Open Hub Platform BW as an Information Hub Controlled Distribution of consolidated and integrated data BW Data Mart SAP AG 2003, Open Hub, B. Katis 9 9 Open Hub Service - Details Data transfer in Open Hub Service BW DB Table /BIC/0H. Open Hub Service InfoCubes Flat file.csv Data Marts BW S-API Other Data warehouses/marts Other system (ERP, CRM, etc) DB connect type functionality Push Master Data ODS Pull SAP AG 2003, Open Hub, B. Katis Open Hub - Functional Details Meta object InfoSpoke for asynchronous data transfer of mass data Modelling Data Sources: InfoCube, ODS Object, and Master Data (Attributes and Text) Full and Delta Processing (Delta for InfoCubes and ODS Objects) Distribution targets: File (.csv format), BW DB Table Aggregation, Selection, Transformation Scheduling Direct Scheduling Process Chain Integration Monitoring AWB-Monitor Functions Technical Realization Optimized Read Access for Star Schema Transformation SAP AG 2003, Open Hub, B. Katis Model: Design-Time BW Extern Data Source Metadata, Selectabilty, Data Data Target Metadata, Data Transformation Process Reference to Data Source Reference to Transformation Reference to Data Variant Scheduler Periodicity, Starting condition Selections for data source SAP AG 2003, Open Hub, B. Katis Model: Run-Time BW Extern Data Source Data Data Target Data Transformation Request Selections for data source Data package(in) Data package(out) Log/Monitor Reference to Data Source Reference to Transformation Reference to Data Request Broker SAP AG 2003, Open Hub, B. Katis Accessing the Open Hub Service Transaction RSBO or via AWB Tools menu SAP AG 2003, Open Hub, B. Katis InfoSpoke Definition General tab Data Source InfoCube ODS Object InfoObject (Attributes) InfoObject (Texts) Destination For Open Hub use only Uses InfoSpoke name by default The Open Hub Destination (as an object) is generated during the activation Extraction Mode Full or Delta Records per Data Package SAP AG 2003, Open Hub, B. Katis InfoSpoke Destination Destination Tab Automatically generated during destination activation Destination target options.csv file on front end or Application Server DB table name: /BIC/0H SAP AG 2003, Open Hub, B. Katis Special Features with Database Table Extractions Deleting Tables Before Extraction With an extraction to a database table, you have the option of getting the history of the data or only storing the new data in the table. Choose Delete Table Before Extraction when defining your destination if you want to overwrite the fields. In this case, the table is completely deleted and regenerated before extraction takes place. We recommend you use this mode when the table is not to contain a history of the data. If you do not select this option, the extracted data records are added to the database table using an INSERT. We recommend you use this mode when the history of the data is to be retained. Key Fields from the Table With extractions to a database table, you have to note that the generated DB table can have a maximum of 16 key fields. Therefore, check whether your field list includes more key fields. If this is the case, you can set the Technical Key indicator. A key is then added, consisting of the technical fields OHREQUID (open hub request SID), DATAPAKID (data package ID), and RECORD (running number of a data record to be added to the table within a data package). These fields then display the individual key fields for the table. SAP AG 2003, Open Hub, B. Katis Scenarios Using a target table with a technical key would be useful in the following instances: Delta extraction from ODS objects: the data is read in the change log, in which several records with different RECORDMODEs can exist for a specific, semantic key (after/before image). In general, extracting to a table with the semantic key from the ODS object leads to duplicate records and, ultimately, to a short dump. Extracting in full mode to a table that does not need to be deleted before the extraction. If, for an extracted record, one already exists with the same key, a short dump occurs due to duplicate records. If the source has more than 16 key fields, no DB table can be created with these key fields. In this case, therefore, the table has to include a technical key. SAP AG 2003, Open Hub, B. Katis Defining the Extract Structure Define Aggregation Level SAP AG 2003, Open Hub, B. Katis InfoSpoke Definition Selection Excludes possible as well SAP AG 2003, Open Hub, B. Katis Transformation via Business Add-In (BAdI) Enhanced User Exit Handling SAP AG 2003, Open Hub, B. Katis Implementing BAdIs Enter short text for the implementation. If you do not specify an InfoSpoke under Defined filters, then this implementation is valid for all InfoSpokes. This means that this is called up for all InfoSpokes during the extraction. SAP AG 2003, Open Hub, B. Katis Implementing BAdIs (continued) Choose Implementation type: ABAP Code or Formula Builder Double-click on Transform method to enter ABAP code. SAP AG 2003, Open Hub, B. Katis Change an InfoSpokes Extraction Layout You can manipulate the Target Structures field order. Note: Do not remove or change any of the structures fields or attributes otherwise extraction errors will occur. Check the paper How-Tochange an InfoSpokes extraction layout for more detailed steps. SAP AG 2003, Open Hub, B. Katis Open Hub Process Chain Integration Designing complex Dataflow Processes SAP AG 2003, Open Hub, B. Katis InfoSpoke Monitoring Monitoring Runtime Results in Detail SAP AG 2003, Open Hub, B. Katis Open Hub Delta Handling You can deactivate the delta administration. Then an additional delta request is not possible. At the same time, the status of all source requests that have already been read is reset to Not Yet Read. The delta administration is also deactivated if one of the following events occurs: A request that has already been extracted is deleted in the source object. A request that has not yet been extracted is condensed in the source object. You can reactivate the delta administration. Then a delta request is once again possible. Note: Delta requests should be reset individually rather than deactivating all deltas at once! SAP AG 2003, Open Hub, B. Katis Open Hub Destination Table DDIC Description Meta Data Information for Extraction Table SAP AG 2003, Open Hub, B. Katis Open Hub Destination Table Contents Extraction Format DB Table SAP AG 2003, Open Hub, B. Katis Meta Data Description File (S_DEST01.TXT) Data File (DEST01.CSV) Open Hub Destination File Description and Data SAP AG 2003, Open Hub, B. Katis ODBC Stage Open Hub Scenario for one step data delivery SAP BW ODBC Stage RDBMS DataStage Jobs + InfoSpoke Non SAP DB How to implement: DataStage triggers InfoSpoke via API and then starts DS Job BW Process Chain step launches InfoSpoke delivery and then starts DS Job (possible via ABAP process type) SAP AG 2003, Open Hub, B. Katis Changing Open Hub Destinations for Files Whenever I save a file to the Application Server it always gets sent to the work directory. How can I change the path my files get sent to on the Application Server? The default separator for.csv files is a semicolon. How can I change this to something else like a colon, comma, etc.? The value that is used for the Field separator is a global setting maintained in the IMG. Transaction SPRO -> Business Information Warehouse -> Links to Other Systems -> Link Between Flat File and BW -> Set options for uploading flat files. SAP AG 2003, Open Hub, B. Katis Changing Open Hub Destinations for Files (cont.) Solution: Go to transaction SE11 or SE16, and choose table RSBFILE. Select the record based on the OHDEST field and OBJVERS = A, and then Change. NOTE: When InfoSpokes are transported, the system will use the default separator (from the IMG) and the work directory path (DIR_HOME) from the target system. So you would need to manually change this table in each of the target systems. SAP AG 2003, Open Hub, B. Katis Transports InfoSpoke definitions and the Open Hub Destinations are transportable using the Transport Connection. They are also both changeable in the target systems via the Object Changeability option. This adds the flexibility of changing file paths for the destinations, or selection criteria for an InfoSpoke for each target system, for example. SAP AG 2003, Open Hub, B. Katis Open Hub Pricing Whenever you extract data from the SAP BW environment into 3rd-party target systems your SAP BW Enterprise Data Warehouse functions as an Open Hub Platform. The Open Hub Service is one tool among other functions to accomplish this task. Additionally, DataBrowser functionality (ListCube transaction) or CRM interfaces can also be used to export data, and many other options are possible. Extracting data from SAP BW by any means requires additional licensing! For additional pricing information please contact your SAP representative. SAP AG 2003, Open Hub, B. Katis Outlook beyond BW 3.x Logical file name handling in order to enable full access to the file system of the Application Server Separator maintenance in the InfoSpoke definition Variables used in Selection Additional Data Sources like BEx Query and Hierarchies Additional destination formats like ASCII and XML Remote access to external database tables Sorting of fields for the output table (without BAdI workaround) Transformation Library integration for transformations Deltas available for additional Data Sources SAP AG 2003, Open Hub, B. Katis Public Web: Solutions Business Intelligence SAPNet: -> SAP NetWeaver -> SAP Business Information Warehouse Documentation Enhancement-> Documentation How-To Guide-> Services & Implementation -> HOW TO Guides -> Guide List BW 3.x Further Information SAP AG 2003, Open Hub, B. Katis Summary Openness to extract data from BW All BW data objects are supported for extraction Delta tracking for each target system Scheduling and central monitoring SAP BW can serve as an enterprise information hub (EDW) and feed data to any downstream system SAP AG 2003, Open Hub, B. Katis Q&A Questions SAP AG 2003, Open Hub, B. Katis No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix and Informix Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries. ORACLE is a registered trademark of ORACLE Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, MultiWin and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. JAVA is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One. SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are trademarks of their respective companies. Copyright 2003 SAP AG. All Rights Reserved