Clarity Connect integration
Dynamics 365 Oracle Integration
Sell and serve customers in Dynamics 365 while Oracle Fusion Cloud ERP runs orders and receivables, with orders going one way and billing status the other.
Which Dynamics 365, and which Oracle
Both names cover several products. This page covers the split we see most: Dynamics 365 Sales and Customer Service, which keep their data in Microsoft Dataverse, in front of customers, and Oracle Fusion Cloud ERP, with Order Management and Receivables, behind them.
An order agreed in Dynamics 365 is created once in Oracle. Oracle stays the record for invoices, receipts and credit, and the parts of that record a salesperson or service agent needs are copied back to the Dynamics 365 account.
Dynamics 365
Sales and Customer Service, on Dataverse
- Accounts and contacts
- Opportunities and quotes
- Orders
- Cases
Oracle Fusion Cloud ERP
Order Management and Receivables
- Customer accounts
- Sales orders
- Receivables invoices
- Standard receipts
Dynamics 365 to Oracle Fusion record mapping
A starting map using Dataverse table names on the left. Discovery confirms the Oracle setup and the fields.
| Dynamics 365 | Oracle Fusion Cloud ERP | Direction |
|---|---|---|
| Account (account) | Customer account | Dynamics 365 to Oracle |
| Contact (contact) | Customer contact | Dynamics 365 to Oracle |
| Order (salesorder) and its products | Sales order and order lines | Dynamics 365 to Oracle |
| Fields on the order | Order status and shipment | Oracle to Dynamics 365 |
| Invoice (invoice) or fields on the account | Receivables invoice | Oracle to Dynamics 365 |
| Paid status on the invoice | Standard receipt | Oracle to Dynamics 365 |
How the front and back office stay in step
Dynamics 365 orders into Order Management
A Dataverse webhook can fire when an order is created or reaches the status you pick. Connect maps it and creates the order through Oracle's Sales Orders for Order Hub REST resource, which keys each order by its source system and source order ID, so every Dynamics 365 order traces to exactly one Oracle order.
Invoices and receipts back to the account
Oracle Receivables holds the invoices and the standard receipts applied to them. On a schedule, Connect reads both and writes invoice numbers, amounts, due dates and paid status to the Dynamics 365 order or account, so an agent can answer a billing question without an Oracle login.
Customers created in one place
Discovery decides which system creates customers. A common rule is that Dynamics 365 creates the account, Oracle creates the customer account and billing address when the first order arrives, and the Oracle customer number is stored on the Dynamics 365 account for every order after that.
See Clarity Connect move an order
Watch an online order travel into the ERP and its status come back in our Clarity Connect demo, or book a live walkthrough on your own systems.
How each side is reached
Dynamics 365 Sales and Customer Service are read and written through the Dataverse Web API, an OData v4 REST interface. Dataverse webhooks can send a record's create or update event to an outside service, synchronously or asynchronously.
Oracle Fusion Cloud ERP publishes REST resources for sales orders, receivables invoices and standard receipts, plus file-based data import (FBDI) for bulk loads such as AutoInvoice. For Order Management, Oracle says to use the REST API or FBDI rather than its older Import Sales Orders web service, so that is what a new connection should use.
How Clarity Connect runs it
Clarity Connect is Clarity's integration platform. Both systems here are cloud services, so Connect runs cloud to cloud with access limited to what each task needs, keeps a persistent two-way connection and runs each flow in real time or on a schedule. When either side is unavailable, the job waits in a retry queue and nothing in transit is lost. Recorded demos are in Clarity's video playlist.
Discovery
A Clarity business analyst documents the data fields and workflows each system can share and which ones you need.
Tasks and mapping
Each flow becomes a Connect task, such as orders to the ERP or stock to the store, set to run in real time or on a schedule.
Testing
Orders and updates are run end to end, including the return trip of statuses back to the customer-facing system.
Live, with a dashboard
Queues and scheduled tasks show in Connect's Hangfire dashboard. A job whose target is offline is retried 10 times, every 30 minutes, and can be re-queued once the cause is fixed.
Clarity Connect is sold as a SaaS subscription at $599 a month or as a one-time license at $15,000 with no ongoing fees, and larger projects are priced to scope. See pricing.
Questions
We run Dynamics 365 Finance and need accounts receivable payments. Is this the page?
Not quite. This page pairs Dynamics 365's sales apps with Oracle's ERP. If Dynamics 365 Finance is your ERP and you want card and ACH payments posted to receivables, see Payment Hub for Dynamics 365 Finance, which posts them as customer payment journals.
Does it work with Oracle E-Business Suite?
Yes. EBS is usually on-premises, so Connect is installed beside it behind your firewall. Clarity's Oracle eCommerce page covers its work with EBS.
Can orders reach Oracle in real time?
Yes. A Dataverse webhook hands the order to Connect as it is saved, and Connect creates it in Order Management straight away. Invoice and receipt updates going back usually run on a schedule.
How much does Clarity Connect cost?
It is $599 a month as SaaS or a $15,000 one-time license with no ongoing fees, and larger projects are priced to scope. See pricing.
Related resources
Connect Dynamics 365 and Oracle
Tell us which Dynamics 365 apps and which Oracle ERP you run, and where customers and orders start. A Clarity business analyst will document the records and rules with your team as the first step.
Book a demo