Salesforce For Brady


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Salesforce For Brady

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