Step Ahead focuses on step-by-step data Integration of Salesforce.com with other applications data like E-Business Suite, D&B SAP & NetSuite etc. using various tool kits like Informatica, Oracle Data Integrator, Apatar and Apex Data loader etc.
Five Essential Steps are:
1.) Explore your integration goals:
Is there a centralized customer maintenance team that can create customers when requested by a salesperson?
How is the customer data created? Does it come from external sources (events, Campaigns) as leads?
How large is the data and how many customers are being created?
How fluid is the customer data? Are changes made frequently? To what entities?
How long is your sales cycle? Can the salesreps wait for a reasonable time before the customer data is present in Salesforce.com?
What kind of customer model is used? Is Oracle Trading Community Architecture implemented and leveraged?
Does the Organization have any address validation tools in place like DNB, Vertex on Oracle and SFDC? If there are validation tools on only of the systems, then this will be good candidate for being the Master.
2.) Provide connection to data sources:
To start reading and writing data, you need to establish connections to the sources. In other words, you need to gain access to data tables, data structures, data types, and data records. This is where data integration actually begins.
3.) Map Data sources together:
Integration tools will allow the map between the Salesforce.com and other applications data
4.) Match the fields:
You need to set the rules for data transformations.
Why is the mapping so critical?
You need to point where the source of data is and where the target is.
Sometimes you need to transform source table formats to SalesForce.com table formats. For instance, you have Time or Binary objects at the source and need to save them as text at the target.
5.) Run the transformation job:
Finally, run the transformation, and let your SalesForce.com accounts be populated.
Customer Data Integration with Oracle
Oracle e-Business Suite customers are either increasingly considering using salesforce.com or are currently using this application for sales force automation. The opportunities and challenges when using two disparate applications that do not integrate out-of-the-box are discussed. Integration with the corresponding implementation considerations on both Saleforce.com and Oracle e-Business Suite:
EBS Customer Information:
Salesforce Customer Account
Customer integration is the most challenging of integrations which requires a detailed business process analysis.
The first step is to determine if the integration has to be unidirectional or bi-directional. Unidirectional interface mandates data in one system as the master and the other as slave. In a unidirectional interface, customer data is created in the master application and the updates in the master cascades down to the slave. In a bi-directional interface data can be updated in either system and will cascade to the other.
Most customers use unidirectional customer interface as bi-directional interfaces are rather difficult to develop and maintain and also causes conflicts when various users update the same data.
Bring E-Business Case Management & Sales Orders, Helpzilla, Business & IT project related tickets
Service Contracts & Entitlement
Partner Revenue Compliance
My Learn Data
Enterprise Territory Management