3 MIN READ

Improving sales team productivity by integrating Oracle EBS and Salesforce.

A salesperson is effective only to the extent of knowledge they have about the product or service that they are selling. Even the most "blue chip" CRM systems do not effectively provide the internal product or services information required by the sales person at that time. Typically, the information related to customer, sales order, availability, etc. resides within the internal ERP systems, which limits access to the increasingly mobile salesforce. Having the ability to access information on-the-go in real-time expedites the sales process and enables the sales person to make more effective sales.

Don’t have time? Read it later:

Client Snapshot

  • Manufacturer of physical infrastructure for Data Center, Enterprise, and Industrial environments
  • 5,000+ employees
  • $1+ billion (USD) annual revenue
  • Location: Chicago, IL

Project Overview

A manufacturer needed to integrate Salesforce CRM to its Oracle E-Business Suite ERP system. Using MuleSoft Anypoint Studio, ennVee would build the integration and a framework to allow each salesperson to optimize sales via Salesforce, and access required information from a central repository (the ERP system). In this case, Oracle EBS is the back-end system for business transactions.

  • Use MuleSoft as the integration engine to build a solution that creates customer details (customer and site details) and sales orders in Oracle EBS based on the opportunity created in Salesforce.
  • Send an acknowledgement back to Salesforce by updating the sales order number against the designated opportunity.
  • Deploy the MuleSoft solution exclusively to Cloud.

Solution Components

Oracle EBS to Salesforce Integration Process

  1. MuleSoft integrations assist in updating an item from Oracle EBS to SFDC as a product that a salesperson can see and plan to sell.
  2. When a salesperson selects a product in SFDC, this event triggers an action in Oracle EBS to bring the availability information back to SFDC.
  3. The salesperson can proceed to creating an opportunity based on availability. The system will allow an opportunity to be created if the available quantity is equal to or greater than the requested quantity. Alternatively, if there is no availability or less availability, SFDC will throw up a warning but allow the opportunity to be created.
  4. Based on the opportunity details, MuleSoft will check if the customer pre-exists in Oracle EBS for the associated account in SFDC. If the customer does not exist in EBS, MuleSoft creates the customer details and associated Bill-To and Ship-To details (sites) by calling standard APIs. Subsequently, MuleSoft creates the sales order in Oracle EBS for the customer.
  5. Later, MuleSoft sends back the information to SFDC regarding the generated sales order for the particular opportunity.
  6. MuleSoft throws up an exception if it cannot connect to either SFDC or Oracle EBS after a set number of tries.

Read the full white paper here:


Subscribe to updates