Sap salesforce integration
Upcoming SlideShare
Loading in...5

Sap salesforce integration






Total Views
Slideshare-icon Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment
  • Salesforce has successfully enable several other customers reaching similar and better throughput. The key to improving throughput once all other standard optimizations have been done (HTTP keep-alive, gzip compression, etc.) is parallel processing of several partitions of the data set. Using this approach one customer is achieving a throughput of 10M records in 2 hours using an optimally configured ETL tool. Other examples show a throughput per process of ~60-90 inserts/second and the general experience is that you can run up to 3-5 parallel processes without performance degradation. This yields a total throughput of 648,000 – 1,620,000 records per hour.
  • SAP PreSales UK Enablement Workshop December 17th, 2007 One of the important ways that makes Informatica is different from any other data integration software vendor is the range of our partner ecosystem. Here are just some of the companies that comprise our partner ecosystem . It ’ s important to note that because Informatica is singularly focused on data integration , we are able to build strong partnerships with a wide variety of companies. This is because our partners are not threatened by a competing product or technology agenda . Therefore, both Informatica and its partners are focused exclusively on your success with data integration through the use of data services. In turn, Informatica ’ s neutrality benefits you. You can work with the company of your choice —the vendor or service provider that suits your business best and minimizes your risk . Informatica doesn ’ t pigeonhole you into a technology or service provider decision. Regardless of the technology you currently have in your environment, or the service provider you want to work with, you can be confident that Informatica and our software will work with what and whom you want to work. The list of partners on this slide is NOT intended to be exhaustive , but is representative of the kind and caliber of partnerships that can help Informatica customers meaningfully expand their choices (when designing their overall IT architecture) and minimize risks in implementing their very own Data Services architecture.
  • SAP PreSales UK Enablement Workshop December 17th, 2007
  • SAP PreSales UK Enablement Workshop December 17th, 2007
  • SAP PreSales UK Enablement Workshop December 17th, 2007
  • Pre-Packaged Integration Points The first version of the SAPEBS Connector supports Account / Customer Master Synchronization only. The three integration points implemented are: New Account in -> New Customer in SAPEBS New Customer in SAPEBS -> New Account in Changed Customer in SAPEBS -> Update Account in All three integration Points come pre-packaged with the SAPEBS Connector, meaning that the needed Business Logic, Transformations, etc. automatically get deployed when installing the Connector.
  • Apex Connect is a comprehensive family of on technologies built on top of the Apex Web Services API to enable customer integration success. Apex Connect offers five paths to integration success 1. Mash-ups on the AppExchange directory that customers can install with the click of a mouse. Over 230 partners have pre-packaged common integrations to the AppExchange directory. This is a unique integration advantage that only multi-tenant architectures can deliver. Because ISV partners know that every customer is on the exact same version, they are able to essentially shift the integration development burden from the customer to the partner. 2. Native connectors for common ERP applications such as SAPEBS and SAP11i.  These connectors allow our customers to rapidly deploy the most common integration use case for ERP - customer master synchronization. 3. Native connectors for common desktop applications. These connectors support rapid integration to Microsoft Outlook and Lotus Notes for email; and Microsoft Excel and Word for integrating salesforce data with Microsoft Office. 4. An Apex Connect category on AppExchange provides connectors to popular integration middleware platforms. We have worked very closely with over 25 integration middleware vendors to developer connectors that make essentially plug-and-play with these solutions.  Companies like Tibco, Informatica, Cast Iron and Pervasive are providing certified connectors to to accelerate customer development of sophisticated business process integrations. 5. Toolkits for common development environments to support custom integration development. provides toolkits to support popular development environments such as J2EE, and .NET. Customers can create highly custom integrations and leverage their development environment investments and skill-sets.
  • Today, we get most of our revenue from SFA. We see growth across all segments of CRM as we continue to expand functionality. The initial goal for the platform is to make our CRM products easier to sell, easier for customers to achieve success. But, with that said, we see a huge market opportunity in selling non-CRM licenses across multiple departments.

Sap salesforce integration Sap salesforce integration Presentation Transcript

  • Presented by:Narayanan Palani (9)Keshav Trehan (16)Keyur Shah (11)SAP Integration Analysis in E-Business(Cloud Computing)
  • AgendaSalesforce Integration overview Native, Partners, and Apexchange communitySAP Integration overview SAP Netweaver & PI/XIWhat are the integration options? Build vs Buy Partners: SIs/DIsBest PracticesWhere to find more Information? Resources Chatter GroupsE-Business -ERP Integration Analysis 2
  • E-Business -ERP Integration Analysis 3Web Services Integration with SalesforceMiddleware /Developer toolkitsWeb ServiceEndpointCall ExternalWeb ServiceWebServices APIWebServices APIDataservicesWeb ServiceEndpointOutboundMessagingWorkflowWorkflowApexWeb ServicesCustomLogicApexCalloutsApexCalloutsBulk APIBulk APIDataUploadMetadataAPIMetadataAPICustomization& IDEMigration ToolCustom IDEMigration ToolCustom Tools Security Proven technologies Confidentiality and data integrity Interoperability Well adopted, mature standards Simple CRUD interfaces Compatibility Versioning Transparent upgrades Reliability and Scalability 450M+ calls/day Bulk processing, optimizedinfrastructure
  • Support Any Integration ProcessE-Business -ERP Integration Analysis 4Replicate data across systems – Full set up data replicationverbs to access, manage, and exchange all standard andcustom data including polling and peer-to-peer,SOA & Process Automation – Consume external web servicesin real-time. Aggregates and accesses external transactions ordata for use in application process or Visualforce. pagesApplication Lifecycle Management – manage metadatachanges across multiple environments. Works with Eclipse IDEHigh Data Volumes – Upload large amounts ofdata rapidly for migration or replication of 100Ksor millions of records (100K records in 30secs)Move Data With Static & Dynamic Clients – choose ease-of-use and robustness as appropriate Enterprise WSDL for strongtyping. Partner WSDL for loose-typing & dynamic clientsExpose Custom Logic as a Web Service – automatically applycustom logic or aggregate work into single transactional WS callProactively Alert External Systems– use workflow to notifyexternal systems of events in Force.comIn/out ReplicationData LoadBulk LoadChange MetadataOutbound MgsSOA CalloutsCustom ServicesWSAPIWSAPIBULKBULK
  • SAP Integration Benefits ofE-Business Applications: SAP Integration has successfully enable several other customersreaching similar and better throughput.The key to improving throughput once all other standardoptimizations have been done (HTTP keep-alive, gzipcompression, etc.) is parallel processing of several partitions ofthe data set.Using this approach one customer is achieving a throughput of10M records in 2 hours using an optimally configured ETL tool.Other examples show a throughput per process of ~60-90inserts/second and the general experience is that you can run upto 3-5 parallel processes without performance degradation. This yields a total throughput of 648,000 – 1,620,000 recordsper hour.E-Business -ERP Integration Analysis 5
  • Three Steps to Integration SuccessDefine theProcessDefineIntegration LayersChooseApproachDataTasksTimingPackaged orBuildUser InterfaceApplication LogicData
  • Your Data ModelYour business logic(in C, Java, Apex + workflows, rules, etc)SecurityScreens exposed to end usersDefine LayersWhat Layers Need Integration?ApplicationLogicUserInterfaceDataLayerE-Business -ERP Integration Analysis 7
  • E-Business -ERP Integration Analysis 8SAP NetWeaver• SAP Enteprise Portal• SAP Master Data Management• SAP Business Intelligence Warehouse• SAP Exchange Infrastructure (XI)• SAP Mobile Infrastructure• SAP Web Application Server• SAP xApp Resource &Portfolio Management• SAP xApp ProductDefinition• SAP xApp IntegratedExploration and ProductionSAP xApps mySAP Business Suite• mySAP ERP• mySAP CRM• mySAP SCM• Industry-SpecificComponentsSAP Smart Business Solutions• mySAPAll-in-One• SAP BusinessOneSAP for <industry>• SAP for Aerospace& Defense• SAP for Automotive • SAP for Utilities &Customer Care
  • SAP Solutions Definitions SAP Netweaver Is the technical basis of the solutions from mySAP Business Suite and theComposite Applications, the SAP xApps. Is the core of the Enterprise Services Architecture (ESA), SAP’s basic conceptfor Web Services Solutions. mySAP Business Suite (previously known Is a complete package of open enterprise solutions that link all people involved,information, and processes within an organization. It provides components that can be adapted to meet multiple businessrequirements, i.e. mySAP ERP is based on an SAP ECC System with functionsfrom mySAP HR and mySAP Financials. All SAP solutions are based on a complete SAP Netweaver. SAP Smart Business Solutions are SAP Solutions and Packages aimed to SMBs businesses. SAP xApps (Collaborative Cross Applications) Allow to integrate existing applications with each other by accessing existingdatasets and functions via open interfaces. SAP Industry Solutions Provide business functions for selected industries. They are implemented in an SAP R/3 System and are available as Add-Ons.E-Business -ERP Integration Analysis 9
  • DB and OS AbstractionPeople IntegrationProcess IntegrationIntegrationBrokerBusiness ProcessManagementInformation IntegrationBusinessIntelligenceAnalytical AppsPortal CollaborationJ2EE ABAPCore SystemMulti-Channel AccessSAP NetWeaver™SAP NetWeaver™DB and OS AbstractionMaster Data ManagementSAP Netweaver Components OverviewE-Business -ERP Integration Analysis 10SAP Mobile Infras.Close coupling andintegration with SAPbusiness applicationsSAP BI/BW• Close Integration with SAP• Open architecture• Business data in highquantitySAP MDM• Consistent master data handlingSAP XI• Central Management of Interfaces• Connection of any SAP or non-SAPsystems via adaptors and proxiesSAP WAS• Proven, scalable andpowerful platform• Modernization of existingIT Infrastructures andinvestment made
  • SAP Netweaver PI 7.1 Architecture Technical foundation for aService-OrientedArchitecture Enables you to consolidateheterogeneous systems,applications, and data tosimplify the IT environmentand reduce operational costs Tuned for a high-volume,reliable exchange ofinformation acrossdistributed businessapplications Built on open standards,supports process-centriccollaboration among SAP andnon-SAP applicationsE-Business -ERP Integration Analysis 11
  • SAP PI / XI (eXchange Infrastructure)XI JCA Adapters:E-Business -ERP Integration Analysis 12
  • provides many flexible optionsall built on our flexible API and robust web servicesNative ERPConnectorsNativeDesktopConnectorsIntegrationMiddlewareMash-ups fromAppExchangeDeveloperToolkits1 2 3 4XE-Business -ERP Integration Analysis 13
  • E-Business -ERP Integration Analysis 14Three Steps to SAP IntegrationSuccessDefine theProcessDefineIntegration LayersChooseApproachDataTasksTimingPackaged orBuildUser InterfaceApplication LogicData“Salesforce can integrate seamlessly with our SAP back office and scale tomultiple time zones, geographies, and currencies.“
  • Define Process: Common Processes with SAPProcesses have 3 Parts: Data, Tasks, and TimingTimingSynchronous vs.Non SynchronousInvoicesProductsOrdersAssetsCreditQuotesPricingShippingAccountsInstall BaseDataTasksTransformationValidate DataMass UpdatesData CleansingCustom LogicAlerts and Workflow
  • Your Data ModelYour business logic(in C, Java, Apex + workflows, rules, etc)SecurityScreens exposed to end usersDefine Layers: What Layers Need Integration?ApplicationLogicUserInterfaceDataLayerE-Business -ERP Integration Analysis 16
  • E-Business -ERP Integration Analysis 17Materials Data to SFDCCustom Object via APISalesforce AccountData
  • E-Business -ERP Integration Analysis 18Real-time CallOut
  • Integration Pattern 3: Presentation Level IntegrationMashupsE-Business -ERP Integration Analysis 19
  • Choose Approach: 3 Approaches for SAP IntegrationE-Business -ERP Integration Analysis 2021NativeConnectorsIntegrationMiddlewareCustom BuiltIntegrationX
  • NetWeaver (XI/PI) IntegrationR/34.6.xR/34.6.xBABI/RFCIDOCWebServiceABAPProxyRFCAdapterIDocAdapterSOAPAdapterPIAdapterSOAPAdapterWebServicesWebServiceAPIMappingEngineX RefManagementMarketing/Sales/ServiceCloudMarketing/Sales/ServiceCloudWebServicesECC6ECC6ProcessEngineSessionManagement
  • PartnerMagmaAccount and CustomerMaster5 days Cast IronAnalog Devices Products, Orders 8 weeks WebmethodsOxford Press Customers, Products 4 weeks PervasiveTecan Customers, Products 6 weeks MenticorpShell Customer, Products In ProcessZimmerCustomer and Productmaster12 Weeks PervasiveKoneCustomers, Products,Billing16 Weeks SalesforceESRI Order Management 5 days Cast IronEskerCustomer and ProductMaster12 Weeks salesforce.comDestination Process ImplementationCustomerProven Integration Success for SAP
  • SAP Integration Best PracticesWhat to consider before committing to a POCE-Business -ERP Integration Analysis 231. What is the business goal/process?• 360 Degree Customer View (customer master)• Product, Material , and Pricing Management (product master)• Invoices (billing master)• Order Management2. How will the systems communicate?• What are you going to connect to and how? (R3, ERP, BW) (BAPI, IDOC, Web services, DBAccess)• Transformation (SAP XI, Third Party Middleware, Custom Dev, ETL)3. What data should be shared?• Objects: Accounts, Orders, Products, Prices, Inventory, Assets, Invoices, etc• Direction: Read only vs, Bi Directional• Timing: Real-time vs. Batch• Data integrity: Who is the system of record4. How much time and resources are required?• Prebuilt Solutions• Customer References• Domain Expertise
  • Integration Activities of SAPConsultants-An overviewE-Business -ERP Integration Analysis 24Microsoft OfficeWord Document
  • KeypointsIntegrating PI with is done using SOAPAdapters. exposes APIs and provide WSDLs for itsinterfaces.You can integrate PI with by configuringSOAP-Client interfaces in PI using these WSDLs and bydefining routing rules in PI ID using SOAP Adapter.After you import the WSDLs into PI, you can build aninterface by integrating this with other applications.You can use Netweaver Service Orchestration capabilitiesto model, execute and monitor cross SAP-SalesforceprocessesE-Business -ERP Integration Analysis 25
  • SummarySAP Integration is specially helpful for E-Business applicationsIt helps the organization in integrating the business activitiesIt Improves the sales conversions, Real Time Reporting andReduced repeated activitiesE-Business -ERP Integration Analysis 26