b2b(edi) integration using process integration capabilities of sap netweaver and seeburger as2...
TRANSCRIPT
Seeburger and B2B Adapters
Why Enabling Business-to-Business Processes?
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 cr itical
B2B Integration Challenges
Standards-based integration of inter-company processes
B2B Integration
B2B Integration USING SAP NetWeaver
SAP NetWeaver
3. Connect Processes standards-based and out-of-the-box
4. Pave the road to an Enterprise SOA
History of EDI
Several industries invented their own sets of standardized data
formats including TDCC - 1960
ANSI ASC X12 – 1979
UN/EDIFACT – 1985
Other EDI standards
Buyer Supplier Request for Quote 840
EDI and the Business Cycle
Quote 843
Purchasing
Seeburger and B2B Adapters
Architecture supporting B2B Integration
i t y
Configuration
including address data
including user, passwords
Message, Component monitoring et.al.
Supporting Standards to Improve Processes
Industries involved in
Industry Standards Support
Adapter Partner Ecosystem for B2B Integration
SAP relies on an ecosystem of
partners to prov ide adapters for
other applications and certain
delivered through SAP
Seeburger and B2B Adapters
Seeburger
6,000+ Companies in 35 Countr ies rely on Seeburger Solutions
500 Employees Worldw ide
Internally developed Integration Application
Leading B2B Gateway Provider
100% Trading Partner Integration
SAP NetWeaver EDI Adapter: Architecture
Industry
Standard
Protocol
Integration Server Integration Repository
• Message descripti ons
• Partner master data
• Communication
• Components
S e c u r
i t y
Industry Adapter/ Business Packages
Modeled SAP XI workflows
content integrated in SAP NetWeaver (Integration
Repository)
Industry Scenarios
EDI data transfer: VAN, EDINT AS 1 / AS2, X.400, OFTP
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
SEEBURGER EDI Adapter – 997 Process
Seeburger and B2B Adapters
Integration Repository – Seeburger XI Content
Two main software components in
the repository
External Definitions - XSDs behind the EDI standards
EDI Standard as Integration scenario
Mappings from the SAP standard to the EDI standard
Adapter metadata
Seeburger and B2B Adapters
Business Integration Converter (BIC) Adapter
Seeburger’s BIC Adapter is an Any-to-Any format converter, used to translate EDI data and Legacy data formats into XML and v ice versa
Supported EDI formats include: XML
EDIFACT
Inhouse (flatfile propr ietary formats)
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 conf iguration table
Module Parameters
AS2 Adapter
Seeburger’s AS2 Adapter can be configured in the configuration
part of the XI’s 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
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
AS2 Adapter
AS2 Adapter Configuration
AS2 Adapter Configuration Contd..
MDN Configuration
Seeburger and B2B Adapters
Message Monitoring
useful for monitoring Seeburger Adapters and correlating their
messages.
functions:
Additional information on stores of special protocols
Additional information about errors
to their corresponding delivery notifications
MessageIdStore Monitor
MessageIdStore Monitor
MessageIdStore Monitor Contd..
Seeburger adapters – security configurations
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
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 communicat ion channels and agreements need to be
conf igured in the Integration Directory
Demo
Demo
Demo
The Order create process is init iated when a Buyer commits to buy
a product f rom 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.
Seeburger and B2B Adapters
Benefits of B2B with SAP NetWeaver XI
B2B capabil ities of SAP XI
Only one solution for all integration requirements (B2B/EDI and A2A)
Same skills for all integration requirements
Centralized design, conf iguration, monitoring, alerting
Pre-configured solutions including mappings
Benefits
Low TCO because only one platform is required for B2B/EDI and A2A
Less maintenance effort
Packages)
More budget for innovations
Seeburger and B2B Adapters
SEEBURGER adapters run on the SAP NetWeaver platform and can be ful ly
integrated via JCA
Q
Questions?
SAP AG 2006, KHNC/ Sam Raju/ 071107/ 44
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 t rademarks 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.
Copyright 2007 SAP AG. All Rights Reserved
Why Enabling Business-to-Business Processes?
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 cr itical
B2B Integration Challenges
Standards-based integration of inter-company processes
B2B Integration
B2B Integration USING SAP NetWeaver
SAP NetWeaver
3. Connect Processes standards-based and out-of-the-box
4. Pave the road to an Enterprise SOA
History of EDI
Several industries invented their own sets of standardized data
formats including TDCC - 1960
ANSI ASC X12 – 1979
UN/EDIFACT – 1985
Other EDI standards
Buyer Supplier Request for Quote 840
EDI and the Business Cycle
Quote 843
Purchasing
Seeburger and B2B Adapters
Architecture supporting B2B Integration
i t y
Configuration
including address data
including user, passwords
Message, Component monitoring et.al.
Supporting Standards to Improve Processes
Industries involved in
Industry Standards Support
Adapter Partner Ecosystem for B2B Integration
SAP relies on an ecosystem of
partners to prov ide adapters for
other applications and certain
delivered through SAP
Seeburger and B2B Adapters
Seeburger
6,000+ Companies in 35 Countr ies rely on Seeburger Solutions
500 Employees Worldw ide
Internally developed Integration Application
Leading B2B Gateway Provider
100% Trading Partner Integration
SAP NetWeaver EDI Adapter: Architecture
Industry
Standard
Protocol
Integration Server Integration Repository
• Message descripti ons
• Partner master data
• Communication
• Components
S e c u r
i t y
Industry Adapter/ Business Packages
Modeled SAP XI workflows
content integrated in SAP NetWeaver (Integration
Repository)
Industry Scenarios
EDI data transfer: VAN, EDINT AS 1 / AS2, X.400, OFTP
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
SEEBURGER EDI Adapter – 997 Process
Seeburger and B2B Adapters
Integration Repository – Seeburger XI Content
Two main software components in
the repository
External Definitions - XSDs behind the EDI standards
EDI Standard as Integration scenario
Mappings from the SAP standard to the EDI standard
Adapter metadata
Seeburger and B2B Adapters
Business Integration Converter (BIC) Adapter
Seeburger’s BIC Adapter is an Any-to-Any format converter, used to translate EDI data and Legacy data formats into XML and v ice versa
Supported EDI formats include: XML
EDIFACT
Inhouse (flatfile propr ietary formats)
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 conf iguration table
Module Parameters
AS2 Adapter
Seeburger’s AS2 Adapter can be configured in the configuration
part of the XI’s 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
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
AS2 Adapter
AS2 Adapter Configuration
AS2 Adapter Configuration Contd..
MDN Configuration
Seeburger and B2B Adapters
Message Monitoring
useful for monitoring Seeburger Adapters and correlating their
messages.
functions:
Additional information on stores of special protocols
Additional information about errors
to their corresponding delivery notifications
MessageIdStore Monitor
MessageIdStore Monitor
MessageIdStore Monitor Contd..
Seeburger adapters – security configurations
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
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 communicat ion channels and agreements need to be
conf igured in the Integration Directory
Demo
Demo
Demo
The Order create process is init iated when a Buyer commits to buy
a product f rom 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.
Seeburger and B2B Adapters
Benefits of B2B with SAP NetWeaver XI
B2B capabil ities of SAP XI
Only one solution for all integration requirements (B2B/EDI and A2A)
Same skills for all integration requirements
Centralized design, conf iguration, monitoring, alerting
Pre-configured solutions including mappings
Benefits
Low TCO because only one platform is required for B2B/EDI and A2A
Less maintenance effort
Packages)
More budget for innovations
Seeburger and B2B Adapters
SEEBURGER adapters run on the SAP NetWeaver platform and can be ful ly
integrated via JCA
Q
Questions?
SAP AG 2006, KHNC/ Sam Raju/ 071107/ 44
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 t rademarks 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.
Copyright 2007 SAP AG. All Rights Reserved