Hide Notes 

Slide 1: Put Your ERP Data to Work! Salesforce Best Practices for ERP Integration Success Track: IT Executives
Slide 2: ERP Integration Challenge Data Redundancy Business Process Fragmentation SaaS ERP Partners ERP Partners Legacy RDBMS Legacy RDBMS Legacy RDBMS 80s 90s Era 25+ Years of Assets Proliferation 2000s    Rigid Applications by design Not all are service enabled Too much data to share with field
Slide 3: Three Steps to Integration Success Define the Process Define Integration Layers User Interface Application Logic Choose Approach Focus on New Metrics Data Layer •Subscription Pricing Data Tasks Timing Presentation Application Logic Data Packaged or Build •Project Timeline •Additional Endpoints •TCO “Salesforce can integrate seamlessly with our SAP back office and scale to multiple time zones, geographies, and currencies.“
Slide 4: The Process has 3 Parts: Data, Tasks, and Timing Data New Account Account New Customer Changed Customer Closed / Open Invoices FI Customer Master Invoice Invoices Products Orders Credit Quotes Pricing Shipping Accounts Payments / Payment History Transaction History Payments Tasks Transformation Validate Data Mass Updates Data Cleansing Custom Logic Alerts and Workflow LO Price Books New Pricelist Changed Pricelist Price Lists Opportunity Opportunity to Order Order Order Status / Order History New Item Product Changed Item Material Master Timing Synchronous vs. Non Synchronous
Slide 5: What Layers Need to be Integrated? Security User Interface Screens exposed to the end users Application Logic Your business logic (in C, Java, Apex + workflows, rules, etc) Data Layer Your Data Model
Slide 6: Packaged Integration Options Low Complexity Composite Apps/SOA • Enterprise Mash-ups • Rich user interface 4 Integration and Data Management Category on the AppExchange Medium Complexity High Complexity Application Integration • Real-time integration • Multi-step integration • Human workflow Data Integration • Data migration • Data replication • Bulk Data Transfers Data Cleansing • Data deduplication • Data assessment Over 80 Certified Solutions
Slide 7: Integration Moves to the Cloud SaaS Integration Solutions Low Complexity Composite Apps/SOA • Enterprise Mash-ups • Rich user interface 4 Medium Complexity High Complexity Application Integration • Real-time integration • Multi-step integration • Human workflow Data Integration • Data migration • Data replication • Bulk Data Transfers Data Cleansing • Data deduplication • Data assessment
Slide 8: What If I Want to Build It? The Two Core Types of Integration Design Mechanisms Synchronous Asynchronous SFDC Integration Mechanisms:  Composite Application / Mashup  Salesforce SOA  Apex Custom Web Services SFDC Integration Mechanisms:  Inbound Replication To Salesforce  Outbound Replication From Salesforce  Outbound Messaging  Salesforce Network
Slide 9: Luke Leonhard Integration Lead
Slide 10: About Brady Corporation Brady is an international manufacturer of complete solutions that Identify & Protect People, Products, & Premises Brady is an SAP shop using Salesforce.
Slide 11: Why Integrate in Phase 1? Phase 1 Value  360° Customer View  Automate Manual Processes  Reduce Costs  Achieve Better Data
Slide 12: Integration Project Constraints Time Resources New Technologies for Brady
Slide 13: Tailored integration options… …based on business requirements.
Slide 14: Integration Overview 1 FI New Account (Prospect) Customer Master Updated SAP Customer 2 Contact Transaction History 7 Literature Request Lead s t atu er S Ord cts r odu r ed P Or de Account Literature Request LO Order 3 Ordered Products Sp l ash Opportunity Pa g e Quotes Qual it Notif y icatio ns 4 4 Quotes Product Appliance Or Custom Web Service Cre d it S ta 5 tus Quality Notifications 6 Credit Status
Slide 15: New Customer & Customer Synchronization Requirements • New customers: • • • • Created in salesforce on a daily basis (Converted Leads, New Accounts) Once an opportunity reaches a certain stage, the customer needs to be created in SAP Real-time updates of SAP customer information that exists in Salesforce Existing customers: Approach • • New customers: • • Trigger the creation of a new Customer in SAP once the Opportunity’s stage is >= 50% SAP triggers a change to Salesforce information through the Web Service API Existing customers: Technologies Used Salesforce Outbound Messaging w/ Apex Code IBM Enterprise Service Bus SAP / SAP XI
Slide 16: SAP 360° View of Customer Orders Requirements • To allow the Sales team 24/7 access to relevant SAP order information without making a phone call. Approach • Leverage existing web platform (Lotus Domino) to cache relevant information, and provide a relevant mashup for Salesforce. Technologies Used Salesforce Custom Buttons / Links Lotus Domino Visual Force SAP Web Services / XI
Slide 17: Literature Request Orders Requirements • The Sales team can send customers / prospects catalogs or product samples. Approach • • Sales team can “order” literature items from within Salesforce. On a scheduled basis, these orders are sent to SAP in a batch process. Technologies Used Salesforce Custom Objects IBM Enterprise Service Bus SAP / SAP XI
Slide 19: The Future? Data Improvement Mobile Reach Support Integration
Slide 20: Lessons Learned  Analyze each integration’s requirements – Need for Real-time, Data Exchanges, Data Presentation  Test integration points with good and bad data.  Leverage web-service middleware
Slide 21: Integration in Action: Literature Requests
Slide 22: Integration in Action: Literature Requests
Slide 23: Questions? Contact Luke, or use the Community! http://community.salesforce.com