B2B(EDI) Integration using

SAP Netweaver XI and

Seeburger AS2 Adapter
Sam Raju
SAP Netweaver RIG Americas
SAP Labs, LLC

Introduction
SAP Netweaver Providing infrastructure of B2B
Seeburger and B2B Adapters
EDI Content
Configuration
Message Monitoring and Security
Summary

Why Enabling Business-to-Business Processes?

B2B Integration Challenges
Complex Integration Requirements
Non-homogeneous infrastructures
Integration via open networks (Internet)
Diverse options for technical connectivity

Adapt to changing processes / business partners

Changing ability to dictate communication standards
Connect to all sizes of business partners
Time to connect new business partners is business critical

your
company

your
business
partners

Marketplace

Partner

SAP AG 2006, KHNC/ Sam Raju/ 071107/ 3

B2B Integration
Standards-based integration of inter-company processes

your
company

Marketplace

Partner

SAP AG 2006, KHNC/ Sam Raju/ 071107/ 4

your
business
partners

B2B Integration USING SAP NetWeaver

1. Reduce complexity

using ONE integration platform

2. Protect your Data

enabling secure connections

3. Connect Processes

standards-based and out-of-the-box

4. Pave the road

to an Enterprise SOA

SAP NetWeaver

SAP AG 2006, KHNC/ Sam Raju/ 071107/ 5

History of EDI
Originated in the 60s/70s
Several industries invented their own sets of standardized data
formats including TDCC - 1960
ANSI ASC X12 1979
Over 300 transactions sets in a single version

UN/EDIFACT 1985
Almost 200 transactions sets in a single version

Other EDI standards

HL7, ODETTE, TRADACOM,SWIFT etc.

SAP AG 2006, KHNC/ Sam Raju/ 071107/ 6

EDI and the Business Cycle

Buyer

Supplier
Request for Quote 840

Purchasing
&
Requisition

Quote 843
Purchase Order 850

Sales/Order
Management

PO Acknowledgement 855

Receiving

Shipment Notice 856

Shipping

Invoice 810

Accounts
Payable

Accounts
Receivable
Check and Invoice Info. 820

SAP AG 2006, KHNC/ Sam Raju/ 071107/ 7

Introduction
SAP Netweaver Providing infrastructure of B2B
Seeburger and B2B Adapters
EDI Content
Configuration
Message Monitoring and Security
Summary

Architecture supporting B2B Integration

SAPApplication
Any
Application

Industry Standard
Protocols
Integration Server
Integration Directory

Business
Partners

BPE

Collaboration Agreements
Collaboration Profiles

Integration
Engine

B2B
Messaging
Business
Partners

Integration Repository
Adapter Engine
Integration Scenarios

Mappings
Message Interfaces

SAP AG 2006, KHNC/ Sam Raju/ 071107/ 9

Adapter Framework
Messaging
Queuing
Security Handling

Security

Integration Processes

Partner
Connectivity Kit
Small Trading
Partners

XI Landscape and Messaging

Adapter
Framework
Adapter Engine in SAP J2EE
Adapter
Sender

Back
end

IB
Dir

Module Processor
Channel

Adapter
Receiver

Configuration
cache

Messaging

Tracing
Logging

Monitoring

Security

Administration

Scenario Configuration

IS

Configuration
cache

http
IDoc
BPE

XI Messages

Queue Receiver

Mapping

Determination

System Landscape Directory

RWB

Holds component description

including address data

Exchange Profile
Message, Component
monitoring et.al.
SAP AG 2006, KHNC/ Sam Raju/ 071107/ 10

Holds central connection descriptions

including user, passwords

Supporting Standards to Improve Processes

Industries involved in
Industry Standards Support
High Tech
Chemical
Agrichemical
Oil and Gas
Automotive
Aerospace and Defense
Consumer Products
Mill Products
Financial

GS1

Others

UN/CEFACT
SAP AG 2006, KHNC/ Sam Raju/ 071107/ 11

Adapter Partner Ecosystem for B2B Integration

SAP relies on an ecosystem of
partners to provide adapters for
other applications and certain
industry standards
WebMethods
SEEBURGER
iWay Software
More to come
Partner adapters are sold and
delivered through SAP

SAP System
3rd Party Appl.
File/DB/JMS
Marketplaces

SAP AG 2006, KHNC/ Sam Raju/ 071107/ 12

Support for the following

Application Vendors
Baan
Broadvision
JDE
Oracle
PeopleSoft
Siebel
Support for the following
Industry Standards
CIDX
EDI
EDI-INT
RosettaNet
UCCNet

Introduction
SAP Netweaver Providing infrastructure of B2B
Seeburger and B2B Adapters
EDI Content
Configuration
Message Monitoring and Security
Summary

Seeburger
Founded in 1986 in Germany
6,000+ Companies in 35 Countries rely on Seeburger Solutions
500 Employees Worldwide
Internally developed Integration Application
Leading B2B Gateway Provider
100% Trading Partner Integration

SAP AG 2006, KHNC/ Sam Raju/ 071107/ 14

SAP NetWeaver EDI Adapter: Architecture

mySAP CRM, SRM, SCM

SAP Industry Solution

Industry
networks

Non-SAP-System

Customer

Proxy, IDOC-Adapter, SQL-Adapter, JMS-Adapter, FILE Adapter, ....

SEEBURGER
SEEBURGER
Adapter
Adapter

Industry-specific
content:

Mappings as JAVA code

Message descriptions
Partner master data
SAP XI Workflows
Business Scenarios und
Processes
Rules

Exchange Infrastructure

SAP AG 2006, KHNC/ Sam Raju/ 071107/ 15

Integration Server
Supplier

Integration
Engine
Adapter
Adapter Engine
Engine
Adapter
Engine
Adapter
Framework
SEEBURGER
SEEBURGER
Adapter
Adapter

SEEBURGER EDI/ B2B

Technology suite
Conversion
Communication
Components

SEEBURGER
SEEBURGER
Adapter
Adapter

Logistics
Industry
Standard
Protocol

Bank

Security

Integration Repository
& Integration Directory

EDI/B2B
partner

EDI Adapter by SEEBURGER

Industry Adapter/ Business Packages
SAP XI workflows and business content
Modeled SAP XI workflows
Mapping templates for mapping industry-specific
content integrated in SAP NetWeaver (Integration
Repository)
Compreshensive set of generic, off-the-shelf
Industry Scenarios

EDI/B2B technology suite

EDI data transfer: VAN, EDINT AS 1 / AS2, X.400, OFTP

SAP NetWeaver
People Integration

Integration into SAP Netweaver via JCA

Configuration, Monitoring via SAP XI
Runtime: J2EE Engine SAP Web AS

SAP AG 2006, KHNC/ Sam Raju/ 071107/ 16

Customer

Information Integration
Process Integration

Vendor

SAP NetWeaver
EDI Adapter
by SEEBURGER
Logistics

EDI standard formats: EDIFACT, ANSI X.12, TRADACOM,

VDA, ODETTE, GALIA, AECMA, EANCOM, (SWIFT, Asian
formats depending on the adapter)
EDI components: analyze, view, split, compress,
encryption/e-signature

Industry
Networks

JCA
Integration
Broker

Business Process
Management

Application Platform
J2EE

ABAP

DB and
OS Abstraction
Abstraction
DB and
OS

Bank

EDI/
B2B
Partner

SEEBURGER EDI Adapter 997 Process

SAP AG 2006, KHNC/ Sam Raju/ 071107/ 17

Introduction
SAP Netweaver Providing infrastructure of B2B
Seeburger and B2B Adapters
EDI Content
Configuration
Message Monitoring and Security
Summary

Integration Repository Seeburger XI Content

Two main software components in
the repository
SEEBURGER_EDI_ADAPTER
SEEBURGER_GENERIC_EDI
The SEEBURGER_EDI_ADAPTER
contains the Adapter metadata
The SEEBURGER_GENERIC_EDI
contains the Standard content,
Mappings, Integration Scenarios, and
Communication channel templates

SAP AG 2006, KHNC/ Sam Raju/ 071107/ 19

External Definitions - XSDs behind the EDI standards

SAP AG 2006, KHNC/ Sam Raju/ 071107/ 20

EDI Standard as Integration scenario

SAP AG 2006, KHNC/ Sam Raju/ 071107/ 21

Mappings from the SAP standard to the EDI standard

SAP AG 2006, KHNC/ Sam Raju/ 071107/ 22

Adapter metadata

SAP AG 2006, KHNC/ Sam Raju/ 071107/ 23

Introduction
SAP Netweaver Providing infrastructure of B2B
Seeburger and B2B Adapters
EDI Content
Configuration
Message Monitoring and Security
Summary

Business Integration Converter (BIC) Adapter

Seeburgers BIC Adapter is an Any-to-Any format converter, used
to translate EDI data and Legacy data formats into XML and vice
versa
Supported EDI formats include:
XML
EDIFACT
ANSI X12
Aecma
Tradacom
CSV
VDA
SWIFT
Database
Inhouse (flatfile proprietary formats)

The converter is configured in the configuration part of the

Integration Builder

SAP AG 2006, KHNC/ Sam Raju/ 071107/ 25

Configuring BIC as Module

XML documents may need to be converted to and from other
formats, before sending, or receiving them to and from business
partners
The converter is configured on the module tab page in the module
processor of the communication channel
To configure the converter, the module must be entered in the
processing sequence (module sequence) and the parameters of the
module must be entered in the configuration table

SAP AG 2006, KHNC/ Sam Raju/ 071107/ 26

Module Parameters

DestSourceMsg / Target SourceMSG

MappingName
NewLine
DestDelimiter / Src Delimiter

SAP AG 2006, KHNC/ Sam Raju/ 071107/ 27

AS2 Adapter
Seeburgers AS2 Adapter can be configured in the configuration
part of the XIs Integration Builder
The Adapter is based on the Adapter Framework and is executed
by the SAP J2EE Adapter Engine
AS2 uses two different message types
Message payload
MDN

The Message Payload encapsulates an EDI file that can be

transmitted via HTTP protocal
MDN is to acknowledge the receipt of the payload message
MDN is optionally signed

SAP AG 2006, KHNC/ Sam Raju/ 071107/ 28

AS2 Adapter
Adapter Engine SAP J2EE

IS
RUNTIME

SAP AG 2006, KHNC/ Sam Raju/ 071107/ 29

AS2
Adapter

EDI
Partner

AS2 Adapter Configuration

SAP AG 2006, KHNC/ Sam Raju/ 071107/ 30

AS2 Adapter Configuration Contd..

SAP AG 2006, KHNC/ Sam Raju/ 071107/ 31

MDN Configuration

SAP AG 2006, KHNC/ Sam Raju/ 071107/ 32

Introduction
SAP Netweaver Providing infrastructure of B2B
Seeburger and B2B Adapters
EDI Content
Configuration
Message Monitoring and Security
Summary

Message Monitoring
Seeburger XI MessageIdMonitor provides some basic functions,
useful for monitoring Seeburger Adapters and correlating their
messages.
The Seeburger XI MessageIdMonitor provides the following
functions:
General view of any MessageIdStore files
Additional information on stores of special protocols
Additional information about errors
The MessageIdStore is used to correlate asynchronous messages
to their corresponding delivery notifications

SAP AG 2006, KHNC/ Sam Raju/ 071107/ 34

MessageIdStore Monitor

SAP AG 2006, KHNC/ Sam Raju/ 071107/ 35

MessageIdStore Monitor

SAP AG 2006, KHNC/ Sam Raju/ 071107/ 36

MessageIdStore Monitor Contd..

SAP AG 2006, KHNC/ Sam Raju/ 071107/ 37

Seeburger adapters security configurations

General adapter framework security settings apply for the Seeburger
adapters
Message security credentials are stored in the J2EE key store
Includes the public and private key certificates for the local as well as the
business partners
Adapter framework service user must be assigned the Keystore
administrator role for the particular view in the key storage
Applies to all views which are referenced in the sender and receiver
agreements for RosettaNet trading partners
Appropriate communication channels and agreements need to be
configured in the Integration Directory

SAP AG 2006, KHNC/ Sam Raju/ 071107/ 38

Demo

Demo

SAP AG 2006, KHNC/ Sam Raju/ 071107/ 39

Demo
The Order create process is initiated when a Buyer commits to buy
a product from Seller.
The Buyer sends an order create ANSI X12 850 message to the
seller.
Upon receipt of the message, the Seller sends a receipt
acknowledgement to the Buyer.

SAP AG 2006, KHNC/ Sam Raju/ 071107/ 40

Introduction
SAP Netweaver Providing infrastructure of B2B
Seeburger and B2B Adapters
EDI Content
Configuration
Message Monitoring and Security
Summary

Benefits of B2B with SAP NetWeaver XI

B2B capabilities of SAP XI
Only one solution for all integration requirements (B2B/EDI and A2A)
Same skills for all integration requirements
Centralized design, configuration, monitoring, alerting
Pre-configured solutions including mappings
Replacement of all isolated integration systems

Seeburger and B2B Adapters

SEEBURGER adapters run on the SAP NetWeaver platform and can be fully
integrated via JCA

Benefits
Low TCO because only one platform is required for B2B/EDI and A2A
Less maintenance effort
Less human resources needed
Rapid implementation using pre-delivered Integration Content (Business
Packages)
More budget for innovations
SAP AG 2006, KHNC/ Sam Raju/ 071107/ 42

Questions?

Q&A
SAP AG 2006, KHNC/ Sam Raju/ 071107/ 43

Copyright 2007 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.
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.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose
without the express prior written permission of SAP AG.
This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended
strategies, developments, and functionalities of the SAP product and is not intended to be binding upon SAP to any particular course of business, product
strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.
SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics,
links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited
to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of
these materials. This limitation shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of
hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web
pages.

SAP AG 2006, KHNC/ Sam Raju/ 071107/ 44