Upload
karthick-s-nair
View
115
Download
4
Tags:
Embed Size (px)
DESCRIPTION
Usefull for integrating XI to BI
Citation preview
Session ID: XI201SAP XI and SAP BI Integration
John Ta, SAP Labs, LLC.
Anthony Andreacchio, SAP Labs, LLC.
Lothar Henkes, SAP AG
Wolfgang Fassnacht, SAP AG
FAQs
Summary
Introduction
BW-XI Integration Technical Details
SAP AG 2004, SAP TechEd / XI201 / 4
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
Process Integration Highlights
SAP AG 2004, SAP TechEd / XI201 / 5
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 Business Intelligence (BI) Highlights
SAP AG 2004, SAP TechEd / XI201 / 6
BI Global Spend
Business Content Scenario SRMGlobal Spend Analysis Scenario
Visualize global spend across organizational 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
Invoices
CopyPurchaser Suppliers
Purchaseorders
XML XMLSAP XI
SAP XI and SAP BI integration scenarios (1)
Components SAP BW SAP XI SAP MDM Purchasing systems
SAP AG 2004, SAP TechEd / XI201 / 7
Business Content Scenario RetailStore Connectivity Scenario
Increase profitability by utilizing POS1 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
SAP XI and SAP BI integration scenarios (2)
Components SAP XI SAP BW SAP POS DM Store Systems
1 Point of Sale2 Association for Retail Technology Standards /
International XML Retail Cooperative
StoreChannel Manager
POS Transactions
XML
XML
SAP XI
SAP AG 2004, SAP TechEd / XI201 / 8
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 XI and SAP BI integration scenarios Benefits
SAP AG 2004, SAP TechEd / XI201 / 9
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 datatransfer (XI functionality) complement each other.
UDConnect
DBConnect File Proxy
B
SAP BW
SAP XIC D
HF G
BAPI
E
SAPI
A
FAQs
Summary
Introduction
BW-XI Integration Technical Details
SAP AG 2004, SAP TechEd / XI201 / 11
Proxy Adapter
BW (Receiver)XI
Delta Queue
Sender
IntegrationServer
Proxy
XI Adapter
Outbound Interface
Message inSender Format
Inbound Interface
Message in BW (=Receiver)
Format
Transformation
Monitoring
For example:
Java/ABAP Proxies
SOAP Adapter
Plain HTTP Adapter
JDBC Adapter
JMS Adapter
RFC Adapter
IDoc Adapter
Mail Adapter
and so on
How to connect BW and XI Overview
SAP AG 2004, SAP TechEd / XI201 / 12
myselfDataSource
Delta QueueRFC FunctionModule
Request (Pull)
ICF
Web Service
3rd Party Application
SOAP/RFC
XI Proxy Framework
Proxy
XI Integration Server
3rd Party Application
Push
Proxy-Adapter
RFC-Adapter
BW
XI
SOAP-Adapter
RFC Framework
Status Management
SENDER
tRFC
How to connect BW and XI Details
SAP AG 2004, SAP TechEd / XI201 / 13
RFC FunctionModule withDataSource
Interface
BW
FileDataSource for
Trans. Data
Comm. Str.
Tran. Str.
Rules
myselfDataSource
Comm. Str.
Tran. Str.
Rules
Extr. Str.Extr. Str.
QueueExtr. Str.
PSAODS
XI ExchangeInterface
Create by Hand1
Generate2
Initialize withoutData Transfer
3
Push Datavia Proxy
4
Delta Loadfrom Queue
5
Five Steps to Bring It All Together
SAP AG 2004, SAP TechEd / XI201 / 14
Five Steps to Bring It All Together
Create by Hand1
InfoObjects for Trans.Structure
definition
CreateInfoSource withtransfer rules
to flat file
Generate BW-
DataSourcewith SOAP-
Interface
SAP AG 2004, SAP TechEd / XI201 / 15
Generated Function Module
TcodeSE37
RFC FunctionModule withDS-Name
Table
Generate2
SAP AG 2004, SAP TechEd / XI201 / 16
Activating the Delta Queue
TransactionRSA7
InitializeWithout
Datatransfer
3 QueueExtr. Str.
SAP AG 2004, SAP TechEd / XI201 / 17
Push Data via Proxy Generation
Design
SAP XI 3.0
SAP BW 3.5DataSource
RFC Function Module
BW XXX
Integration Repository
Delta Queue
Message InterfaceDataToBW
CreateMsg Interface
2
RFCBW XXX
ImportRFC Interface
1
Proxy ClassZ_DataToBW
GenerateProxy Class
3
Proxy-ImplementationCall Function BW XXX
ImplementProxy Interface
4
Push Datavia Proxy
4
QueueExtr. Str.
SAP AG 2004, SAP TechEd / XI201 / 18
Delta Load from Queue
Delta Loadfrom Queue
5
PSAODS
SAP AG 2004, SAP TechEd / XI201 / 19
XI Proxy Generation / Overview
Sender/Receiver/Interf./Namesp. Comm.-Channel
Sender/Interf./Namesp. Comm.-Channel
Sender/Interface/Namespace Receiver
Sender/Interf./Namesp./Receiver Inbound Interface
Receiver Service Inbound Interface Comm.-Channel
Sender Service Outbound Interface Comm.-Channel
Configuration
SAP XI 3.0
SAP BW 3.5DataSource
RFC Function Module
BW XXX
Integration Repository
Delta Queue
Message InterfaceDataToBW Create
MsgInterface
2
RFCBW XXX
ImportRFC Interface1
Proxy ClassZ_DataToBW
GenerateProxy Class
3
Proxy-ImplementationCall Function BW XXX
ImplementProxy
Interface
4
Design
SAP AG 2004, SAP TechEd / XI201 / 20
SAP BW 3.5SAP XI (Integration Repository)
XI Proxy Generation / Design
CreateMessageInterface
2
ImportRFC Interface
1
GenerateProxy Class(TransactionSPROXY orSE80*)
3a
* 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 / 21
SAP BW 3.5
XI Proxy Generation / Design II
GenerateProxy Class
3bImplementProxy Interface
ExampleImplementation*
* 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.
Replace the highlighted elements of the coding to fit to your environment.
4
SAP AG 2004, SAP TechEd / XI201 / 22
XI Proxy Generation / Overview
Sender/Receiver/Interf./Namesp. Comm.-Channel
Sender/Interf./Namesp. Comm.-Channel
Sender/Interface/Namespace Receiver
Sender/Interf./Namesp./Receiver Inbound Interface
Receiver Service Inbound Interface Comm.-Channel
Sender Service Outbound Interface Comm.-Channel
Configuration
SAP XI 3.0
SAP BW 3.5DataSource
RFC Function Module
BW XXX
Integration Repository
Delta Queue
Message InterfaceDataToBW Create
MsgInterface
2
RFCBW XXX
ImportRFC Interface1
Proxy ClassZ_DataToBW
GenerateProxy Class
3
Proxy-ImplementationCall Function BW XXX
ImplementProxy
Interface
4
Design
SAP AG 2004, SAP TechEd / XI201 / 23
XI Proxy Generation / Configuration
Collaboration Agreement Receiver Agreement: Msg. Parameter (see Int.Determ.) Comm.-Channel = CH2
Routing Rules
Receiver DeterminationSender = XYZInterface = OUT1Namespace = MySpace
Interface DeterminationSender = XYZInterface = OUT1Namespace = MySpaceReceiver = BW1
Receiver=BW1 Inbd. Interface = DataToBW
Collaboration Profile for Receiver Service (BW) Receiver Service BW Business System BW1 Inbound Interface Msg. Interface DataToBW Comm.-Channel CH2 (Adapter Type = XI; System, Login, )
Collaboration Profile for Sender Service (e.g. File, IDOC, ) Sender Service XYZ (Any Business System/Process/Service) Outbound Interface OUT1 Comm.-Channel CH1
FAQs
Summary
Introduction
BW-XI Integration Technical Details
SAP AG 2004, SAP TechEd / XI201 / 25
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 enhanceXI 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 integrateBW 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.
FAQs
Summary
Introduction
BW-XI Integration Technical Details
SAP AG 2004, SAP TechEd / XI201 / 27
Summary
Existing integration scenarios
Positioning SAP BW / SAP XI
Steps to integrate SAP BW / SAP XI Future directions
SAP AG 2004, SAP TechEd / XI201 / 28
Further Information
Service Marketplace
Integration LandscapeBW-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 SourceFeature available since BW 30bFor 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 FrameworkFor 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 / 29
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 / 30
Q&A
Questions?
SAP AG 2004, SAP TechEd / XI201 / 31
Please complete your session evaluation.
Be courteous deposit your trash, and do not take the handouts for the following session.
Feedback
Thank You !
SAP AG 2004, SAP TechEd / XI201 / 32
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 / 33
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.
Copyright 2004 SAP AG. All Rights Reserved