SAP NetWeaver Regional Implementation Group
SAP Netweaver Product Management
B2B Integration Using
Predefined Integration Content
with SAP NetWeaver
Benefits
Understand B2B Integration and the related challenges
Understand the new B2B related features of SAP NetWeaver Process Integration 7.1
 
1. Introduction: B2B Integration
3. Connect Your Process Out-of-the-Box
4. Summary
1. Introduction: B2B Integration
3. Connect Your Process Out-of-the-Box
4. Summary
Why Enabling Business-to-Business
 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 
business
partners
your 
company
B2B: Standards-based integration of inter-company processes
B2B Integration with SAP NetWeaver 
your 
business
partners
your 
company
 
One Integration Platform:
Industry Standard Protocols
      i      t     y
 Any  Appl ication
Looking at the architecture you can see that a lot of changes have been incorporated for providing B2B
support.
First of all let us look at the different components of PI – we have the Enterprise Services Repository for 
the design time information, the Integration Directory for configuration time information and the Integration
Server which takes care of the runtime information using the different adapters.
The Enterprise Services Repository contains the different objects like business scenarios which are used
in the B2B scenarios.
The business processes are used to define B2B processes running across application components in and
beyond 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 collaboration
profiles 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. The
first level corresponds to a business system and the second level to a technical or semantic unit within a
business unit or company.
In cross-company processes, you can specify entire company units as the sender or receiver, with each
 
PI Landscape and Messaging
including address data
including user, passwords
RWB / SAP NWA
http IDoc BPE
If you look at the flow of the message processing in the PI landscape, first the message is sent to
PI using one of the adapters.
 
Secure Messaging and Routing for B2B
Integration
provide 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 integrity
S/MIME support
 
Transport Level Security
Basic, Client Certificate, SAP Assert.XI Protocol
Basic, Client CertificateTTP / HTTPs SSL)CIDX
Basic, Client Certificate
Basic, Client Certificate
Basic, Client Certificate
Basic, Client Certificate
Basic, Client Certificate
Basic, Client Certificate
Challenge-Response Authentication Mechanism (CRAM) The authentication type associated
with CRAM is "CRAM-MD5". The data encoded in the first ready response contains an
presumptively arbitrary string of random digits, a timestamp, and the fully-qualified primary host
name of the server. The syntax of the unencoded form must correspond to that of anRFC 822
'msg-id' [RFC822] as described in [POP3]. The client makes note of the data and then responds
with a string consisting of the user name, a space, and a 'digest'. The latter is computed by
applying the keyed MD5 algorithm from [KEYED-MD5] where the key is a shared secret and the
digested text is the timestamp (including angle-brackets). This shared secret is a string known
only to the client and server. The `digest' parameter itself is a 16-octet value which is sent in
hexadecimal format, using lower-case ASCII characters. When the server receives this client
response, it verifies the digest provided. If the digest is correct, the server should consider the
client authenticated and respond appropriately.
More at http://www.faqs.org/rfcs/rfc2195.html
Message Level Security
1. Introduction: B2B Integration
3. Connect Your Process Out-of-the-Box
4. Summary
B2B Related New Capabilities of SAP NW PI 7.1
Reliable Messaging and Queuing
BAM Process
B2B Partner  3rd Party
Middleware 3rd Party
 App licat ionSAP
 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 to
SAP 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 that
the Process Integration capabilities will clearly be the cornerstone of customers' SOA strategy. These capabilities will continue to be used
heavily 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 message
processing is supported by message packaging where a bulk of messages are processed in a single service call.
 – Additional function al enhancements , such as principle propagation based on open standards SAML, allows you to forward user 
credentials 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 core
technology 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 (logical
units 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 application
server 
 – 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 Repository Definit ion of Processes and Services
Service Metadata
Services Registry
Enterprise Services
Repository and
Evolution of the Enterprise Services Repository
ANALYTICS/REPORTING
Bus.
Partner  Services
types (GDTs) and service interfaces
 Al lows re-use of exist ing data and
leverages existing investment
objects such as:
 – Process Component Models
 – Service Interfaces
The Integration Repository used by Process Integration has become the basis of the central
Enterprise Services Repository: powering Enterprise SOA and Service Enablement.
The first version of the ES Repository for customers is the PI based Integration Repository which is
already part of SAP XI 3.0 and SAP NW 7.0.
Customers can be assured that their investments in the Repository are protected because there
will 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 SAP
process component modeling methodology
The ES Repository in the new release will be available with SAP NetWeaver Process Integration
7.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 delivered
objects
Web Services Reliable Messaging (WS-RM)
 Asynchronous messaging (EO, EOIO) based on open WS standard
Native support through Integration Engine (without adapter)
Integration Server 
Integration Engine
Web Services Reliable Messaging
The purpose of WS-RM is “… to create a generic and open model for ensuring reliable message
delivery for Web services.” (OASIS)
WS-RM is an open WS standard for asynchronous messaging (EO (exactly once), EOIO (exactly
once 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 the
adapter 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 SAML
Forward user context from sender to receiver 
 Author ization check in receiv ing system based on original user 
Principle Propagation Based on SAML
Request status
Principle propagation allows to forward the user credentials (user name, password) from the
sender to the receiver according to the single-sign-on principle. With this the user credentials don’t
have 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 with
backend 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
 
High Volume Support via Message Packaging
IS
Message Packaging
Process a bulk of messages in one service call (mapping, routing...)
Reduce context switches
For 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 are possible. This feature can be used in asynchronous scenarios only.
Performance improvement:
 – For asynchronous scenarios message packaging plus bulk processing in ccBPM improves throughput for small messages (<100kB) by factor 2-10. This includes ccBPM improvements like transient processing of multiple steps. I. e. factor 10 can be reached only for selected scenarios.
 
High Volume Support via
Natural evolution of the adapter engine
Provides mapping, routing to bypass the Integration Server 
 Adapter-to-adapter communication
SAP
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 (performance
improvement 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 certain
scenarios.
Central configuration and monitoring through Integration Directory and Runtime Workbench, also of 
multiple “local processing engines”
 
Major Enhancements for Mapping
Mapping Parameters
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 is being executed. This therefore requires the Integration Server and the application system to communicate with each other. This is achieved by using an adapter, which can be accessed by using the mapping 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 as well 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-up
Functions with multi ple results
 – Better flexibility in defining your mapping scenarios
 
XML Payload Validation
XML Payload Validation
Forward/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 Adapter 
Engine. 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 the
Integration Engine. If the validation fails, the message processing will be stopped in the
monitoring. An administrator can decide depending on the severity of the validation failure
whether the message should be processed. He can correct the message payload or he can
 
Mass Changes via Integration Directory API
Integration Directory API
 Application Programming Interface (API) al lows to access, edit, act ivate objects
in Integration Directory
Examples: Communication channels, business systems, receiver 
determination, interface determination, change li sts
 API Access via Web Serv ice
WSDL files are stored in Enterprise Services Repository as external definitions
 API al lows to create, update, delete, read, search etc. objects in Integration
Directory
 API is part icularly suitable to perform mass changes
Content of Integration Directory can be read by API in order to use this input for 
defining own views, statistics etc.
Objects of Integration Directory can be accessed, e. g. communication channels, business systems, receiver  determination, 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 Integration Directory 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-consuming manual procedure. You can realize the following possible applications:
- If you have newly installed SAP NetWeaver Process Integration and would like to fill the Integration Directory with your existing configuration data then you can import the available configuration data using 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 object concerned accordingly. You can do this for multiple configuration objects by using the programming interface.
 –  Individually Presenting the Contents of the Integration Directory
 
1. Introduction: B2B Integration
3. Connect Your Process Out-of-the-Box
1. Introduction: Business Value
1. Introduction: B2B Integration
3. Connect Your Process Out-of-the-Box
1. Introduction: Business Value
Supporting Standards to Improve Processes
Industries involved in Industry
Chemical Companies CIDXTM Customer 
 Appli cation
SAP Business Packages – Example
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
Backend
CRM
SCM
ERP
 A business process consists of a set of steps that, when executed, accomplish a
certain business goal.
For instance, a customer issues a request for a product from a supplier by sending a
purchase order containing the descriptions of the items to be purchased. The supplier 
checks for the availability of the items in its inventory before accepting or rejecting the
customer's purchase of the specific items. These steps constitute a purchase order 
business process.
To the customer in the purchasing scenario, some business process steps are neither 
visible nor particularly relevant. For instance, checking the availability of the items in
the supplier's inventory is one such step that is particularly relevant to the supplier but
not visible to the customer. Similarly business process steps on the customer side are
neither visible nor relevant.
Public business processes consist of steps that are visible to both parties conducting
the business, whereas private business processes consist of steps that are visible
only to one party.
iWay Adapter 
e.g. Siebel
business value
for 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 adapter 
afterwards.
 – Separate installation step are required, but these are fully integrated into SAP Service Marketplace processes
 – 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 
 
Ready-to-Run Integration Scenarios
Partner Content A2A/B2B
Enhance Package A 
   P   a   c
Content from SAP
Content from SAP
Content 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
SAP Business Packages (Integration Content focussing on vertical industry standards e.g. RosettaNet; CIDX, S95, …) BENEFITS
 – Enable seamless B2B communication
 – … based on Industry Standards
Content from SAP Partners
Many partners are providing integration content that extends the content offering of SAP (for A2A / B2B scenarios)
Certified integration scenarios
 
Ready-to-Run Integration Scenarios
SAP Content Catalog*
from Partners
Check out the PI content catalog. It contains content offerings from SAP as well as from certified
Connectivity Info on SAP Service Marketplace
SAP Service Marketplace: http://service.sap.com/xi
SAP XI in Detail Connectivity Connectivity SAP NW 7.0 / ‘04
Partner Eco System
SAP relies on a system of partners to provide solutions for other 
applications and certain industry standards
Together with these partner solutions SAP NetWeaver Process Integration
posit ions c learly as complete B2B gateway
Connectivi ty Reseller Agreements w ith
Seeburger AG
iWay Software
Technical support for partner solutions via the
SAP Support Portal, 24x7
Certification Programs for Process Integration
* http://www.sdn.sap.com   Partners and ISVs  
 
1. Introduction: B2B Integration
3. Connect Your Process Out-of-the-Box
1. Introduction: Business Value
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:
Who are RosettaNet members?
Sony, TSMC, UMC, SMIC
Nokia, STM
SAP, 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 is one 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 are pushing the standards very hard.
RosettaNet standards form a common e-business language, aligning processes between supply chains on a global basis.
RosettaNet standards offer a robust nonproprietary solution, encompassing data dictionaries, implementation framework, and XML based message schemas and process specifications, for  e-business standardization. These standards are free to the public on the RosettaNet web page.
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 networks separated geographically.
RosettaNet has achieved tremendous adoption of its standards in the high-tech manufacturing
supply chain over the past three years.
 
Main Components of RosettaNet Standards…
PIPs (Partner Interface Processes)
Public processes between business partners, linking each private process into a business transaction
PIP defines
Roles for Trading Partners
The Business Process is defined in terms of Business Activi ty
Example: Create Purchase Order 
Business Action message
Business Signal message
One-action
Two-action
RosettaNet PIPs or Partner Interface Processes are XML based dialogs that define business
processes 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 a
business nature.
Business signals are positive and negative acknowledgment messages that are sent in response to
business 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 latter 
returning a business signal.
 A two-action activity involves the initiator sending a request action to the responder, and the
responder returning a receipt acknowledgment to the initiator. This is followed by the responder 
returning a response action to the initiator, and the initiator returning a receipt acknowledgement to
the responder.
One-action and two-action activities can also use either one or both of the synchronous and
 
Industry Standard Adapters – RNIF Adapter 
Pack and unpack RosettaNet messages
Structural verification of the message
headers
Uses the Collaboration Partner 
exchanges
applications
Integration
Server 
Enterprise
Services
Repository
 Adapter 
Engine
 Adapter 
Framework
The RNIF Adapter is used for sending messages between the Integration Server and your 
partner system by transforming the XI message format into RosettaNet PIP message format
and so on.
The RNIF Adapter executes the transport, packaging and routing of all PIP messages and
business signals based on the relevant information retrieved from the Enterprise Services
Repository and Integration Directory at runtime
The RNIF Adapter is part of the Adapter Framework. The inbound RNIF Adapter is located
before the Integration Engine pipeline, and calls this pipeline while the outbound RNIF Adapter 
is called by the pipeline.
 
Business Package for RosettaNet
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 addresses
RosettaNet standards – not just tools.
Dedicated, prebuilt, out-of-the-box message and process mappings between the application
interfaces and business logic of various SAP solutions and RosettaNet PIP payloads are delivered
with the Business Package.
SAP delivers Technical Adapters like RNIF Adapter, Mapping & Business Processes plus the
Business 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 Repository
Example
Mappings PIP standard
RosettaNet PIPs
RosettaNet PIPs - Out of the Box
 
Reduces time to hook up with new Business Partners
Pre-Defined Configuration
Configuration Templates
Model Configurator 
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 
Specific settings for B2B configuration
This speeds up the process to set-up new BP-connections
 
SAP NW PI
Partner 
RosettaNet Partner Interface Process 3A4:
Buyer sends a purchase order request action to PI via RNIF adapter. The RNIF Adapter 
transforms the message protocol into a message protocol that is understood by the PI and
sends the message to the Integration Server for further processing.
PI receives the message and sends a receipt acknowledgement via the RNIF Adapter to the
Buyer.
PI transforms the PIP3A4 RosettaNet Standard message to the SAP message (IDOC
ORDERS05) and sends the message to the backend R/3 system via the IDoc adapter for 
further processing.
Backend R/3 processes the IDoc and creates a Sales Order in the system and send the Order 
confirmation message (ORDERSP IDOC) back to the waiting PI process.
PI transforms the received confirmation IDoc to the PIP3A4 Purchase Order Confirmation
message format.
The RNIF Adapter accepts the message from the Integration Server, transforms the message
protocol from PI to PIP message protocol, and sends the message to the RosettaNet-compliant
system.
 
1. Introduction: B2B Integration
3. Connect Your Process Out-of-the-Box
1. RosettaNet
SAP TechEd ‘06
Package –Process In Detail
Service Marketplace
Define SLD-objects
repository
https://service.sap.com/ibc --> Industry Solutions --> SAP for Chemicals   Order to Invoice
SAP help portal
http://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.
Definition of process flows +
CIDX Business Package – Repository Objects
External Definit ions
Configuring Business Package
Process In Detail
CIDX security standards (non-repudiation, …)
 
1. Introduction: B2B Integration
3. Connect Your Process Out-of-the-Box
1. Introduction: Business Value
PIDX Content in Enterprise Services
Repository
Configuration Using the Model Configurator 
Generate Configuration
Transfer scenario
from repository
1. Introduction: B2B Integration
3. Connect Your Process Out-of-the-Box
1. Introduction: Business Value
Electronic Data Interchange
 Agreed message standards
Minimum of human intervention.
History o f EDI
Several industries invented their own sets of standardized data formats including TDCC – 1960
 ANSI ASC X12 – 1979
UN/EDIFACT – 1985
Other EDI standards
SAP NetWeaver EDI Adapter: Architecture
Industry
Standard
Protocol
SAP CRM, SRM, SCM SAP Indust ry So lu tion
Integration Server  ES Repository
• Message descriptions
      S     e     c     u     r
      i      t    y
Seeburger’s B2B and Industry-specific content in the Enterprise Services Repository includes:
 – Mappings, message descriptions, adapter metadata, partner master data, integration scenarios and processes.
 – Seeburger EDI and B2B technology suite in the Adapter framework includes conversion, communication and components.
 
 
Example: Configuration of an
Example: EDIFACT->XML-EDIFACT
Adapters by Seeburger for Process Integration
Technical EDI Adapters  AS2 (EDIINT/HTTP(S)); Pro toco l: AS2
OFTP; Protocol: OFTP/ISDN, OFTP/TCPIP
VAN Access; Protocol: P7 / X.400, VAN FTP
Business EDI Adapters Generic EDI; Pro tocol: OFTP/ISDN or P7 / X.400, VAN FTP
EDI Converter: ANSI X.12, EDIFACT Various Mapping Templates: PO, Order confirmation, …
Payment (Financial Service Providers); Protocol: OFTP/ISDN, P7, VAN FTP EDI Converter : EDIFACT, SWIFT various Mapping Templates: Payment orders, Debit advice …
Industry Specific EDI Adapters  Aerospace and Defen se
 Automot ive
High-Tech
Paper 
Pharmaceutical
Retail
 
Adapters by iWay Software
i2   Lawson   Microsoft CRM
Manugistics   Oracle Applications   Peoplesoft
Industry Standard Adapters
Swift   Transora   UCCnet
COM+/DCOM   Corba   Lotus Notes
Tibco Rendezvous
Mainframe/transaction Adapters
Telnet (5250)   Tuxedo
 
SAP Conversion Agent by Informatica
Seamlessly integrated into PI
Bi-directional conversion of unstructured and semi st ructured data from / to XML
Transformation on message payload
Protocol support via SAP’s technical adapter (PI adapter framework)
Transformations integrated via PI AF module
SAP Java EE 5
PI Adapter Framework A 
Lib
The Conversion Agent delivery includes Adapter Framework modules that enable the usage of 
Conversion Agent transformations based on all (java based) SAP technical adapters in PI
Conversion Agent transformations are used for payload transformations; the adapters take care of 
the protocol layer.
Supported Data Formats by Informatica
(Partial List)
… 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 Agent
enables bi-directional transformation from/to these formats
 
1. Introduction: B2B Integration
3. Connect Your Process Out-of-the-Box
1. Introduction: Business Value
SAP NetWeaver Process Integration 7.1 - B2B 62
SAP’s Approach to SOA for More Flexibility Enterprise SOA Enriches SOA with Business Content to Ensure Integrity
Enterprise SOA enriches industry-standard service-oriented architectures
with productized services as well as business semantics in a unified
repository to ensure business process integrity for enterprises and
deliver advanced business process flexibility.
It increases scalability, reusability, and governance in SOA-based
architectures to reduce TCO, enhance responsiveness, and
accelerate business process change and innovation.

Introducing Enterprise Services Bundles Make the Value of Enterprise SOA “Consumption Ready”
Deliver high-impact business capability
Provide “quick wins” for the business
Enterprise Services: Highly integrated Web services combined with business logic and semantics that can be accessed and used repeatedly to support a particular business process
Enterprise Services Bundles:
SAP’s Enterprise Services Workplace:
https://www.sdn.sap.com/irj/sdn/esworkplace
Group-relevant enterprise services for a specific business scenario
Cross-industry bundles
Industry-specific bundles
Governance for Enterprise Services
Semantics/Taxonomy Global Data Types
Architectural Guidelines and Standards
Semantic building blocks for interfaces
Business semantics consistency: same understanding between service consumers and service providers
Technical (Transport protocols, security standards, formats …)
Enterprise Services Repository
The enterprise services
Bundles of Enterprise Services
Order to Cash
Bank Relationship Management
External Cash Desk
Hire to Retire
Benefits and Compensation (Duet)
Integration of Quality Management 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.
 
Logistics Execution Inventory Lookup
Handling of Business Events
Customer Collaboration for the Supply Chain
Supply Network and Production Planning Processes
Transportation Collaboration and Subcontracting
Management of Tag IDs and Tag Observations
Bundles of Enterprise Services Year-end shipments 2007 – PREVIEW*
PLANNED RELEASE
Warehouse Mgmt System
Supply Chain Operations and Execution in Oil and Gas
Order to Cash Order to Cash v2 (incl. B2B)
Quote to Order for Configuration Products
Fin. SSC – Interco. Processing
Reserve and Commit Budget Multi-Channel Tax and Revenue
Management
* Disclaimer: As the roll-in for the winter edition is not completely finalized, the list of enterprise service bundles shown here is subject to change by SAP without prior notice. Not all scenarios and industries are listed here.
Service for Customer  Customer Service Execution v2
Procure to Pay Document Builder 
Procure to Pay (incl. B2B)
Outsourced Manufacturing
Enterprise Asset Mgmt  Asset Configuration v2
Maintenance Processing v2
HCM Time Management
HCM Org Management
HCM Learning Solution
Insurance Billing and Payment
Insurance Extension Claims Investigation
Planning Int.
Chargeback Management
POS Integration
Trade Price–Specific Contract
Medical Documentation and Coding
Medication and Materials Management
Compliance Relevant Data Exchange –  eLogbook (Defense)
Information Integr. Systems (GIS) (Defense)
Environment, Health, and Safety (EH&S) Services
Integration of Learning Management Systems
Subscription Management (Media)
Year-End Shipments 2007
1. Introduction: B2B Integration
3. Connect Your Process Out-of-the-Box
4. Summary
Why use SAP NetWeaver Process Integration
7.1?
Reasons for using SAP NW PI 7.1 as B2B Gateway
Use Process Integration as the SOA backbone for all integration needs
Establish SAP NetWeaver Process Integration as SOA middleware with central design, configuration, monitoring, alerting
Leverage pre-configured solutions that are based on open standards and provide business
processes, mappings etc.
Utilize same skill set for all integration requirements
Benefits
SAP NetWeaver Process Integration 7.1 - B2B 69
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, 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 or  registered 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 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.