B2B and Industry Standards Support

SAP Exchange Infrastructure

B2B and Industry Standards Support SAP AG

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

� SAP AG 2003, B2B and Industry Standards Support, Sindhu Gangadharan / 2


Agenda

B2B in XI 3.0 – Features

Industry Standards Support in XI 3.0

Focus Vertical Industry High Tech - RosettaNet

Marketplace Connectivity


B2B And Industry Standards Support – Challenges

OtherIntegration

Solution

Secu

rity

Industry Standard Protocols

• Different solutions for A2A and B2B scenarios

• Custom solutions to connect to Industry Standards compliant business partners

• Substantial effort to develop and support mappings to standard interfaces

• Small business partners have to invest heavily to be industry standards compliant

• Different solutions used to connect to Marketplaces

• Use of proprietary technologies for security handling in B2B scenarios

Business Partners3rd Party

Application SAPApplicationWorkflow

ToolHard-codedIntegration

MainframeApplication

MarketplacesSAP

Application B2B Tool

B2B Tool BusinessPartner

ApplicationIndustry standardAdapter

EAITool


B2B In XI 3.0

B2BMessaging

Secu

rit

PartnerConnectivity Kit

BusinessPartners


SAPApplication

BusinessPartners

AnyApplication

SAP XISmall Trading

Partners

yMarketplaces


Secu

rit


BusinessPartners

IntegrationEngine

Adapter Engine

Adapter FrameworkMessagingQueuing

Security Handling

SAPApplication

B2B In XI 3.0

AnyApplication


Integration ServerIntegration Directory BPE

Collaboration AgreementsB2BMessagingCollaboration Profiles

BusinessPartners

Integration Repository

yMessage Interfaces

Business ScenariosBusiness Processes

MappingsSmall Trading

Partners


B2B In XI 3.0

� Collaboration Partner Data in the Integration Directory

Manages technical characteristics of partners to facilitate document exchange such as� Party identification� Message formats and versions supported� Security requirements� Collaboration Agreements

�Partner Connectivity Kit � For small business partners� Enable business partners of XI customers to conduct XML document

exchange with XI� Small scale easy to use client

� B2B security (Signature/Encryption)

� Industry Standards Support

� XI as marketplace messaging infrastructure



Agenda






SAP XI Provides Industry Standards Technology

SAPApplication

Secu

rit


BusinessPartners

Any Application


Adapter Engine

Integration Server

Integration Repository & Integration Directory

BPE

IntegrationEngine

B2BMessaging

BusinessPartners

ySmall Trading

Partners


Industry Standards Support

SAP CRM

SAP Industry SolutionIDOC/Proxy

Adapter Engine

Adapter Framework Industry StandardProtocol

Integration Server

BPE

IntegrationEngineCollaboration Agreements

Integration DirectoryBusiness Partner

Collaboration Profiles


Message Interfaces

Business ScenariosBusiness Processes

Application�Standard Mappings

Business Doc Schema


SAP® Business Packages for Industry Standards

Provide Solution Kits for specific industries

Deliver mappings for RosettaNet, CIDX, others to follow

Application adoption� Enhance business applications like mySAP CRM or mySAP SCM to

support SAP® Business Packages for high priority processes

Mapping� Including message sets for the industries according to their priority� Support mappings: versions, upgrade, maintenance

Process Integration� Message protocol implementation (such as RNIF 2.0 for RosettaNet and

RNIF 1.1 for CIDX)� Provision of Collaboration Agreements� Business Process Management support



Agenda






What is RosettaNet?

A Consortium of more than 500 companies founded in 1998

� Create & Implement internet based e-biz standards in High Tech Industry

Boards: Information Technology (IT), Electronic Components (EC),Semiconductor Manufacturing (SM), Software Providers (SP), Telecommunication (newly formed)

Global Standard: � Americas, Europe, Japan, Korea, Singapore, Taiwan, Malaysia,

Philippines

Who are RosettaNet members?� Most of the top High-Tech companies around the world

� Sony, TSMC, UMC, SMIC� Intel, Cisco, TI, HP, Dell, Applied Materials, Motorola, Molex� Nokia, STM� SAP, Microsoft, IBM, Oracle, i2, webMethods, TIBCO


Why SAP Supports RosettaNet

RosettaNet = High Tech Industry Speak

B2B communication is essential for High Tech collaboration

High Tech companies are demanding their partners to comply� Evaluate their partners thru the adoption of RosettaNet standards

Customers demand for RosettaNet support� Want SAP to deliver a solution to lower the RosettaNet

implementation cost

RosettaNet is the proven e-standard� Other standards such as CIDX and PIDX are leveraging the

foundation components


Main components of RosettaNet standards…

PIPs (Partner Interface Processes)� Public processes between business partners, linking each private process

into a business transaction

� based on simple, transactional exchange of business documents(NOT a business process with complex control flow !)� Request-confirm (two-action)� One-way notification (single-action)

� comprises business document definition� DTD� Message Guideline (= possibly complex validation rules)

� based on Business Transaction Dialog (RNIF 2.0 higher layers)� defines additional business signal and exception handling for “atomic

outcome” of business document exchange

� defines business activity performance controls � Timeout, Retry (transaction level, not transport level !)� Security (signature, encryption, non-repudation of receipt / of origin and

content)


Main components of RosettaNet Standards

RosettaNet Implementation Framework (RNIF)� Protocol specification standardizing the packaging, routing and transport of all

PIP messages and business signals

Meta-Level Framework: � no real class library� protocol specification

Transport� http, https, smtp, …

Packaging� S/MIME

Security� S/MIME

Message Choreography for Business Transaction Dialog� Business Signals

� positive ACKs� negative ACKs

RNIF 1.1 and RNIF 2.0 are significantly different


RosettaNet support for SAP applications – What isinvolved?

SCM CRM

PurchaseOrderRequest

PurchaseOrderConfirm

AdvanceShipmentNotification

InvoiceNotification

SAP XI

RNIF AdapterB

2B e

nabl

ing

Com

pany

A

Bus

ines

sP

artn

erX

PIP

PIP

PIP

CollaborativeProcess

Application drives overall collaborative process

XI – B2B enabling, RNIF 2.0adapter

Collaboration knowledge for PIPs

Goal – Deliver an end to end RosettaNet solution for ourcustomers


RosettaNet support for SAP applications – What is involved?

� Application enhancements to better enable RosettaNet

� Dedicated PIP mappings delivered with XI

� RNIF 2.0 native with XI 3.0

� SAP is the only soln. Provider to offer end-to-end RosettaNet solutions

ApplicationApplicationBusiness Logic

Interface Interface Interface

RosettaNet Protocol (e.g. RNIF)RosettaNet Protocol (e.g. RNIF)

Map Map Map

RosettaNet PIPs


Business Logic

Integration Logic

IndustryStandard processes


RosettaNet Support within XI


Integration Server

Business Process Engine

Integration Engine

Adapter Engine

MessagingQueuing

Security Handling

ResourceAdapter

RNIF 2.0ResourceAdapter

SAPIndustry Solution

(High Tech)

IDoc/Proxy

3rd PartyApplication

Message Interfaces

Business Processes

Mappings

Business Scenarios

RNIF toBusinessPartner

Integration DirectoryRosettaNet

PIP

Application �

RosettaNet PIPs

BusinessDocumentSchema

RosettaNetBusiness Partner

Collaboration Agreements

Collaboration Profiles


RosettaNet support in XI – Different phases

•PIP’s as Business Scenario in the Integration Repository

•Import of DTDs into the Integration Repository

•Mappings from standard interfaces to application interfaces

Collaboration Agreements in the Integration Directory

RNIF 2.0 adapter in the adapter framework

�Identify PIP – party and service configuration

�Security handling based on party

�Endpoint configuration

�Policy overrides

�RNIF protocol header overrides

�Business Activity Performance controls

Design Time

Config Time

Run Time


Integration Repository Layout for Industry Standards

� Separate SWCVs for Industry Standards Content e.g. RosettaNet, PIDX, CIDX, UCCnet

� Industry Standards integration content or mappings to backend applications in a separate SWCV

� Both components along with the technical adapter will constitute a single product called SAP Business Package for RosettaNet in the case of RosettaNet


RosettaNet PIP as Business Scenario in the Integration Repository

Advantages

PIP metadata can be shipped

Provides visibility of the B2B scenario

Helps in defining mappings

Future - composite scenarios for collaborative processes


Sample PIP schema used by the RNIF Adapter...

<AdapterTypeMetadata>

<outbound>

<TransportProtocol>

<Name>HTTP</Name>

<ChannelAttributes><attributeReference>addressingMode</attributeReference>

</ChannelAttributes>

<SecurityAttributes><attributeReference>Username</attributeReference>

</SecurityAttributes>

</TransportProtocol>

<MessageProtocol>

<Name>RNIF</Name>

<ChannelAttributes/>

<SecurityAttributes><CertificateReference>DigitalSignatureCertificate</CertificateReference>

</SecurityAttributes>

</MessageProtocol>

<GlobalChannelAttributes>

<attributeReference>messageStandard</attributeReference>

<attributeReference>timeToPerform</attributeReference>

<EditCondition>

<AttributeName>PIP_DIALOG_TYPE</AttributeName>

<AttributeValue>2-Action</AttributeValue>

</EditCondition>

<EditCondition>

<AttributeName>INITIATING_PARTY</AttributeName>

<AttributeValue>XI</AttributeValue>

<EditCondition>

<attributeReference>GlobalDigestAlgorithm</attributeReference>

</GlobalChannelAttributes>

</outbound>

Constraint: User could edit the field timeToPerform based on certain conditions

Transport protocols could be N in number. Eg. HTTP 1.0, HTTP 1., HTTPS 2.0 , SMTP 1.0 The attributes that are specific to a given Transport Protocol should be defined in this block.

Message protocols could be N in number. Eg RNIF 2.0, RNIF 1.1. The attributes that are specific to a given Message Protocol will be defined in this block.

Contains a set of attributes that are common / wouldn’t fit into to the above defined protocol blocks.


Sample RNIF Adapter Configuration Screen in the Integration Directory


RNIF adapter – key features

� Pack and unpack RosettaNet messages� Structural verification of the message

headers � Handling of security and digital

certificates� Uses the Collaboration Partner

Agreements to manage RosettaNet PIP exchanges

� Execution of pre- built mappings between SAP interfaces & RosettaNetPIP payload

� RosettaNet defined error handling procedure (PIP0A1 Notification of Failure)

� Message monitoring & auditing� Notification of Exceptions to backend

applications

IntegrationServer

RNIF adapterAdapter Engine

AdapterFramework

Industry Standards Content IntegrationRepository


RosettaNet Support within XI - Overall Architecture

IntegrationRepository

Business Scenarios

Interfaces,Message Types,

Imported MessageTypes

Mappings

Business Processses

IntegrationDirectory

Business Scenarios

Interface DeterminationRules

CollaborationAgreements / Adapter

Configuration

Receiver DeterminationRules

Receiver Det.,Interface Det. Mapping

Protocol/AdapterDeterm.


Messaging EnginePERSIST

RR

S/MIME

RNIF choreography mgr

Protocol Mapping

XI SPI

R

RosettaN

et PIP XYZ

R

RNet message

BASIS/Security

Services:Message, CPA, Timer,Monitorin+Alerting, Security Audit

KeyStore

SAP Application

R

Standard RosettaNetPIP as Business ScenarioBusiness Document Schema (DTD)Meta-Data (Action/Role, BT Dialog,performance controls, ...)

Std. IntegrationMappingBroker Process Template

Central Monitoring Server

Integration Engine Adapter Framework

CCMS

PMI

Runtime Workbench

RNIF SPI

MS framework

R

Metadata Svc

TransactionDialog Hdler

Msg Validation

PIP as scenario

Mapping + Integr.

Scenario

PartnerAgreements

&Partner Profiles

PIPs dialoghandling

Transport+Routing+

PackagingXI Msg(N)ACK

Conversation Context

Broker Process

Private Process

Monitoring + Alerting

B2B gatewaytest with partner


Roadmap for Industry Standards Support @ SAP

• Provide RNet adapter (RNIF2.0) in XI 3.0• Provide UCCnet adapter• Provide Collaboration Partner Agreement• Provide key mappings• Provide Business Process Management

• Provide CIDX adapter (based on RNIF1.1)

• Provide PIDX adapter (based on RNIF2.0)

• Provide application enhancements

• Provide key mappings• Enhance Collaboration

Partner Agreement and BPM

TIME/Solution

Cap

abili

ty /

Valu

e

2004(Phase 2)

2003(Phase 1)

2005(Phase 3)

• Provide other adapters (such as ebXML)

• Provide additional app. enhancements

• Enhance Business Process Management

•Single place to manage Collaboration Partner Profile)•Single place to manage Collaboration Partner Agreement full compliance with RNIF 2.0

• Modeling and monitoring of business processes across value chain • Provide connectivity to

Collaboration Partners via RosettaNet• Accelerate RosettaNet implementation in High Tech Industry• Reduce standard implementation cost• Support for Collaborative Partner Agreement


Release Schedule for SAP® Business Packages

Timeline: To be scheduled with ramp-up XI 3.0

SAP® Business Package for RosettaNet: Scenarios� Order to Invoice consisting of 8 different PIPs

SAP® Business Package for Chem eStandardsTM: Scenarios� Order to Invoice consisting of different Business Documents

Proposal based on Industry Priority


Release Schedule SAP® Business Packages

Timeline: To be scheduled after ramp-up XI 3.0

SAP® Business Package for RosettaNet: Scenarios� Forecasting� Replenishment� Preparation for Distribution� Design Win Management� Ship From Stock & Debit� Manage Mfg Work Order and WIP� Technical Support & Service Management

SAP® Business Package for Chem eStandards: Scenarios� Logistics� Replenishment � Forecasting� Financials� Exchange Proposal based on Industry Priority



Agenda



Focus High Tech Vertical Industry - RosettaNet



Marketplace Connectivity: The Basic Model

Marketplace Trading Partner

Market Analysis

ERP

SAPApplication

Document Management

CallCenter

SCME-Procurement

E-Sales

Connector/Connector/XI-AdapterXI-Adapter

r

public

Marketplace

Firewall Firewall

private

Connector/Connector/XI-AdapterXI-Adapte


Marketplace Adapter of SAP XI as an option to connect to mySAP Marketplaces

Currently SAP Customers are using the SAP Business Connector based SAP MarketSet Connector Version 3.0.

The MarketSet Connector 3.0 will go out of maintenance by the end of December 2003 (see SAP Note 632359).

Short-Term required action:SAP advices their customers to upgrade to the newer Version 3.1 (SAP Marketplace Connector) which will be based on the latest SAP Business Connector Release 4.7 with extended functionality available in Q4/2003.

Mid-Term Option:SAP Customers have the option to register in the XI 3.0 Ramp-up to use the appropriate XI-adapter (Marketplace Adapter) to connect to a MOE-based Public Marketplace.


XI 3.0: Exchange Infrastructure for Marketplace Connectivity

Execute Collaborative Business Processes


Integration Server

Integration Engine

Central Adapter Engine

Adapter FrameworkMessagingQueuing

Security Handling

Resource

Adapter

Integration Builder Integration Builder

Shared Collaboration Knowledge

Design Configuration


IntegrationRepository

Configuration &Admin of RAs

xcbl-MappingTemplates

Execute Collaborative Business Processes

Central Monitoring –ensures collaboration reliabilityCentral Monitoring –

ensures collaboration reliability

SAPSystems

SAPSystems

MarketplaceAdapter

MarketplaceAdapter

Partner Connectivity Kit

Partner Connectivity Kit

ApplicationTechn. System

File/DB/JMS

System Landscape Directory (SLD)System Landscape Directory (SLD)


SAPNetWeaverTM on-ramps to MySAP Marketplaces

MarketplaceTrading Partners MySAP Marketplace

IntegrationRepositoryIntegrationRepository



Configuration

Execute CollaborativeBusiness Processes

Design

System Landscape DirectorySystem Landscape Directory

Shared CollaborationKnowledge

Runtime Workbench

Runtime

Integration ServerIntegration ServerIntegration

EngineAdditional Integration Services

SAP Systems

3rd Party and Messaging Systems

SOAP Plain HTTP

Marketplaces

Partner Eco-System (additional 3rd Party Adapters and Industry Standards)


xCBLMappings

Marketplace Adapter(MML)


Questions?


Copyright 2003 SAP AG. Alle Rechte vorbehalten

� Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die aus-drückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankün-digung geändert werden.

� Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte können Softwarekomponenten auch anderer Softwarehersteller enthalten.

� Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® und SQL Server® sind eingetragene Marken der 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®, Informixund Informix® Dynamic ServerTM sind Marken der IBM Corporation in den USA und/oder anderen Ländern.

� ORACLE® ist eine eingetragene Marke der ORACLE Corporation.� UNIX®, X/Open®, OSF/1® und Motif® sind eingetragene Marken der Open Group.� Citrix®, das Citrix-Logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® und

andere hier erwähnte Namen von Citrix-Produkten sind Marken von Citrix Systems, Inc.� HTML, DHTML, XML, XHTML sind Marken oder eingetragene Marken des W3C®, World Wide Web Consortium,

Massachusetts Institute of Technology. � JAVA® ist eine eingetragene Marke der Sun Microsystems, Inc. � JAVASCRIPT® ist eine eingetragene Marke der Sun Microsystems, Inc., verwendet unter der Lizenz der von

Netscape entwickelten und implementierten Technologie.� MarketSet und Enterprise Buyer sind gemeinsame Marken von SAP AG und Commerce One.� SAP, R/3, mySAP, mySAP.com, xApps, xApp und weitere im Text erwähnte SAP-Produkte und –Dienstleistungen

sowie die entsprechenden Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und anderen Ländern weltweit. Alle anderen Namen von Produkten und Dienstleistungen sind Marken der jeweiligen Firmen.