PMC213 Reduce SAP NetWeaver PIs Mapping and Integration Efforts Significantly
Next Generation Solution
Gunther Stuhec, OCTO Mark Crawford, OCTO Petko Ivanov, SAP Research Dresden October 2010
Disclaimer
This presentation outlines our general product direction and should not be relied on in making a purchase decision. This presentation is not subject to your license agreement or any other agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to develop or release any functionality mentioned in this presentation. This presentation and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP intentionally or grossly negligent.
2010 SAP AG. All rights reserved. / Page 2
Agenda
1. The Problem with B2B Integration 2. Current and Future SAP Solutions Demo I Map and Transformation Script Generation Demo Next Generation Mapping Demo Collaborative Mapping in SAP StreamWork Demo Context Based Object Modifications Demo PI Map and Transformation Script Generation 3. Roadmaps 4. Discussion
2010 SAP AG. All rights reserved. / Page 3
Traditional B2B Integration
Complex, Time Consuming & Costly
Business beyond boundaries is a growing focus
82% need electronic data interchange 34 % of data originates from outside the enterprise (e.g., from customers, suppliers, 3PLs, etc.). 56% consolidate multiple disparate B2B gateways on to a common integrated platform 47% expanded the scope of their B2B efforts (e.g. new transactions or trading partners)
Integration In Practice
20-37 Days to Enable a Single Partner $15,000 Internal Cost per Partner Interface 90% experienced delays with ERP projects due to B2B integration issues 57% experienced a production outage due to lack of B2B connectivity 65% performed inadequate testing of B2B prior to new ERP launches 37% said B2B integration staff were supporting ERP related projects
Integration Issues
82% need to reduce integration costs Point to Point Mappings Constant Business Changes Regional Process Regulations Time & Material Projects
2010 SAP AG. All rights reserved. / Page 4
Major Factor 1 Methodology Complexities
Purchase Order
DataArea BuyerCustomerParty PurchaseOrder OrderHeader Party
fromRole Order Create Body PartnerRoleDescription (./GlobalPartnerRoleClassificationCode=BY)
PurchaseOrderHeader IDOC SG1 CLO N1 (./N1/98=BY) SG2 (./NAD/3035=BY) BuyerParty Buyer PartnerDescription Order Create Partners
Type Systems
OAGIS UBL xCBL SAP GDT Tradacomms ODETTE ASC ANSI X.12 UN/EDIFACT IDoc PapiNet CIDX RosettaNet Location BuyerParty PostalAddress PurchaseHeader OrderParty
PurchaseOrder
BuyerParty
PhysicalLocation BDT BuyerParty Address CADD NameAddress Partner Information N4 NAD E1EDKA1 (./PARVW=AG)
NameAddress Country PhysicalAddress Country Address Information PhysicalAddress Address
Every Standard Interface has different type systems and different graphs from root to leafs
2010 SAP AG. All rights reserved. / Page 5
Country Code
Major Factor 2 Data Element and Definition Inconsistency
Type System OAGIS Name Buyer Party Definition The entity that is responsible for Buying the document or element in which it is associated. Additionally, the contact may be a person or a group or department. An association to the Buyer. A BuyerParty is a party that buys goods or services. Contains the information for the party purchasing the goods. Customer's location A mandatory, repeatable segment which gives details of the buyer. A coded or uncoded name and address must be included. ./N1 - "To identify a party by type of organization, name, and code ./N1/98 - "Code identifying an organizational entity, a physical location, property or an individual" ./N1/98=BY - "Buying Party (Purchaser)" A group of segments identifying the parties with associated information. ./NAD - "A segment identifying names and addresses of the parties, in coded or clear form, and their functions relevant to the order. Identification of the seller and buyer parties is mandatory for the order message. It is recommended that where possible only the coded form of the party ID should be specified e.g. The Buyer and Seller are known to each other, thus only the coded ID is required, but the Consignee or Delivery address may vary and would have to be clearly specified, preferably in structured format." ./NAD/3035 - "Code giving specific meaning to a party." ./NAD/3035=BY - "Party to which merchandise or services are sold." The segment includes the address of the business partner. The individual roles of the business partners and their addresses are qualified in field "PARVW". ./PARVW - "Partner function (e.g. sold-to party, ship-to party, ...)" ./PARVW=BY - "Sold-to party" PapiNet Buyer Party The legal entity to which the product is sold. Also commonly referred to as the sold to party or customer. If no OtherParty is defined as the Payer, the Buyer is the Payer. Purchasing party or role in a transaction. If the purchasing party is not the owning party then the owning party will be the "SoldTo" partner.
UBL SAP GDT xCBL Tradacomms ODETTE ASC ANSI X.12
Buyer Customer Party Buyer Party Buyer Party CLO - Customer's Location BDT - Buyer Details N1 - Segment group (./N1/98=BY - Buyer)
UN/EDIFACT
SG2 - Segment Group (./NAD/3035=BY - Buyer)
IDoc
E1EDKA1 - Partner information (./PARVW=BY - Buyer)
CIDX RosettaNet
Buyer
PartnerRoleDescription The collection of business properties that describe a business partners' role in a partner interface process. (./GlobalPartnerRole ./GlobalPartnerRoleClassificationCode - "Code identifying a party's role in the supply chain." ClassificationCode= Buyer) ./GlobalPartnerRoleClassificationCode=Buyer - "An employee or organization that buys products for a partner type in the supply chain."
2010 SAP AG. All rights reserved. / Page 6
Major Factor 3 Object Class Equivalency Issues
OAGIS UBL xCBL SAP GDT
Purchase Order Request
Tradacomms
ODETTE
ASC ANSI X.12
850
UN/ EDIFACT
ORDERS
IDoc
PapiNet
Purchase Order
CIDX
RosettaNet
Pip3A4Purchase OrderRequest
PurchaseOrder
Order
Order
ORDERS
ORDERR
ORDERS05
OrderCreate
Possible matches for Purchase Order
DataArea Order Create Body BuyerCustomer Party OrderHeader PurchaseOrder Purchase OrderHeader fromRole
PurchaseOrder CLO Possible matches for Header Party PurchaseHeader OrderParty BuyerParty SG1 N1 (./N1/98=BY) SG2 (./NAD/3035 =BY) IDOC Order Create Partners PartnerRoleDescription (./GlobalPartnerRole ClassificationCode=BY)
BuyerParty
Possible matches for Buyer Party
Buyer
PartnerDescription
BuyerParty PostalAddress Possible matches for Location Location BuyerParty Address NameAddress
CADD
BDT
N4
NAD
E1EDKA1 (./PARVW=AG)
Partner Information
PhysicalLocation
Possible matches for Address
Country
NameAddress PhysicalAddress
Country Address Information PhysicalAddress
Address
Possible matches for Country Code Identification Code ISOCountry Code GlobalCountry Code
CountryCode
Country
CountryCode
CADD1
3207
26
3207
LAND1
CountryCode
Identifying possible equivalence classes over different imported schemas based on different type systems is overly complex
2010 SAP AG. All rights reserved. / Page 7
Agenda
1. The Problem with B2B Integration 2. Current and Future SAP Solutions Demo PI Map and Transformation Script Generation Demo Next Generation Mapping Demo Collaborative Mapping in SAP StreamWork Demo Context Based Object Modifications Demo PI Map and Transformation Script Generation 3. Roadmaps 4. Discussion
2010 SAP AG. All rights reserved. / Page 8
Demo DEMO
PI Map and Transformation Script Generation
Finding Interface Objects In Enterprise Service Repository (ESR)
Over 2000 Interface Objects (message types) are available to select from
You scroll until you find the object you believe to be appropriate You click on the object to select it and expand to a detailed view
2010 SAP AG. All rights reserved. / Page 10
Interface Object Detail
The selected interface object appears with expanded detail
All possible elements appear, independent of any customization requirements Confirm this is the object you are looking for If it is the object, then you will need to restrict it to meet your requirements
If it is not the object, then you return to the previous step
2010 SAP AG. All rights reserved. / Page 11
Identifying the Appropriate Mapping Object
Following the same process as the source, but identify the Object Type as Mapping Objects Over 2000 Interface Objects (message types) are available to select
You scroll until you find the mapping object you believe to be appropriate You click on the mapping object to select it and expand to a detailed view
2010 SAP AG. All rights reserved. / Page 12
PI Mapping Template
The selected mapping object appears with expanded detail
All possible elements from source and destination appear, independent of any customization requirements Confirm this is the mapping object you are looking for If it is the mapping object, then you will need to restrict it to meet your requirements
If it is not the mapping object, then you return to the previous step
2010 SAP AG. All rights reserved. / Page 13
Demo
Next Generation Mapping
List of Knowledge Library Messages in Selected Context
2010 SAP AG. All rights reserved. / Page 15
Available Knowledge Library Mappings For Selected Purchase Order Message
2010 SAP AG. All rights reserved. / Page 16
Upload a Further Message Schema that should be Mapped
2010 SAP AG. All rights reserved. / Page 17
Automatic Recognition of Schema Type and Library Name
2010 SAP AG. All rights reserved. / Page 18
Show Automatic Mapping Result
2010 SAP AG. All rights reserved. / Page 19
Mapping Added to Knowledge Library
2010 SAP AG. All rights reserved. / Page 20
Demo
Collaborative Mapping in SAP StreamWork
Collaborative Mapping in SAP StreamWork
Having uploaded the input schema we can now collaboratively edit the proposed mapping within SAP StreamWork. This helps us to synchronize the definition of, as well as the confirmation or rejection of proposed mappings with partners or other experts within the company.
2010 SAP AG. All rights reserved. / Page 22
Collaborative Mapping in SAP StreamWork
Automatically proposed mappings are visualized using both tabular (upper part) and tree (lower part) views. The tree view shows the structural and textual information coming from the schema as well as the mappings specified as lines between matching elements. The tabular view, on the other side, shows the degree of similarity between a pair of matching elements and enables the user to confirm a selected mapping. The yellow colored mappings are mappings proposed by the system
2010 SAP AG. All rights reserved. / Page 23
Collaborative Mapping in SAP StreamWork
Confirmation of a certain mapping by the domain expert changes the similarity confidence as indicated in the similarity progress bar (here the demonstrator confirms the Product.Requested_Net. Price mapping pair) The color of a confirmed mapping changes to green A domain expert is the user of the system that performs/edits the mapping
2010 SAP AG. All rights reserved. / Page 24
Collaborative Mapping in SAP StreamWork
The domain expert could also reject proposed mappings by simply cutting the line in the tree view. The mapping is automatically removed from the tabular view afterwards.
2010 SAP AG. All rights reserved. / Page 25
Collaborative Mapping in SAP StreamWork
The domain expert could easily define new mappings within the tree view by performing drag and drop.
2010 SAP AG. All rights reserved. / Page 26
Collaborative Mapping in SAP StreamWork
User defined mappings are also displayed in the tabular view. They appear directly after the drag and drop operation. User defined mappings are displayed in green color and are automatically confirmed.
2010 SAP AG. All rights reserved. / Page 27
Collaborative Mapping in SAP StreamWork
After defining all mappings, the domain expert can now save the mapping and the results are propagated to the system. The business partner is now ready to communicate/exchange information with all other partners that have already integrated their schemas.
2010 SAP AG. All rights reserved. / Page 28
Show Mapped Element Details
2010 SAP AG. All rights reserved. / Page 29
Show How Mapped Element will be Expressed in Other Type Systems in Knowledge Library
2010 SAP AG. All rights reserved. / Page 30
Demo
Context Based Object Modifications
Complete Model Before Contextualization
2010 SAP AG. All rights reserved. / Page 32
Modifying Canonical Data Model Context based Messages for Buyer/Germany France
2010 SAP AG. All rights reserved. / Page 33
Show Order Message in Selected Business Context
2010 SAP AG. All rights reserved. / Page 34
Process - Add Element in Given Business Context Using Text Search
2010 SAP AG. All rights reserved. / Page 35
User Describes the Element to be Added
2010 SAP AG. All rights reserved. / Page 36
System Automatically Resolves Acronyms
2010 SAP AG. All rights reserved. / Page 37
System Resolves Synonyms
2010 SAP AG. All rights reserved. / Page 38
System Provides Suggested Element Name
2010 SAP AG. All rights reserved. / Page 39
System Suggests Value Domain Parameters
2010 SAP AG. All rights reserved. / Page 40
System Adds Element to Appropriate Position
Status_ Basic Issue Item. Date
2010 SAP AG. All rights reserved. / Page 41
Demo
Next Generation Transformation and PI Integration
Next Generation XSLT Creation between Selected Source and Target Schema
2010 SAP AG. All rights reserved. / Page 43
XSLT Save
2010 SAP AG. All rights reserved. / Page 44
Import XSLT into ESR for PI Consumption
2010 SAP AG. All rights reserved. / Page 45
XSLT Imported
2010 SAP AG. All rights reserved. / Page 46
Representation of Result in ESR
2010 SAP AG. All rights reserved. / Page 47
Agenda
1. The Problem with B2B Integration 2. Current and Future SAP Solutions Demo PI Map and Transformation Script Generation Demo Next Generation Mapping Demo Collaborative Mapping in SAP StreamWork Demo Context Based Object Modifications Demo PI Map and Transformation Script Generation 3. Roadmaps 4. Discussion
2010 SAP AG. All rights reserved. / Page 48
Planned Innovations for Technology Process Integration
Key Needs
Reduce total
Key Innovation
Simplified configuration Eclipse based System
cost of Development
tools
centric process support SAP Solution
Reduce total
cost of
Enhanced integration with
operations Process Integration
Manager
Alerting, reporting, task
management via of Java stack
SAP Solution Manager
Functional completeness
Further enhancements
Scalability for
high volume use cases
Enhanced B2B On-Demand
integration
PLANNED INNOVATIONS
2010 SAP AG. All rights reserved. / Page 49
Going Forward Next Generation Integration Knowledge Library
>2008
Conceptualization Research Proof of Concept Development Phased Delivery
2008 - 2009
2009 2010
2010 201?
Forthcoming
2010 SAP AG. All rights reserved. / Page 50
Agenda
1. The Problem with B2B Integration 2. Current and Future SAP Solutions Demo PI Map and Transformation Script Generation Demo Next Generation Mapping Demo Collaborative Mapping in SAP StreamWork Demo Context Based Object Modifications Demo PI Map and Transformation Script Generation 3. Roadmaps 4. Discussion
2010 SAP AG. All rights reserved. / Page 51
Further Information
SAP Public Web:
SAP Developer Network (SDN): www.sdn.sap.com SCN - SAP NetWeaver - Process Integration Business Process Expert (BPX) Community: www.bpx.sap.com SAP BusinessObjects Community (BOC): boc.sap.com
Related SAP Education and Certification Opportunities
Process Integration and Business Integration Technology http://www.sap.com/services/education/catalog/netweaver/bit.epx
Related Workshops/Lectures at SAP TechEd 2010
PMC206, A Deep Dive into the Next Generation Process Integration, Lecture PMC207 What's New in SAP NetWeaver Process Integration, Lecture PMC214 B2B Support Today and Roadmap Moving Forward, Lecture
2010 SAP AG. All rights reserved. / Page 52
Further Information
SDN Articles
From EDI to UN/CEFACT: An Evolutionary Path Towards a Next Generation eBusiness Framework, G. Stuhec et. all, 20Sep06 Enabling of Next Generation B2B by Web 3.0 G. Stuhec, 30Sep07 Canonical Formats and Business Data M. Crawford, G. Stuhec, 30Dec08 Using CCTS Modeler Warp 10 Advantages of Collaborative Modeling of Business Information Interfaces G. Stuhec, M. Crawford 20Dec07 Accelerate Your Business Data Modeling and Integration Issues by CCTS Modeler Warp 10 G. Stuhec, M. Crawford, 17Nov07 Using CCTS Modeler Warp 10 to Customize Business Information Interfaces G. Stuhec, 22Nov07 Getting Started with ISO 11179 G. Stuhec, M. Crawford; 26May06
2010 SAP AG. All rights reserved. / Page 53
Further Information
SDN Articles
How to Solve the Business Standards Dilemma The CCTS Standards Stack G. Stuhec, M. Crawford; 07Nov06 Getting Started with UN CEFACT XML NDR for CCTS, G. Stuhec, M. Crawford; 04Aug06 How to Solve the Business Standards Dilemma - The Context Driven Business Exchange, Gunther Stuhec, 01Dec05 How to Solve the Business Standards Dilemma - The CCTS based Core Data Types, Gunther Stuhec, 20 Sep 2006 How to Solve the Business Standards Dilemma - CCTS Key Model Concepts, Gunther Stuhec, 03Mar06
2010 SAP AG. All rights reserved. / Page 54
Contact Feedback
Please complete your session evaluation. Be courteous deposit your trash, and do not take the handouts for the following session.
2010 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, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POW ER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. 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. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer 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 other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. in the United States and in other countries. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence. The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.
2010 SAP AG. All rights reserved. / Page 56
