Real World Scenarios of SAP XI

7/28/2019 Real World Scenarios of SAP XI

http://slidepdf.com/reader/full/real-world-scenarios-of-sap-xi 1/36

Real World Scenarios of SAP XI

George YuSAP Labs, LLC



© SAP AG 2004, Scenarios, George Yu / 2

Agenda

SAP Integration

1. Backend System Connectivity

2. SAP ICH

Non-SAP Integration

3. Integration of 3rd Party & SAP Systems

4. Integration With a Marketplace

5. SEEBURGER EDI Adapter

SAP XI Funct ionality6. Web Services With SAP XI

7. Integration of Mapping Tools

ccBPM Functionality

8. Message Split

9. Message Synchronization

10. Financial Data Verification

High Volume11. 1.44 Mill ion Messages per Day




Use Case 1: Backend System Connectivity

Descriptions:

SAP XI is intended as a central hub for various applications and back-ends infour scenarios:

1. Transport R/2 data (e.g. Invoice, Order, ASN) over to SAP BW

2. Transport R/2 data via PDF format over to SAP cFolders application and also record

them in SAP BW

3. Transport SAP CRM user roles over to SAP cFolders and SAP BW

4. Transport R/2 data over to SAP CRM via IDoc

Benefits:

Join or extend SAP XI to

other subsidiaries and

groups containing additional

back-ends

Central point of administration

Central reporting through

SAP BW

Objective:

Implement one common

sales platform for a

company


http://slidepdf.com/reader/full/real-world-scenarios-of-sap-xi 4/36© SAP AG 2004, Scenarios, George Yu / 4

Use Case 1: Backend System Connectivity (2)

File Adapter

Integration

Repository

IntegrationDirectory

Integration

Repository

Integration

Directory

Integration

Server

Integration

Engine

SAP CRM*

SAP BW*

SAP cFolders*

SAP

R/2 Backend

Local

Integration

Engine

Proxy

Proxy Runtime

* based on SAP Web Application Server 6.20+



Use Case 1: Backend System Connectivity (3)

* BWBackend R/2

Invoice, Order,

Change Order, Opportunity

AdvanceShipmentNot ice

TradingPartnerOrgInfo

Report s torage

Author ization structure

* cFolders & BWBackend R/2

PDF

HeaderInfo

PDF storage

Usergroup assignment

* BW & cFolders* CRM

User

User details

User assignment to

Usergroups and

Authorization st ructure

* CRMBackend R/2

Product Info

Company Info

Product Info

Company Info

IntegrationServer RFC

Java VM

RFC

Java VM

RFC

Java VM

IDoc

Interf.IDOC

ABAP

Inbound

Proxy

ABAP

Inbound

Proxy

ABAP

Inbound

Proxy

ABAP

Outbound

Proxy

Integration

Engine

* based on SAP Web Application Server 6.20+



Use Case 2: SAP Inventory Collaboration Hub 4.0 (1)

Descriptions: Use SAP XI as a gateway to communicate with other business

systems

Act as a component of SAP SCM 4.0

Benefits:

Leverage exist ing

integration solution of SAP

XI Adopt new internet standard

such as XML

Objective:

Offers the supplier an

adaptive approach to the

collaborative business

process



Integration

Server

SAP Web AS 6.20

Integration Enginew/Integration Logic

SAP

XI

Integration Builder

Use Case 2: SAP Inventory Collaboration Hub 4.0 (2)

Integration

Directory

ProxyGeneration

of WSDL

Interface

DescriptionIntegration

Repository

ICH

Application

Logic

Proxy

Proxy

Framework

Integration Engine

as Sender/Receiver

SAP Web AS 6.20

XML

XML

SAP

Application

SAP

Application

IDoc

3rd Party

ApplicationXML



Material Master -> Product

Plant -> Customer Location

Vendor Master -> Supplier Location

DELFOR

Product Activity N.PROACT

DELVRYDispatched Delivery N.

DELVRYReceived Delivery N.

Email :

Notification

(Alerts)

Delivery Schedule N.

C

I

F

SAP R/3 SCM 4.0

C

I

F

IDocs XML

Demand

Stock

Master

Data

Releases

ASN

Alerts

I n t e g r a t i o n

E n g i n e

Info Rec/Contract/Sched.Agreement - > Transportation Lane

APO

BA

PI’s

Business Partner (BP) settingsmaintained via: BAPI (external) or SAPGUI

Integration of R/3 MM and ICH via SAP XI

SAP

XI



Agenda

SAP Integration


2. SAP ICH

Non-SAP Integration

3. Integration of 3rd Party & SAP Systems4. Integration With a Marketplace


SAP XI Funct ionality6. Web Services With SAP XI


ccBPM Functionality

8. Message Split






Use Case 3: Integration of 3rd Party & SAP Systems (1)

Descriptions:

Transfer Product Data from 3rd Party System over to Transfer Queue

Update Data from Transfer Queue via JDBC Adapter to SAP XI

Correct value mapping and routes data within XI before PLM system

Update other SAP systems from PLM system

Benefits:

Reliable product datadistr ibution to ERP system

from 3rd Party system

One common exchange

platform across company One single system instead of

multiple systems for

monitoring

Objective:

Integrate a 3rd party system

to a SAP PLM system



Use Case 3: Integration of 3rd Party & SAP Systems (2)

SAP XI

3rd Party System

T_Master

_Data

Transfer Queue

Java VM

RFC

Java VM

JDBCAuftragNR ID Status Object ID1234

1235

1356

22 INIT

22 HOLD

23 READ

T_Doc

_DAT

T_Master

_DOC BAPI

PDR PLM Asyn-Sync Bridge

Inbound ProxyAsynchronous

Outbound ProxySynchronous

Outbound ProxyAsynchronous

Status

Update

Routing and

Value Mapping

XSLT Mapping

Integration

Engine

C 4 (1)




Use Case 4: Integration with a Marketplace (1)

Objective:

Receive content updates

from global marketplace

– TradeRanger

Benefits:

Harmonize master data

(products and partners)

across subsidiariesaround the world

Descriptions:

Use XI to connect up to 60 subsidiaries to SAP MarketSet Connect subsidiary's Content Catalog to Global XI

Connect Global XI to MarketSet (using MarketSet Adapter)

Connect Customer’s MarketPlace (i.e. MarketSet) to TradeRanger

U C 4 I t ti ith M k t l (2)




Use Case 4: Integration with a Marketplace (2)

SAP XI

SMQ

Up to 60 local subsidiaries

Customer’s Global

Marketplace

HTTPS

…

Marketset

SonicMQ

Content

Catalog

Content

CatalogContent

Catalog

Content

Catalog

Content

Catalog

U C 5 SEEBURGER EDI Ad t




Use Case 5: SEEBURGER EDI Adapter

Objectives:

Provide an EDI solution

on internet rather than

VAN

Leverage SAP XI’s

Adapter Framework

Benefits:

Minimize impact to EDI

partners Introduce modern

integration solution to

prepare for the future

Descriptions:

Use SEEBURGER EDI Adapter to convert XML message to EDI format

Transfer EDI message via HTTP or AS2 protocol to replace expensive

Value Added Network (VAN)

Use many industry specific mappings and protocols off the shelf

Make SAP XI an EDI Hub

U C 5 SEEBURGER EDI Ad t (2)




Use Case 5: SEEBURGER EDI Adapter (2)

Back-endSystems

Partner

Systems

SAP XISEEBURGER

EDI Adapter

Agenda




Agenda

SAP Integration


2. SAP ICH

Non-SAP Integration



SAP XI Funct ionality

6. Web Services With SAP XI


ccBPM Functionality

8. Message Split




Value added Web Services through XI




Value-added Web Services through XI

SAP Web AS ≥ 6.40

Integration Server

SAP

System

SOAP

Mapping

Routing

Business Processes

SOAP

XI Protocol

or

SOAP

3rd Party Appl icat ion Adapter

Adapter IDocsRFCs

Proxy

Proxy Runtime

Local

Integration Engine

Web Services

Framework

‘Basic’ Web Service

‘Enhanced’ Web Service

Web ServiceClient

(SAP/non-SAP)

Web Service

Client

(SAP/non-SAP)

Use Case 6: Web Services with SAP XI




Use Case 6: Web Services with SAP XI

Descriptions:

Return Available To Promise (ATP) request

1. Send IDoc from SAP APO to SAP XI

2. Connect SAP XI to INTERNATIONAL delivering

plants (e.g. Sweden, Korea, Germany)

3. Connect to Microsoft platforms over HTTP using

SOAP Adapter

Benefits:

Leverage the value of the

existing applications by

integrating them

Align heterogeneous

systems from frequent

acquisitions to show a

unified company to

customers and resellers

Objectives:

Test performance and

response time for the Stock

Balance Request

Establish backend

connectivity

Use Case 6: Web Services with SAP XI (2)




Use Case 6: Web Services with SAP XI (2)

SAP XI

Business Logic Sweden

Korea

Germany

RFC

Msg 1

Msg 1 – IDOC over RFCMsg 2 – SOAP over http

Msg 3 – IDOC over RFC

Msg 4 – SOAP over http

Msg 3

Msg 2

Msg 4

HIS = Microsoft Host Integration Server

SAP

R/3 4.6C

SAP

APO 2.0

SAP

R/3 4.6C(Unix)

MOPS

(IBS –

AS/400)

SPIS

(S/390)

HIS

WS

SOAP

SOAP

IDOCIDOC

Message Broker

Use Case 7: Integration of Mapping Tool




Use Case 7: Integration of Mapping Tool

Benefits:

Leverage existing 3rd party

tools

Keep existing messages

Track and trade messageflows with automatic

guaranteed deliveryDescriptions:

SAP XI fits into an existing simple ALE to ALE system landscape

Send EDI message from a non-SAP application to SAP XI

Perform routing, XSLT mapping and address resolution within XI

Perform mapping and transportation within existing Mercator

Deliver IDOC to SAP System by XI

Objective:

Incorporate existing

Mercator mappings in SAP

XI

Use Case 7: Integration of Mapping Tool (2)





SAP XI XML

ExistingExisting

InfrastructureInfrastructure

Mercator MappingEngine

ALE

ALE

EDI

IDOC






Scenario Details: SAP XIÅÆ Mercator Link

Integration Server

SAP

System

IDocs

Non-SAPSystem

MappingRouting

IDoc

Adapter

Mercator

Mapping

JMS

Adapter

Java

PropertiesMercator

Web Service

J2EE

Web Service Call

XML with IDOC Payload

IDOC Payload within XML

Agenda




Agenda

SAP Integration


2. SAP ICH

Non-SAP Integration






ccBPM Functionality

8. Message Split




Use Case 8: Message SplitccBPM Non PO Invoice in XI 3 0




ccBPM – Non-PO Invoice in XI 3.0

Benefits:

Remove slow Gateway

Program

Only spli t invoices once

Eliminate custom developed

code

Descriptions:

Use ccBPM in an Integration Scenario

Receive Invoice Packets from MQ Series via JMS adapter

Use ccBPM to do message spl itt ing, data mapping, and organize IDOC by

company code

Based on Receiver Determination and message type, send messages toits destinations via various adapters

Objective:

Take advantage of ccBPM to

simpli fy the message

processing

Use Case 8: Message SplitNon PO Invoice in XI 2 0




Non-PO Invoice in XI 2.0

SAP XI 2.0

JDBC

Adapter

System

A

Mapping

Invoice

Packet

Gateway

Program

(Message Split)

Single

InvoiceMapping

Mapping

IDoc

Adapter

File

Adapter

System

B

System

C

R e c ei v er

D e t er mi n a t i o

n

MQSJMS

Adapter Com

Code

Use Case 8: Message SplitccBPM Non PO Invoice in XI 3 0




ccBPM – Non-PO Invoice in XI 3.0

SAP XI 3.0JDBC

Adapter

System

A

Invoice

Packet

ccBPM

Data Mapping and

Invoice Spli t

(In case of IDOC,

Organize IDOC by

cost center)

IDoc

Adapter

File Adapter

System

B

SystemC

R e c ei v er

D

e t er mi n a t i on

MQS JMS

Adapter

Com

Code

Use Case 9: Message Synchronization




g y

Benefits:

Process logic resides in

middleware

Leverage exist ing

applications


code

Descriptions:

Use ccBPM to control data synchronization Receive data from SAP R/3 via IDoc adapter

Use ccBPM to verify if the data is used for update an existing record or

creating a new record

Objective:

Synchronize data between

SAP R/3 and a 3rd party

system

Use Case 9: Message Synchronization




SAP XI 3.0

Business Process Management

SEND

to third-party lookup: does record exist?

WAIT for

response

Update and

wait for acknowl.

Insert and

wait for acknowl.exist?

SEND

To GMD

WAIT for

acknowl.

response: yes/no

confirm

no

yes

Routing

to BPM

SAP

R/3

3rd Party

System

IDoc

Adapter

Use Case 10: Financial Data Verification (1)




Benefits:

Incorporate Java program

for data mapping

Leverage exist ing

applications


code

Descriptions:

Use ccBPM to control data verification and mappings Receive data from a treasurer system via JMS adapter

Check the data uniqueness and store in an Oracle DB

Use Java programs to verify digital signature and XSD validation

Objective:

Verify financial data during

data transition from one

system to other systems

Use Case 10: Financial Data Verification (2)




SAP XI 3.0

Oracle

DBPopulate SRN in

DB

Receive

XML

Check SRN

Uniqueness

Verify Digital

Signature

XSD Validation

Mapping to IDoc

Send to R/3

Send Status to

MQ

Treasurer

SystemJMS

Adapter

SAP

R/3

IDoc

Adapter

MQ SeriesJMS

Adapter

Agenda




SAP Integration


2. SAP ICH

Non-SAP Integration






ccBPM Functionality

8. Message Split




Use Case 11: 1.44 Million Messages per Day




Benefits:

Util ize both IDoc adapter and

ABAP Proxy to communicate

between SAP XI and R/3

Make SAP XI a central hubfor integration to reduce

TCODescriptions:

Use SAP XI’s flexibility to connect SAP and non-SAP systems Process 50,000 to 60,000 messages per hour, equivalent to 1,440,000

messages per day

Objective:

Exchange high volume data

between an IBM mainframe

system and an SAP R/3

system

Use Case 11: High Volume




SAP XI

IDoc

Adapter MQS JMS

Adapter SAP

R/3

IBM

Mainframe

System

ABAP Proxy

Benefits of SAP XI




Develop and maintain interfaces using a standard tool

Centralize interface and mapping data to reuse knowledge for future scenarios

Replace 100’s to 1000’s l ines of customer code for splitting androuting messages

Remove tight coupling of systems

Change business processes f lexibly and with high productivity

Enable integration from SAP to non-SAP systems via standardmeans

Use SAP XI to develop new SAP applications

Use ccBPM to intelligently orchestrate message flows amongintegrated systems

Questions?




Q& A

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 expresspermission 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 othersoftware 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®, Informixand Informix®Dynamic Server TM 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.

J AVA®is a registered trademark of Sun Microsystems, Inc.

J AVASCRIPT® 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, R/3, mySAP, mySAP.com, xApps, xApp and other SAP products and services mentioned herein as well astheir respective logos are trademarks or registered trademarks of SAP AG in Germany and in several othercountries all over the world. All other product and service names mentioned are the trademarks of their respectivecompanies.

Real World Scenarios of SAP XI

Documents