Business to Business Integration Using Predefined Integration Content With SAP NetWeaver

SAP NetWeaver Process Integration 7.1 - B2B 1

SAP NetWeaver Regional Implementation GroupSAP Netweaver Product ManagementDecember 2007

SAP NetWeaver Process Integration 7.1B2B Integration UsingPredefined Integration Contentwith SAP NetWeaver


Benefits

After reading this document, you will be able to:Understand B2B Integration and the related challengesUnderstand the new B2B related features of SAP NetWeaver Process Integration 7.1Understand the key benefits that SAP NetWeaver provides for B2B Integration


1. Introduction: B2B Integration2. New B2B Capabilities of SAP NW 7.13. Connect Your Process Out-of-the-Box4. Summary

Agenda



Agenda


Why Enabling Business-to-BusinessProcesses?

B2B Integration Challenges

Complex Integration RequirementsNon-homogeneous infrastructuresIntegration via open networks (Internet)Diverse options for technical connectivity

Adapt to changing processes / business partnersChanging ability to dictate communication standardsConnect to all sizes of business partnersTime to connect new business partners is business critical

yourbusinesspartners

yourcompany

Partner

Market-place


B2B: Standards-based integration of inter-company processes

B2B Integration with SAP NetWeaver

yourbusinesspartners

yourcompany

Partner

Market-place

SAP NetWeaver Process Integration acts as B2B Gateway


One Integration Platform:B2B with SAP NetWeaver Process Integration

Industry StandardProtocols

B2BMessaging

Secu

rity

Enterprise ServicesRepository

Service Interfaces

Integration ProcessesMappings

Integration Scenarios

Integration Directory

Collaboration Agreements

Small TradingPartners

SAPPartnerConnectivity Kit

BusinessPartners

BusinessPartners

Integration Server

BPE

IntegrationEngine

AdvancedAdapter Engine

Collaboration Profiles

Adapter FrameworkMessagingQueuing

Security Handling

SAPApplication

Routing Rules

AnyApplication

Looking at the architecture you can see that a lot of changes have been incorporated for providing B2Bsupport.

First of all let us look at the different components of PI – we have the Enterprise Services Repository forthe design time information, the Integration Directory for configuration time information and the IntegrationServer which takes care of the runtime information using the different adapters.

The Enterprise Services Repository contains the different objects like business scenarios which are usedin the B2B scenarios.

The business processes are used to define B2B processes running across application components in andbeyond your enterprise.

The deliverd mappings are developed using the mapping tool which is part of the ES Repository.

The Integration Directory provides B2B related support – we have the possibility to define collaborationprofiles and collaboration agreements.

Routing rules for the configured B2B scenarios can be defined.

The XI message protocol is extended to support the adressing of senders and receivers on two levels. Thefirst level corresponds to a business system and the second level to a technical or semantic unit within abusiness unit or company.

In cross-company processes, you can specify entire company units as the sender or receiver, with eachcompany unit providing a multitude of services for communicating with other companies.


PI Landscape and Messaging

ConfigurationcacheIS

AdapterSender

AdapterReceiver

Q

AdministrationSecurity

MonitoringTracingLogging

Module Processor

Backend

Channel

Messaging

Configurationcache

AdapterFramework

MappingReceiverDetermination

Queue

PI Messages

System Landscape DirectoryHolds component descriptionincluding address data

Exchange ProfileHolds central connection descriptionsincluding user, passwords

RWB /SAP NWA

IBDir

Advanced Adapter Enginein Java EE 5

Message, Componentmonitoring et.al.

Scenario Configuration

httpIDocBPE

If you look at the flow of the message processing in the PI landscape, first the message is sent toPI using one of the adapters.

The message is processed by the module processor in the Adapter Engine. The message is thenforwarded to the Integration Server (IS) for further processing. In the IS the XI messages arepassed through a series of processing steps called the Pipeline services or PI pipeline. Once theprocessing is done in the Integration Server the message is then forwarded to the Adapter Engineand routed to the Receiver system using the adapter defined in the communication channel.


Secure Messaging and Routing for B2BIntegration

SAP NetWeaver Process Integration leverages the security capabilities toprovide secure message exchange for B2B scenarios.

These include:Data stream encryption via Secure Sockets Layer (HTTPS)Security based on the Web Service standard (WS-Security)Digital signatures to authenticate sending partners and to insure data integrityS/MIME supportMessage level encryption for secure message contents


Transport Level Security

Basic, Client Certificate, SAP Ass., SAMLHTTPs (SSL)WSBasic, Client Certificate, SAP Assert.HTTP / HTTPs (SSL)XI Protocol

Basic, Client CertificateHTTP / HTTPs (SSL)CIDX

Basic, Client Certificate



Basic, CRAM-MD5

Basic, Client Certificate, SAP Assert.



Basic, Client Certificate, SAP Assert.


Authentication Mechanism

HTTP / HTTPs (SSL)RNIF 1.1

HTTP / HTTPs (SSL)RNIF 2.0

HTTP / HTTPs (SSL)Marketplace

SMTP POP3, IMAP4 /HTTPs (SSL)Mail

HTTP / HTTPs (SSL)

SMTP / HTTPs (SSL)(Receiver only)

SOAP

FTP / FTPs (SSL/TLS)File/FTP

HTTP / HTTPs (SSL)Plain HTTP

RFC / SNCRFCRFC / SNCIDoc

Transport Protocol/Transport SecuritySupported by

Levels of Security

Note on CRAM-MD5

Challenge-Response Authentication Mechanism (CRAM) The authentication type associatedwith CRAM is "CRAM-MD5". The data encoded in the first ready response contains anpresumptively arbitrary string of random digits, a timestamp, and the fully-qualified primary hostname of the server. The syntax of the unencoded form must correspond to that of an RFC 822'msg-id' [RFC822] as described in [POP3]. The client makes note of the data and then respondswith a string consisting of the user name, a space, and a 'digest'. The latter is computed byapplying the keyed MD5 algorithm from [KEYED-MD5] where the key is a shared secret and thedigested text is the timestamp (including angle-brackets). This shared secret is a string knownonly to the client and server. The `digest' parameter itself is a 16-octet value which is sent inhexadecimal format, using lower-case ASCII characters. When the server receives this clientresponse, it verifies the digest provided. If the digest is correct, the server should consider theclient authenticated and respond appropriately.

More at http://www.faqs.org/rfcs/rfc2195.html

http://www.faqs.org/rfcs/rfc2195.html


Message Level Security

WS-SecurityXI protocol

PKCS#7CIDX

EncryptionNon-

Repudiationof receipt

PKCS#7RNIF 1.1

S/MIMERNIF 2.0

S/MIMEMail

WS-Security

S/MIMESOAP

WS-SecurityWS

TechnologyNon-

Repudiationof origin

SignatureSupported by

Levels of Security



Agenda


B2B Related New Capabilities of SAP NW PI 7.1

Reliable Messaging and Queuing

Software LifecycleSecurity

User Management

ScalabilityHigh Availability

Archiving

ConfigurationMonitoring

Administration

Dynamic Routing Transformation Connectivity

Infrastructure Services Java EE5 / ABAP

BAMProcess

Automation

Enterprise ServicesRepository & Registry

Enhanced DesignCapabilitiesService Enabling

Additional WS StandardsWS-RMSAML

High Volume SupportAdvanced AdapterEngineMessage packaging

Functional EnhancementsXML payload validationIntegration Directory API

Process Integration

Service Bus

User Interaction (for example, Business Task Management)

B2B Partner 3rd PartyMiddleware

3rd PartyApplicationSAP

A new release of SAP NetWeaver Process Integration is shipped in December 2007. This is called SAP NetWeaver Process Integration 7.1.Customers who have already installed SAP NetWeaver 7.0 (usage type PI) or SAP NetWeaver 2004 (XI 3.0), have the option to upgrade toSAP NetWeaver 7.1 Process Integration at no additional cost

The Process Integration release is one of the key building blocks of the enterprise SOA technology from SAP NetWeaver. We believe thatthe Process Integration capabilities will clearly be the cornerstone of customers' SOA strategy. These capabilities will continue to be usedheavily for middleware consolidation in customer landscapes, and become the SOA backbone.The release will mainly leverage functionalities for service enablement and service and process orchestration.

Highlights include:

– The Enterprise Services Repository containing the design time ES Repository and the UDDI Services Registry.

– SAP NetWeaver Process Integration 7.1 includes significant performance enhancements. In particular, high-volume messageprocessing is supported by message packaging where a bulk of messages are processed in a single service call.

– Additional functional enhancements, such as principle propagation based on open standards SAML, allows you to forward usercredentials from the sender to the receiver system.

– Also, XML schema validation, which allows you to validate the structure of a message payload against an XML schema.

– Also importantly support for asynchronous messaging based on the Web Services Standard Web Services Reliable Messaging (WS-RM) for both brokered communication and for point-to-point communication between two systems will be supported in this release.

– Besides that a lot of SOA enabling standards or WS standards are supported as part of this release again making it the coretechnology enabler of Enterprise SOA

– The new SAP NetWeaver Process Integration release this year will include major enhancements to the BPM offering as:

- Improved performance of the runtime (Process Engine) - message packaging, process queuing, transactional handling (logicalunits of work of process blocks and singular process steps - flexible hibernation)

- WS-BPEL 2.0 preview

- Further enhancements: modeling enhancements such as ,e.g., step groups, BAM patterns; configurable parameters;embedded alert management (alert categories within the BPEL process definition; human interaction (generic user decision),task and workflow services for S2H scenarios (aligned with BPEL4People)

– The process integration capability includes the integration server with the infrastructure services provided by the underlying applicationserver

– The process integration capability within SAP NetWeaver is really laying the foundation for SOA

– Standards compliant offering enterprise class integration capabilities, guaranteed delivery and quality of service


Enterprise Services Repository and Registry

ES RepositoryDefinition of Processes and ServicesService MetadataCentral modeling and design environment

Services RegistryYellow pages of ServicesDeployment information (i.e. endpoint)Services managementEase of consumption: Browse, discover,and use services.

Enterprise ServicesRepository and

Registry

Services Registry


Evolution of the Enterprise Services Repository

ANALYTICS/REPORTING

Bus.Partner Legacy

PEOPLE PRODUCTIVITY

SERVICE COMPOSITIONAND ORCHESTRATION

Business Objects,Components, and Engines

PartnerServices

LIFECYCLE MANAGEMENT

SAP’s EnterpriseServices

SERVICEENABLEMENT

Enterprise SOAThe ES Repository:

Evolved from the IntegrationRepository

Stores objects, such as global datatypes (GDTs) and service interfaces

Allows re-use of existing data andleverages existing investment

Now also stores new and enhancedobjects such as:

– Process Component Models

– Service Interfaces

The Integration Repository used by Process Integration has become the basis of the centralEnterprise Services Repository: powering Enterprise SOA and Service Enablement.

The first version of the ES Repository for customers is the PI based Integration Repository which isalready part of SAP XI 3.0 and SAP NW 7.0.

Customers can be assured that their investments in the Repository are protected because therewill be an upgrade possibility from the existing repository to the Enterprise Services Repository

The ES Repository is of course enhanced with new objects that are needed for defining SAPprocess component modeling methodology

The ES Repository in the new release will be available with SAP NetWeaver Process Integration7.1 and with SAP NetWeaver Composition Environment (CE) available in the same time frame

The ES Repository is open for customers to create their own objects and extend SAP deliveredobjects


Web Services Reliable Messaging (WS-RM)Asynchronous messaging (EO, EOIO) based on open WS standardNative support through Integration Engine (without adapter)

Integration Server

Integration EngineIntegration Engine

Business Process EngineBusiness Process Engine

Central Adapter EngineCentral Adapter Engine

FTP JMS SMTP …XI Protocol WS-RM

Web Services Reliable Messaging

The purpose of WS-RM is “… to create a generic and open model for ensuring reliable messagedelivery for Web services.” (OASIS)

WS-RM is an open WS standard for asynchronous messaging (EO (exactly once), EOIO (exactlyonce in order)). The SOAP adapter as of today supports already asynchronous messaging,however with proprietary means since there was no standard available before.

WS-RM is supported via an own entry in the Integration Engine (implemented in ABAP) and not theadapter engine. The XI 3.0 and XI 2.0 protocol will still be supported as well.

Other vendors like Microsoft and IBM also support WS-RM.


Principle Propagation based on SAMLForward user context from sender to receiverAuthorization check in receiving system based on original user

Principle Propagation Based on SAML

Request statusof order xyz??

IntegrationServer

Authorized??

Principle propagation allows to forward the user credentials (user name, password) from thesender to the receiver according to the single-sign-on principle. With this the user credentials don’thave to be configured in the receiver adapter, but can be dynamically forwarded from the sender.An authorization check in the receiving system based on the original user is performed.

The implementation of this feature is based on the open standard SAML and can be used withbackend systems that support the SAML technology.

This feature uses the WS-RM protocol.

Principle propagation based on SAP logon tickets as introduced with the previous PI releases(SP19 / SP10 ) will be still supported in SAP NW PI 7.1.


High Volume Support via Message Packaging

ISIS

Integration Engine& ccBPM Engine




AB

AP

Java

EDIEDI ...... FileFile

3rd PartyApplication


SAPSAP

Message PackagingProcess a bulk of messages in one service call (mapping, routing...)Reduce context switchesEnable mass operations on the databaseFor asynchronous scenarios

Customers require high-volume throughput.

A bulk of messages can be processed in one service call and thus context switches for mapping,routing, reading message header etc. can be reduced and mass operations on the database arepossible. This feature can be used in asynchronous scenarios only.

Performance improvement:

– For asynchronous scenarios message packaging plus bulk processing in ccBPM improvesthroughput for small messages (<100kB) by factor 2-10. This includes ccBPM improvementslike transient processing of multiple steps. I. e. factor 10 can be reached only for selectedscenarios.

– Performance improvement without using ccBPM are up to factor 3.5.


High Volume Support viaAdvanced Adapter Engine

SAPSAP

ISIS





AB

AP

Java

SOAPSOAP RFCRFC ......


Local Processing in the Advanced Adapter EngineNatural evolution of the adapter engineProvides mapping, routing to bypass the Integration ServerAdapter-to-adapter communicationFor synchronous and asynchronous scenarios

SAPSAP

Customers require high-volume throughput.

The Adapter Engine (central and non-central) evolves to “local processing engine”. This is a non-disruptive evolution, it can be used like a non-central adapter engine, it is a natural extension of PI.

It provides mapping, routing etc., and allows to by-pass the Integration Server (performanceimprovement up to factor 5).

Integration Server (IS) pain points are:

– One-side access only via XI-protocol

– Adapter to Adapter communication always goes through IS

– Mapping is always executed on the central IS

The Advances Adapter Engine reduces TCO, since no double-stack is required for certainscenarios.

Improved performance for adapter-to-adapter communication

Central configuration and monitoring through Integration Directory and Runtime Workbench, also ofmultiple “local processing engines”

Allows customers to distribute execution of mission-critical processes


Major Enhancements for Mapping

Function LibrariesRe-usable user-defined functions

Synchronous DB/RFC Look-upsUse graphical UI to model look-ups

Mapping ParametersSpecify mapping parameters atconfiguration time

Functions with Multiple ResultsLook-up function returns multiplefields

Function Libraries– The Repository saves the user defined functions you create in a message mapping or a mapping

template in a local function library belonging to a mapping object– to use a user defined function in more than one message mapping or mapping template you can create

the user defined functions in function libraries– The user interface is the same for local function libraries and function libraries that are independent of a

message mapping or mapping template.Synchronous DB RFC look-ups

– A mapping look-up enables a function in application system to be called while a mapping program isbeing executed. This therefore requires the Integration Server and the application system tocommunicate with each other. This is achieved by using an adapter, which can be accessed by using themapping program. In this way, the channel for communication is visible in the Integration Directory.

– You could use these mapping look-ups in a Java program, XSLT program, in a message mapping aswell as through JDBC and RFC look-ups

Parameterizable mappings– Define parameters in the mapping and configure the same in the integration directory – for example

which database you can look-upFunctions with multiple results

– Better flexibility in defining your mapping scenarios– You can feed multiple functions with the results of the mapping


XML Payload Validation

XML Payload ValidationValidate incoming/outgoing messages against XML schemaForward/Backward error handling

The payload of incoming and outgoing messages can be validated against an XML schema.

Three modes are supported:

– No validation

– Validation by Adapter (backward error handling): The validation is carried out on the AdapterEngine. If the validation fails, an error will be raised and the message won‘t be processed.

– Validation by Integration Engine (forward error handling): The validation is carried out on theIntegration Engine. If the validation fails, the message processing will be stopped in themonitoring. An administrator can decide depending on the severity of the validation failurewhether the message should be processed. He can correct the message payload or he candecide whether the message should not be processed any further.


Mass Changes via Integration Directory API

Integration Directory APIApplication Programming Interface (API) allows to access, edit, activate objectsin Integration Directory

Examples: Communication channels, business systems, receiverdetermination, interface determination, change lists

API Access via Web ServiceWSDL files are stored in Enterprise Services Repository as externaldefinitions

API allows to create, update, delete, read, search etc. objects in IntegrationDirectoryAPI is particularly suitable to perform mass changesContent of Integration Directory can be read by API in order to use this input fordefining own views, statistics etc.

Objects of Integration Directory can be accessed, e. g. communication channels, business systems, receiverdetermination, interface determination, change lists.Access is provided via Web Service, the WSDL files are stored in the ES Repository as external definitions.The Directory API allows to create, update, delete, read, search etc. objects in Integration Directory.Mass changes of attributes, e. g. names of objects, are supported. Furthermore, the content of the IntegrationDirectory can be read by the API and can be used for any kind of representation, e. g. statistics.Examples:

– Making Mass Changes in the Integration Directory.– Using the programming interface you can make mass changes in the Integration Directory which you

would not otherwise be able to do using the user interface, or at least only with a very time-consumingmanual procedure. You can realize the following possible applications:

- If you have newly installed SAP NetWeaver Process Integration and would like to fill the IntegrationDirectory with your existing configuration data then you can import the available configuration datausing a program in the Integration Directory.

- You can edit the same attributes in a large number of configuration objects at the same time.- If you move an object in the Integration Repository to another namespace or to another software

component version, then you need to update the object reference for the configuration objectconcerned accordingly. You can do this for multiple configuration objects by using the programminginterface.

– Individually Presenting the Contents of the Integration Directory- You can retrieve and individually present the contents of the Integration Directory. You can create

your own views of the contents of the Integration Directory, for example for the purpose of statistics.


1. Introduction: B2B Integration2. New B2B Capabilities of SAP NW 7.13. Connect Your Process Out-of-the-Box

1. Introduction: Business Value2. RosettaNet3. CIDX4. PIDX5. EDI6. Enterprise Services Bundles

4. Summary

Agenda




4. Summary

Agenda


Supporting Standards to Improve Processes

Industries involved in IndustryStandards Support

High TechChemicalAgrichemicalOil and GasAutomotiveAerospace and DefenseConsumer ProductsMill ProductsFinancialOthers…

UN/CEFACT

GS1


Chemical Companies CIDXTM Customer

Shipment Notice

PO

Order Response /Confirmation

Payment

Invoice

Enterprise BApplication

Enterprise BApplication

Enterprise AApplication

Enterprise AApplication

Order Change

Supplier PIDXTM Oil&Gas Companies

SAP Business Packages – Example

Book transport and get transport booking confirmation

Inform the Logistics Site of the planned transport

At dispatch send ‘loaded volume’ to Carrier (later used for self-billing)

At arrival at the Logistics Site, inventory is updated.


Business Processes

Process PO Send POCustomer

Send POSupplier

ProcessSales Order

CustomerCustomer SupplierSupplier

Receive POAcknowledge

Send POAcknowledge

Send POResponse

Close

Send PO

Receive POResponse

Send POResponse

Acknowledge

Receive PO

Send POResponse

Receive POResponse

Acknowledge

Receive PO

CheckCustomer

CheckCredit

CheckAvailability

Create SalesOrder

Receive POAcknowledge

Send POAcknowledge

Send POResponse

Close

Receive PORequest

SelectSupplier

GenerateRFQ

SendRFQ

Select RFQResponse

SendPO

Close

Send PO

Receive POResponse

Send POResponse

Acknowledge

Receive PO

Send POResponse

Receive POResponse

Acknowledge

Receive PO

CheckCustomer

CheckCredit

CheckAvailability

Create SalesOrder

Private process Public process Public process Private process

Backend

CRM

SCM

ERP

A business process consists of a set of steps that, when executed, accomplish acertain business goal.

For instance, a customer issues a request for a product from a supplier by sending apurchase order containing the descriptions of the items to be purchased. The supplierchecks for the availability of the items in its inventory before accepting or rejecting thecustomer's purchase of the specific items. These steps constitute a purchase orderbusiness process.

To the customer in the purchasing scenario, some business process steps are neithervisible nor particularly relevant. For instance, checking the availability of the items inthe supplier's inventory is one such step that is particularly relevant to the supplier butnot visible to the customer. Similarly business process steps on the customer side areneither visible nor relevant.

Public business processes consist of steps that are visible to both parties conductingthe business, whereas private business processes consist of steps that are visibleonly to one party.


iWay Adaptere.g. Siebel

Value Proposition of Content

SAP Adaptere.g. RFC/BAPI

Orchestration/BusinessProcess

Mapping

Interface Definition

Additionalbusiness valuefor customers

A customer gets the SAP adapters together with PI „out of the box“

Technical connectivity to other backend systems can be established by installing the iWay adapterafterwards.

– Separate installation step are required, but these are fully integrated into SAP Service Marketplaceprocesses

– Separate license fees

Finally the customer wants to integrate applications. To achieve this, content (service definitions,mappings, eventuelly business processes), must be built.

– iWay ships the Application Explorer

– There is no predefined content (e.g. as template for frequently used scenarios) available


Ready-to-Run Integration Scenarios

Content from SAP Partners

SAP Application Content SAP Business Packages

Partner Content A2A/B2B

Enhance Package Add new

Pckg.Enha

nce

Pack

g.

Add new Pckage

Content from SAP

Content from SAPContent delivered by SAP can be classified in two categories:

SAP Application Content (Generic integration content provided by SAP applications)BENEFITS

– Out-of-the-box integration scenarios

– Harmonized application and integration logic

– Simplified upgrade of end-to-end scenarios

SAP Business Packages (Integration Content focussing on vertical industry standards e.g. RosettaNet; CIDX, S95, …)BENEFITS

– Enable seamless B2B communication

– … based on Industry Standards

– Easy mapping of industry standards to SAP applications

Content from SAP PartnersMany partners are providing integration content that extends the content offering of SAP (for A2A / B2B scenarios)

Certified integration scenarios

Filling white spaces in SAP’s content offering

Around 150 partners certified/in certification on integration scenarios


Ready-to-Run Integration ScenariosMore Information

* http://service.sap.com/xi xi in detail XI-content-catalog

SAP Content Catalog*

PI-Contentfrom SAP

PI-Contentfrom Partners

Check out the PI content catalog. It contains content offerings from SAP as well as from certifiedpartners

http://service.sap.com/xixi


Connectivity Info on SAP Service Marketplace

SAP Service Marketplace: http://service.sap.com/xiSAP XI in Detail Connectivity Connectivity SAP NW 7.0 / ‘04

http://service.sap.com/xi


Partner Eco System

SAP relies on a system of partners to provide solutions for otherapplications and certain industry standards

Together with these partner solutions SAP NetWeaver Process Integrationpositions clearly as complete B2B gateway

Connectivity Reseller Agreements withSeeburger AGiWay SoftwareInformatica

3rd-Party solutions are sold and delivered through SAP

Technical support for partner solutions via theSAP Support Portal, 24x7


Certification Programs for Process Integration

* http://www.sdn.sap.com Partners and ISVsIntegration and Certification Exchange Infrastructure

PI Based Certification Programs*

http://www.sdn.sap.com/




4. Summary

Agenda


What is RosettaNet?

RosettaNet is named after Rosetta Stone.

A Consortium of more than 500 companies founded in 1998Create & Implement internet based e-biz standards in High Tech IndustryBoards: 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, SMICIntel, Cisco, TI, HP, Dell, Applied Materials, Motorola, MolexNokia, STMSAP, Microsoft, IBM, Oracle, i2, webMethods, TIBCO

RosettaNet is not a marketplace, RosettaNet is not making any money out of the standards.RosettaNet belongs to its members.

It is a non-profit consortium with more than 500 members. It is founded back in 1998. SAP isone of the founding members. SAP is on the solution provider board since 1998.

RosettaNet got affiliates around the globle, Europe, Americas, Japan, Korea, Singapore,Taiwan, Korea, Malaysia, & the Philippines.

The list of RosettaNet members include all High-Tech companies. These companies arepushing the standards very hard.

RosettaNet standards form a common e-business language, aligning processes betweensupply chains on a global basis.

RosettaNet standards offer a robust non proprietary solution, encompassing data dictionaries,implementation framework, and XML based message schemas and process specifications, fore-business standardization. These standards are free to the public on the RosettaNet webpage.

RosettaNet was founded to improve supply-chain efficiency, to increase supply-chain visibility,and to enhance collaboration in a secure and reliable fashion across trading networksseparated geographically.

RosettaNet has achieved tremendous adoption of its standards in the high-tech manufacturingsupply chain over the past three years.


Main Components of RosettaNet Standards…

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

PIP definesRoles for Trading PartnersThe Business Process is defined in terms of Business Activity

Example: Create Purchase OrderThe messages exchanged between Roles are classified into:

Business Action messageBusiness Signal message

RosettaNet activities can be classified into:One-actionTwo-action

RosettaNet PIPs or Partner Interface Processes are XML based dialogs that define businessprocesses between trading partners.

The messages involved in a PIP business document exchange are classified into “Business Action”and “Business Signal” message. Business actions are messages with contents that are of abusiness nature.

Business signals are positive and negative acknowledgment messages that are sent in response tobusiness actions for the purpose of aligning PIP state between the partners.

Broadly speaking, RosettaNet activities can be classified as one-action and two-action activities.

A one-action activity involves the initiator sending a request action to the responder and the latterreturning a business signal.

A two-action activity involves the initiator sending a request action to the responder, and theresponder returning a receipt acknowledgment to the initiator. This is followed by the responderreturning a response action to the initiator, and the initiator returning a receipt acknowledgement tothe responder.

One-action and two-action activities can also use either one or both of the synchronous andasynchronous modes of interaction, as prescribed by their corresponding PIP specifications.


Industry Standard Adapters – RNIF Adapter

Pack and unpack RosettaNet messagesStructural verification of the messageheadersHandling of message securityUses the Collaboration PartnerAgreements to manage RosettaNet PIPexchangesRosettaNet defined error handlingprocedureMessage monitoring & auditingReact to failures in the backendapplications

RNIF adapter

Industry Standards Content

IntegrationServer

EnterpriseServicesRepository

AdapterEngine

AdapterFramework

The RNIF Adapter is used for sending messages between the Integration Server and yourpartner system by transforming the XI message format into RosettaNet PIP message formatand so on.

The RNIF Adapter executes the transport, packaging and routing of all PIP messages andbusiness signals based on the relevant information retrieved from the Enterprise ServicesRepository and Integration Directory at runtime

The RNIF Adapter is part of the Adapter Framework. The inbound RNIF Adapter is locatedbefore the Integration Engine pipeline, and calls this pipeline while the outbound RNIF Adapteris called by the pipeline.


Business Package for RosettaNet

ApplicationApplicationBusiness Logic

Interface Interface Interface

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

Map Map Map

RosettaNet PIPs

SAP Netweaver PI

BusinessLogic

IntegrationLogic

IndustryStandardprocesses

Business Packages include scenario descriptions, business processes,message interfaces, message types, mappings, adapter etc.

The SAP Business Package for RosettaNet offers a comprehensive solution that addressesRosettaNet standards – not just tools.

Dedicated, prebuilt, out-of-the-box message and process mappings between the applicationinterfaces and business logic of various SAP solutions and RosettaNet PIP payloads are deliveredwith the Business Package.

SAP delivers Technical Adapters like RNIF Adapter, Mapping & Business Processes plus theBusiness Logic in the Back end.

SAP is developing SAP Business Packages for the High tech as well as the chemical and Oil &Gas industry.


Enterprise Services RepositoryRosettaNet Content

Two main software componentsin the repositoryRosettaNet software componentcontains the standard contentRosettaNet_ERP softwarecomponent contains theintegration content


ExampleRosettaNet PIP* 3A4 as Integration Scenario

MappingsPIP standardto application

standard

MappingsPIP standardto application

standard

External DefinitionsDTDs describingRosettaNet PIPs

External DefinitionsDTDs describingRosettaNet PIPs

* PIP = Partner Interface Processes


RosettaNet PIPs - Out of the Box


Reduces time to hook up with new Business Partners

Pre-Defined Configuration

ConfigurationTemplates

ConfigurationTemplates

ModelConfigurator

ModelConfigurator

Configuration templates for PIPs are delivered as part of the content:

Enables ease of configuration

Used during the configuration of the RNIF adapter in the Integration Directory.

Templates refer to the business activity performance controls of the RosettaNet Standard

Model Configurator

Guides you through the configuration process

Specific settings for B2B configuration

This speeds up the process to set-up new BP-connections


SAP NW PI

RosettaNet Scenario

PO Req

ACKORDERS05

ORDERSPOrder CONF

ACK

RNIFRNIF IDOCIDOC

SAP Business Packagefor RosettaNet

IntegrationDirectory• Collaboration

Profiles• Security settings• …

ESRepository• Interfaces• Mappings• Integration-scenarios

• …

SAPApplication

Partner

RosettaNet Partner Interface Process 3A4:

Buyer sends a purchase order request action to PI via RNIF adapter. The RNIF Adaptertransforms the message protocol into a message protocol that is understood by the PI andsends the message to the Integration Server for further processing.

PI receives the message and sends a receipt acknowledgement via the RNIF Adapter to theBuyer.

PI transforms the PIP3A4 RosettaNet Standard message to the SAP message (IDOCORDERS05) and sends the message to the backend R/3 system via the IDoc adapter forfurther processing.

Backend R/3 processes the IDoc and creates a Sales Order in the system and send the Orderconfirmation message (ORDERSP IDOC) back to the waiting PI process.

PI transforms the received confirmation IDoc to the PIP3A4 Purchase Order Confirmationmessage format.

The RNIF Adapter accepts the message from the Integration Server, transforms the messageprotocol from PI to PIP message protocol, and sends the message to the RosettaNet-compliantsystem.

The Buyer sends the receipt acknowledgement for the received confirmation message.



1. RosettaNet2. Introduction: Business Value3. CIDX4. PIDX5. EDI6. Enterprise Services Bundles

4. Summary

Agenda


SAP TechEd ‘06

Configure Landscape and Install BusinessPackage –Process In Detail

Download SAP Business Package fromService Marketplace

Define SLD-objects(Product; Software Component, …)

Import Business Package (tpz file) intorepository

ES Builder

ESRepository

(IR)

Central Monitoring

IntegrationDirectory

(ID)

System Landscape Directory (SLD)

Solution Manager

Further InformationCIDX Scenario Description / Configuration Guide, …

https://service.sap.com/ibc --> Industry Solutions --> SAP for Chemicals Order to Invoice

SAP help portalhttp://help.sap.com/saphelp_nw2004s/helpdata/en/index.htm --> Technology Consultants Guide

Enabling A2A Config of UT PI Template Based Basic Config Importing PI Content

Enabling SAP Business Package for

Model Integration Scenarios

Define Integration Processes as process bridge between processes running in applications

Define Interfaces, Message Types and Data Types.

Import DTD, WSDL and XSD and reuse as interfaces

Define Mapping using the mapping editor or import your mappings and reuse.

https://service.sap.com/ibc--

http://help.sap.com/saphelp_nw2004s/helpdata/en/index.htm--


Definition of process flows +Chem eStandard messages + Mapping to ERP backend via …

CIDX Business Package – Repository Objects

External DefinitionsExternal DefinitionsIntegration ScenariosIntegration Scenarios

Message interfacesMessage interfaces

Message MappingsMessage Mappings

Mapping TemplatesMapping Templates


Configuring Business PackageProcess In Detail

Configure communication profile toset Up new BP-communication

– Party = New BP– Service = Chem eStandard Message– Channel = CIDX adapter (RNIF 1.1)

Set up secure communication followingCIDX security standards (non-repudiation, …)

Speed up configuration– Configuration Templates– Model Configurator

Integration Builder

ESRepository

(IR)

Central Monitoring

IntegrationDirectory

(ID)

System Landscape Directory (SLD)

Solution Manager

Configuring SAP Business Package for




4. Summary

Agenda


PIDX Content in Enterprise ServicesRepository

PIDX software component inthe Enterprise ServicesRepository

PIDX software componentcontains the standard content

All the Order-to-Invoice PIDXmessage types are deliveredas external definitions

PIDX over RNIF 2.0


Configuration Using the Model Configurator

Generate Configuration

Transfer scenariofrom repository

AssignParty & Comm.

Component

AssignCommun.-Channel




4. Summary

Agenda


Electronic Data Interchange

Electronic Data Interchange (EDI)Computer-to-computer exchange of structured informationAgreed message standardsFrom one computer application to another by electronic meansMinimum of human intervention.

History of EDIOriginated in the 60’s/70’sSeveral industries invented their own sets of standardized data formats includingTDCC – 1960

ANSI ASC X12 – 1979Over 300 transactions sets in a single version

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

Other EDI standardsHL7, ODETTE, TRADACOM,SWIFT etc.


SAP NetWeaver EDI Adapter: Architecture

IndustryStandardProtocol

SAP CRM, SRM, SCM SAP Industry Solution

Integration ServerES Repository& Integration Directory Integration

Engine

Industry-specificcontent:

• Mappings as JAVA code• Message descriptions• Partner master data• Business Scenarios und

Processes

SEEBURGERAdapter

SEEBURGERAdapter

Adapter Engine

SAP NetWeaverProcess Integration

SEEBURGERAdapter

SEEBURGERAdapterAdvanced

Adapter Engine

Adapter EngineSEEBURGER

AdapterSEEBURGER

Adapter

SEEBURGER EDI/ B2BTechnology suite• Conversion• Communication• Components

Adapter Framework

Non-SAP-System

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

Secu

rity

Customer

Supplier

Logistics

Bank

EDI/B2Bpartner

Industrynetworks

Seeburger’s B2B and Industry-specific content in the Enterprise Services Repository includes:

– Mappings, message descriptions, adapter metadata, partner master data, integration scenarios andprocesses.

– Seeburger EDI and B2B technology suite in the Adapter framework includes conversion, communicationand components.

– Seeburger Adapters includes industry-standard protocols such as AS1, AS2 and other EDI-specificadapters


Example: Message Mapping of EDI to IDoc


Example: Configuration of anOFTP-Sender-Channel


Example: EDIFACT->XML-EDIFACT


Adapters by Seeburger for Process Integration

Technical EDI AdaptersAS2 (EDIINT/HTTP(S)); Protocol: AS2OFTP; Protocol: OFTP/ISDN, OFTP/TCPIPVAN Access; Protocol: P7 / X.400, VAN FTP

Business EDI AdaptersGeneric EDI; Protocol: OFTP/ISDN or P7 / X.400, VAN FTPEDI Converter: ANSI X.12, EDIFACTVarious Mapping Templates: PO, Order confirmation, …Payment (Financial Service Providers); Protocol: OFTP/ISDN, P7, VAN FTPEDI Converter: EDIFACT, SWIFTvarious Mapping Templates: Payment orders, Debit advice …

Industry Specific EDI AdaptersAerospace and DefenseAutomotiveChemicalsConsumer ProductsHigh-TechPaperPharmaceuticalRetail

Incl. various communication protocol handlers, EDI-XML Converter, Mapping Templates, EDI-XMLSchema Definitions


Adapters by iWay Softwarefor Process Integration

Application AdaptersAriba Baan BroadvisionClarify JDE One World XE JDE Worldi2 Lawson Microsoft CRMManugistics Oracle Applications PeoplesoftQAD MFG Pro Siebel Vantive

Industry Standard AdaptersSwift Transora UCCnet

Technical AdaptersAS1 (EDIINT/SMTP) AS2 (EDIINT/HTTP(S)) BEA WLICOM+/DCOM Corba Lotus NotesTibco Rendezvous

Mainframe/transaction AdaptersCICS TMS/IMS Telnet (3270)Telnet (5250) Tuxedo

Optionally further adapters can be added from a list of 160 iWay adapters, e. g. AS3 (EDIINT/FTP), HL7


SAP Conversion Agent by Informatica

Seamlessly integrated into PIBi-directional conversion of unstructured and semi structured data from / to XMLTransformation on message payloadProtocol support via SAP’s technical adapter (PI adapter framework)Transformations integrated via PI AF module

SAP Java EE 5PI Adapter Framework

Adapter

Adapter

Text2XML

XML2Excel.....

PDF2XML

ConversionAgent Studio

ConversionAgent Services

Conversion Agent Engine

CA AFModule

Conversion Agent JEE 5Lib

The Conversion Agent delivery includes Adapter Framework modules that enable the usage ofConversion Agent transformations based on all (java based) SAP technical adapters in PI

Conversion Agent transformations are used for payload transformations; the adapters take care ofthe protocol layer.


Supported Data Formats by Informatica(Partial List)

UNSTRUCTUREDMicrosoft WordMicrosoft ExcelPowerPointPDFStar OfficeWord PerfectASCII reportsHTMLEBCDICUndocumented binariesFlat filesRPGANSI

PRINT STREAMSAFPPost ScriptDJDE

SEMI-STRUCTUREDHL7HIPAAASTMANSI–X12EDIFACTCOBOLFIXCargo IMPMVRSWIFT

OTHER STANDARDSLegalXMLIFXcXMLebXMLHL7 V3.0ACORD (AL3, XML)

… using SAP technical adapter and Conversion Agent:

These are the data formats supported by SAP Conversion Agent by Informatica.

Based on SAP adapter technology for transport protocol support Conversion Agentenables bi-directional transformation from/to these formats




4. Summary

Agenda


SAP’s Approach to SOA for More FlexibilityEnterprise SOA Enriches SOA with Business Content to Ensure Integrity

Enterprise SOA enriches industry-standard service-oriented architectureswith productized services as well as business semantics in a unifiedrepository to ensure business process integrity for enterprises anddeliver advanced business process flexibility.

It increases scalability, reusability, and governance in SOA-basedarchitectures to reduce TCO, enhance responsiveness, andaccelerate business process change and innovation.

SOA

Delete fromDatabase

Roll BackInventory

CancelShipment

CancelInvoicingAdjust

Planning

NotifySuppliers

SendNotification

Order to CashCancelOrder

Productized services

Business semantics

Unified repository

Ensures integrity

ENTERPRISE SOA

CancelOrder

Order to CashManually built

Low reusability

No governance

Leads to chaos


Introducing Enterprise Services BundlesMake the Value of Enterprise SOA “Consumption Ready”

Deliver high-impact business capability

Easy to implement

Provide “quick wins” for the business

Enterprise Services:Highly integrated Web services combined withbusiness logic and semantics thatcan be accessed and used repeatedly to supporta particular business processEnterprise Services Bundles:

Enterprise services and bundlescan be explored and tested atSAP’s Enterprise Services Workplace:

https://www.sdn.sap.com/irj/sdn/esworkplace

Enterprise ServicesBundles

Enterprise Servicesin ES Repository

Benefits of Enterprise Services Bundles:

Group-relevant enterprise servicesfor a specific business scenarioCross-industry bundlesIndustry-specific bundles

https://www.sdn.sap.com/irj/sdn/esworkplace


Governance for Enterprise Services

Semantics/Taxonomy Global Data Types

Architectural Guidelinesand Standards

Company-wide defineddata types based oninternational standardsSemantic building blocksfor interfaces

Business semantics consistency:same understanding between serviceconsumers and service providersTechnical(Transport protocols, security standards,formats …)

Enterprise Services Repository

The enterprise servicesrepository is the centralrepository in which serviceinterfaces and enterpriseservices are modeled andthe correspondingmetadata is managedthroughout the life cycle

Common modelingand implementationguidelines provenby SAP developmentare the basis forevery (new) servicedevelopment

SERVICE DEFINITION

Decision onservice cut

Rawdesign

Elements/data types

Finaldesign

Enterin ESR

Global DataType (SAP)

Core Data Type(CCTS)

Primitive Data Type(XSD)


Bundles of Enterprise Services

Enterprise AssetManagement

Asset ConfigurationMaintenance ProcessingMaintenance ServiceCollaboration

Trading IndustriesTrade and CommodityManagementDemand Management v2

Order to CashCustomer Fact Sheet v2Electronic Bill Presentment andPayment v2Order to CashBank Relationship ManagementExternal Cash Desk

Hire to RetireAbsence Employee TimeRequest (Duet)Benefits and Compensation(Duet)Organizational Management(Duet)Personnel Admin (Duet)Travel Management

ManufacturingBatch Traceability and AnalyticsIntegration of MES v2Integration of QualityManagement Systems v2

www.sdn.sap.com Enterprise SOA Explore Enterprise Services ( ES Workplace / ES Wiki)*Disclaimer: SAP reserves the right to change the ES bundles listed without prior notice.**Some of the bundles listed on this page can be previewed in the ES Wiki.

Mid-Year Shipments 2007

Service for CustomerCustomer Service ExecutionInternal Service Request(Duet)Advanced Meter Infrastructure(Utilities)

Idea to ProductTechnical DocumentManagement Connectivity v2

Logistics ExecutionInventory LookupHandling of Business EventsYard and Storage ManagementProcessesCustomer Collaboration for the SupplyChainSupply Network and ProductionPlanning ProcessesTransportation Collaboration andSubcontractingKanban ProcessingManage Devices Through EnterpriseServicesManagement of Tag IDs and TagObservations

http://www.sdn.sap.com/


Bundles of Enterprise ServicesYear-end shipments 2007 – PREVIEW*

PLANNED RELEASEin Dec 2007

Logistics ExecutionIntegration with ExternalWarehouse Mgmt SystemIntegration with TransportManagement SystemSupply Chain Operations andExecution in Oil and Gas

Order to CashOrder to Cash v2 (incl. B2B)Quote to Order for ConfigurationProductsFin. SSC – Interco. ProcessingReal Estate ReservationAvailability Issue Resolution andBack-Order Processing

ManufacturingBatch Traceability and Analytics v2

Public SectorPublic Sector Budget ManagementReserve and Commit BudgetMulti-Channel Tax and RevenueManagement

* Disclaimer: As the roll-in for the winter edition is not completely finalized, the list of enterprise service bundles shown here is subject to changeby SAP without prior notice. Not all scenarios and industries are listed here.

Service for CustomerCustomer Service Execution v2

Procure to PayDocument BuilderProcure to Pay (incl. B2B)Outsourced ManufacturingSupplier Collaboration in the SupplyChain v2

Enterprise Asset MgmtAsset Configuration v2Maintenance Processing v2Maintenance Service Collaboration v2Project System

Hire to RetireHCM Master DataHCM Time ManagementHCM Org ManagementHCM Learning Solution

Banking and InsuranceAccounting IntegrationFS Business Partner Maintenance v2ISV Integration with Analytical BankingLoans Management Bus. Operations v2Insurance Billing and PaymentInsurance Extension Claims InvestigationInsurance Extension ReportingInsurance Document VendorInsurance Credentialing

Trading IndustriesMerchandise and AssortmentPlanning Int.Chargeback ManagementPOS IntegrationRetail Unified Demand ForecastTrade and Commodity Managementv2Trade Price–Specific Contract

HealthcarePatient AdministrationResource Planning and SchedulingMed. Activities, Patient Billing, and InvoiceMedical Documentation and CodingMedication and Materials ManagementCollaborative Health NetworkSupply Chain Healthcare Providers

And more . . .Advertising Management (Media)Compliance Relevant Data Exchange –eLogbook (Defense)Information Integr. Systems (GIS) (Defense)Environment, Health, and Safety (EH&S)ServicesIntegration of Learning Management SystemsSubscription Management (Media)

Year-End Shipments 2007



Agenda


Why use SAP NetWeaver Process Integration7.1?

Reasons for using SAP NW PI 7.1 as B2B GatewayUse Process Integration as the SOA backbone for all integration needsEstablish SAP NetWeaver Process Integration as SOA middleware with central design,configuration, monitoring, alertingLeverage pre-configured solutions that are based on open standards and provide businessprocesses, mappings etc.Replace all isolated integration systemsUtilize same skill set for all integration requirements

BenefitsLower TCOIncrease business agilityImprove business transparency


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 changedwithout prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, 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, System i, System i5, System p, System p5,System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks orregistered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated 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 registeredtrademarks 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. Datacontained 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 writtenpermission 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, andfunctionalities 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 issubject 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 containedwithin 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 aparticular 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 limitationshall 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 thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

Documents

Business to Business Integration Using Predefined Integration Content With SAP NetWeaver