Vous êtes sur la page 1sur 33

Session ID: XI201 SAP XI and SAP BI Integration

Lothar Henkes, SAP AG Wolfgang Fassnacht, SAP AG John Ta, SAP Labs, LLC. Anthony Andreacchio, SAP Labs, LLC.

Introduction BW-XI Integration Technical Details FAQs Summary

Process Integration Highlights


Adapter Framework (JCA based)
Integrate application systems and business partners via resource adapters Adapter development kit Certification of third party adapters

B2B enablement & Industry Standards Support


Maintain Collaboration Partner Data Partner Connectivity Kit Business packages for Industry Standards

Cross-Component Business Process Management


Design, execute and monitor automated processes across applications and systems BPEL support

Pre-delivered Integration Content


Applications like SRM, CRM, SCM etc deliver integration content within the Integration Repository

SAP AG 2004, SAP TechEd / XI201 / 4

SAP Business Intelligence (BI) Highlights


Data Warehousing (SAP BW Administrator Workbench)
Extraction, transformation, and loading Data warehouse management Business modeling

BI Platform
Online analytical processing (OLAP) Data Mining Alerting Meta Data Repository Planning Framework

BI Suite of Tools (SAP BW Business Explorer)


Query Design Reporting and Analysis Visualization Web Application Design Collaboration (e.g. Information Broadcasting)

Pre-configured Business Content

SAP AG 2004, SAP TechEd / XI201 / 5

SAP XI and SAP BI integration scenarios (1)


Business Content Scenario SRM
Global Spend Analysis Scenario
Visualize global spend across organizational

Components
SAP BW SAP XI SAP MDM Purchasing systems

boundaries in order to compare vendor prices, optimize contracts and consolidate suppliers.
Purchase orders, PO changes, and invoices are

extracted into SAP BW from procurement systems via XI


Master and Key mapping data are extracted from SAP

MDM/CI into SAP BW


Supplier data, product, and product categories are

consolidated by SAP MDM

Purchase orders

Invoices

SAP XI
XML Copy XML

Purchaser

BI Global Spend

Suppliers

SAP AG 2004, SAP TechEd / XI201 / 6

SAP XI and SAP BI integration scenarios (2)


Business Content Scenario Retail
Store Connectivity Scenario
Increase profitability by utilizing

Components
POS1
SAP XI SAP BW SAP POS DM Store Systems

data for controlling of retail processes and by understanding customer behavior in a better way.

SAP XI as single point to collect POS sales information

as mass data from (3thd party) store systems via an open industry specific interface (ARTS/IX-Retail2 compliant).
Using SAP XI as additional source for SAP BW improved by Retail POS Data Management to

ensure better data quality

Store

Channel Manager SAP XI


XML POS Transactions XML

Point of Sale 2 Association for Retail Technology Standards / International XML Retail Cooperative
SAP AG 2004, SAP TechEd / XI201 / 7

SAP XI and SAP BI integration scenarios Benefits


Business Content Scenario SRM
Why using XI in this scenario
XI is used to distribute transaction data between many systems XI is also used for Master data distribution For analysis the data is also distributed to BW via XI Therefore extracting the data to BW from many source systems is not

required

Business Content Scenario Retail


Why using XI in this scenario
A push of message type data to BW is required XI supports quality of service Exactly once in order in push scenarios Stores deliver the data according to ARTS/IX-Retail XI supports ARTS/IX-Retail In case the stores deliver the data as flat files they can be easily

transfered to XML format via XI

SAP AG 2004, SAP TechEd / XI201 / 8

BW and XI
The integration of BW and XI offers additional possibilities
Reducing point to point connections in complex landscapes Exactly Once in Order using proxies for push scenarios All sender formats (such as different XML flavours, flat files) can be mapped in XI

Scheduled data loads (BW functionality) and event triggered data transfer (XI functionality) complement each other.

SAP BW
SAPI UD DB Connect Connect File BAPI Proxy

E F

SAP XI
G H

SAP AG 2004, SAP TechEd / XI201 / 9

Introduction BW-XI Integration Technical Details FAQs Summary

How to connect BW and XI Overview


Sender

XI
Outbound Interface Message in Sender Format

BW (Receiver)

XI Adapter
For example: Java/ABAP Proxies SOAP Adapter Plain HTTP Adapter JDBC Adapter JMS Adapter RFC Adapter IDoc Adapter Mail Adapter and so on

Integration Server

Inbound Interface Message in BW (=Receiver) Format

Transformation Monitoring

Proxy Adapter

Proxy Delta Queue

SAP AG 2004, SAP TechEd / XI201 / 11

How to connect BW and XI Details


BW
myself
RFC Function Module Push DataSource Delta Queue Request (Pull)

XI Proxy Framework

RFC Framework

ICF Web Service SOAP/RFC

Proxy

Status Management

tRFC

XI
ProxyAdapter
RFC-Adapter SOAP-Adapter 3rd Party Application 3rd Party Application

XI Integration Server

SENDER
SAP AG 2004, SAP TechEd / XI201 / 12

Five Steps to Bring It All Together

BW

5
Delta Load from Queue

4
Push Data via Proxy

Queue
ODS PSA
Extr. Str.

XI Exchange Interface

3 File DataSource for Trans. Data


Comm. Str. Rules Tran. Str.
Create by Hand Initialize without Data Transfer

myself DataSource
Comm. Str. Rules Tran. Str. Extr. Str.

RFC Function Module with DataSource Interface


Extr. Str.

Generate

SAP AG 2004, SAP TechEd / XI201 / 13

Five Steps to Bring It All Together


Create by Hand

Create InfoSource with transfer rules to flat file

Generate BWDataSource with SOAPInterface

InfoObjects for Trans.Structure definition

SAP AG 2004, SAP TechEd / XI201 / 14

Generated Function Module


2
Generate

Tcode SE37

RFC Function Module with DS-Name Table

SAP AG 2004, SAP TechEd / XI201 / 15

Activating the Delta Queue


3 Initialize Without Datatransfer Queue
Extr. Str.

Transaction RSA7

SAP AG 2004, SAP TechEd / XI201 / 16

Push Data via Proxy Generation


4
Push Data via Proxy

Design
SAP BW 3.5
DataSource Delta Queue RFC Function Module BW XXX Proxy-Implementation Call Function BW XXX 4

Queue
Extr. Str.

Implement Proxy Interface

Proxy Class Z_DataToBW

SAP XI 3.0 Integration Repository


Message Interface DataToBW

Generate Proxy Class

Create Msg Interface

Import RFC Interface

RFC BW XXX

SAP AG 2004, SAP TechEd / XI201 / 17

Delta Load from Queue


5
Delta Load from Queue

ODS PSA

SAP AG 2004, SAP TechEd / XI201 / 18

XI Proxy Generation / Overview


Design
SAP BW 3.5
DataSource Delta Queue RFC Function Module BW XXX Proxy-Implementation Call Function BW XXX 4 Implement Proxy Proxy Class Interface Z_DataToBW Generate Proxy Class
Sender Service Outbound Interface Comm.-Channel

Configuration

Sender/Interf./Namesp. Comm.-Channel
Sender/Interface/Namespace

Receiver
Sender/Interf./Namesp./Receiver

SAP XI 3.0 Integration Repository


Message Interface DataToBW

Inbound Interface

2
Create Msg Interface

Sender/Receiver/Interf./Namesp.

Import RFC Interface

RFC BW XXX

Comm.-Channel
Receiver Service Inbound Interface Comm.-Channel

SAP AG 2004, SAP TechEd / XI201 / 19

XI Proxy Generation / Design


SAP XI (Integration Repository) 1
Import RFC Interface

SAP BW 3.5

2
Create Message Interface

3a
Generate Proxy Class (Transaction SPROXY or SE80*)

* From WAS 6.40 on you can generate ABAP proxies alternatively via SE80 Choose Package Context Menu ( Enterprise Service/Web Service Proxy Object XI Repository)
SAP AG 2004, SAP TechEd / XI201 / 20

XI Proxy Generation / Design II


3b
Generate Proxy Class

SAP BW 3.5 4
Implement Proxy Interface

Example Implementation*

Replace the highlighted elements of the coding to fit to your environment.


* This coding is for demonstration purposes only. It is not meant to be a delivered SAP product. Therefore SAP cannot give any OSS support concerning problems that might occur when using it.
SAP AG 2004, SAP TechEd / XI201 / 21

XI Proxy Generation / Overview


Design
SAP BW 3.5
DataSource Delta Queue RFC Function Module BW XXX Proxy-Implementation Call Function BW XXX 4 Implement Proxy Proxy Class Interface Z_DataToBW Generate Proxy Class
Sender Service Outbound Interface Comm.-Channel

Configuration

Sender/Interf./Namesp. Comm.-Channel
Sender/Interface/Namespace

Receiver
Sender/Interf./Namesp./Receiver

SAP XI 3.0 Integration Repository


Message Interface DataToBW

Inbound Interface

2
Create Msg Interface

Sender/Receiver/Interf./Namesp.

Import RFC Interface

RFC BW XXX

Comm.-Channel
Receiver Service Inbound Interface Comm.-Channel

SAP AG 2004, SAP TechEd / XI201 / 22

XI Proxy Generation / Configuration

Collaboration Profile for Sender Service (e.g. File, IDOC, )


Sender Service Outbound Interface Comm.-Channel XYZ (Any Business System/Process/Service) OUT1 CH1

Routing Rules Receiver Determination


Sender = XYZ Interface = OUT1 Namespace = MySpace Receiver=BW1

Interface Determination
Sender Interface Namespace Receiver = XYZ = OUT1 = MySpace = BW1 Inbd. Interface = DataToBW

Collaboration Agreement
Receiver Agreement: Msg. Parameter (see Int.Determ.) Comm.-Channel = CH2

Collaboration Profile for Receiver Service (BW)


Receiver Service Inbound Interface Comm.-Channel BW Business System BW1 Msg. Interface DataToBW CH2 (Adapter Type = XI; System, Login, )

SAP AG 2004, SAP TechEd / XI201 / 23

Introduction BW-XI Integration Technical Details FAQs Summary

FAQs
Will extraction from SAP applications be replaced by XI?
There are no plans to replace the existing extractors XI technology complements the options for SAP applications to provide the optimum way of data replication to BW

Currently XI supports push-scenarios. Are there plans to enhance XI with the capability to actively load data (pull, scheduled)?
Currently there are no concrete plans to build this functionality. File-, JMS-, JDBC-Adapter support a polling mode

Will data distribution from BW via Open Hub be replaced by XI?


There are no plans to replace this functionality.

Today a Configuration Guide describes in detail how to integrate BW and XI. Will there be major changes to this procedure?
Today these steps need to be performed manually as introduced in this presentation. Future plans are to offer automated configuration.
SAP AG 2004, SAP TechEd / XI201 / 25

Introduction BW-XI Integration Technical Details FAQs Summary

Summary

Existing integration scenarios Positioning SAP BW / SAP XI


Steps to integrate SAP BW / SAP XI


Future directions

SAP AG 2004, SAP TechEd / XI201 / 27

Further Information

Service Marketplace Integration Landscape


BW-System needs to be integrated in the XI Landscape. For details please refer to the following Configuration Guide http://service.sap.com/XI Media Library Guides Configuration Guide SAP XI 3.0

BW SOAP Data Source


Feature available since BW 30b For details please refer to the following How to Guide http://service.sap.com/BW Media Library Guides How to Send XML Data to BW

XI Proxy Framework
For details please refer to the following How to Guide http://service.sap.com/BW Service&Implementation How To Papers BW 3.5

SAP AG 2004, SAP TechEd / XI201 / 28

SAP Developer Network


Look for SAP TechEd 04 presentations and videos on the SAP Developer Network. Coming in December. http://www.sdn.sap.com/

SAP AG 2004, SAP TechEd / XI201 / 29

Questions?

Q&A
SAP AG 2004, SAP TechEd / XI201 / 30

Feedback
Please complete your session evaluation. Be courteous deposit your trash, and do not take the handouts for the following session.

Thank You !

SAP AG 2004, SAP TechEd / XI201 / 31

Disclaimer

Please note that this document is subject to change and may be changed by SAP at any time without notice. The document is not intended to be binding upon SAP to any particular course of business, product strategy and/or development.

SAP AG 2004, SAP TechEd / XI201 / 32

Copyright 2004 SAP AG. All Rights Reserved


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, Outlook, and PowerPoint 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, and Informix are trademarks or registered trademarks of IBM Corporation in the United States 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, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered

trademarks of Citrix Systems, Inc.


HTML, XML, XHTML and W3C 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.
MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver 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 the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated

companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
SAP AG 2004, SAP TechEd / XI201 / 33

Vous aimerez peut-être aussi