salesforce for brady
Post on 23-Jan-2015
943 Views
Preview:
DESCRIPTION
TRANSCRIPT
Put Your ERP Data to Work! Salesforce Best Practices for ERP Integration Success
Track: IT Executives
ERP Integration Challenge
DataRedundancy
Business ProcessFragmentation
Era
RDBMS
ERP Partners
SaaS
80s80s 90s90s 2000s2000s
Legacy RDBMSLegacy
ERP Partners
RDBMSLegacy
25+ Years of Assets Proliferation
Rigid Applications by design
Not all are service enabled
Too much data to share with field
Three Steps to Integration Success
Focus on New Metrics
Define the Process
Define Integration
Layers
Choose Approach
•Subscription Pricing
•Project Timeline
•Additional Endpoints
•TCO
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
The Process has 3 Parts: Data, Tasks, and Timing
TimingSynchronous vs.
Non Synchronous
InvoicesProductsOrdersCredit
QuotesPricingShippingAccounts
Data
Tasks
TransformationValidate DataMass UpdatesData CleansingCustom Logic
Alerts and Workflow
Account
FI
CustomerMaster
New Account
Invoice
New Customer
Changed Customer
Product
Price Books
Opportunity
New Item
Changed Item
New Pricelist
Changed Pricelist
Opportunity to Order
Tra
nsa
ctio
n H
isto
ry
Closed / Open Invoices
PaymentsPayments / Payment History
Order Status / Order History
LO
Order
Price Lists
MaterialMaster
Your Data Model
Your business logic(in C, Java, Apex + workflows, rules, etc)
Data Layer
Application Logic
User Interface
Security
Screens exposed to the end users
What Layers Need to be Integrated?
4
Over 80 Certified Solutions
Low Complexity
Medium Complexity
High Complexity
Composite Apps/SOA• Enterprise Mash-ups• Rich user interface
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
Packaged Integration OptionsIntegration and Data Management Category on the AppExchange
4
Low Complexity
Medium Complexity
High Complexity
Composite Apps/SOA• Enterprise Mash-ups• Rich user interface
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
Integration Moves to the CloudSaaS Integration Solutions
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
Luke Leonhard Integration Lead
BradyBrady is an international is an international manufacturer of complete manufacturer of complete solutions that solutions that IdentifyIdentify & & ProtectProtect PeoplePeople, , ProductsProducts, , & & PremisesPremises
About Brady Corporation
BradyBrady is an is an SAPSAP shop shop using using SalesforceSalesforce. .
Why Integrate in Phase 1?
360° Customer View
Automate Manual
Processes
Reduce Costs
Achieve Better Data
Phase 1 ValuePhase 1 Value
Integration Project Constraints
Time
ResourcesNew TechnologiesNew Technologies for Brady
Tailored integration options…
…based on business requirements.
Integration Overview
FI
Account
Updated SAP Customer
Product
Opportunity
Tra
nsac
tion
His
tory
Order Status
LO
Order
Ordered Products
Quality Notifications
Credit Status
ApplianceOr
Custom Web Service
Ordered Products
Quality Notifications
Credit Status
New Account (Prospect)
Customer Master
Literature Request Contact
Lead
Literature Request
Splash Page
1
2
4
6
7
QuotesQuotes
4
5
3
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
• Existing customers:
• Real-time updates of SAP customer information that exists in Salesforce
Approach • New customers:
• Trigger the creation of a new Customer in SAP once the Opportunity’s stage is >= 50%
• Existing customers:
• SAP triggers a change to Salesforce information through the Web Service API
Technologies UsedSalesforce Outbound Messaging w/ Apex CodeIBM Enterprise Service BusSAP / SAP XI
Technologies UsedSalesforce Outbound Messaging w/ Apex CodeIBM Enterprise Service BusSAP / SAP XI
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 UsedSalesforce Custom Buttons / LinksLotus DominoVisual ForceSAP Web Services / XI
Technologies UsedSalesforce Custom Buttons / LinksLotus DominoVisual ForceSAP Web Services / XI
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 UsedSalesforce Custom ObjectsIBM Enterprise Service BusSAP / SAP XI
Technologies UsedSalesforce Custom ObjectsIBM Enterprise Service BusSAP / SAP XI
The Future?
Data Improvement
Mobile Reach
Support Integration
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
Integration in Action:
Literature Requests
Integration in Action:
Literature Requests
Questions?Questions?Contact Contact Luke, or use the Community!, or use the Community!
http://community.salesforce.com
top related