NetSuite Integration Series: Part 2: Keep data in Sync between Oracle CX Sales (Engagement Cloud) and NetSuite by Naveen Nahata

Introduction:

The purpose of this post is to introduce readers to the realtime integration between Oracle CX Sales (formerly Engagement Cloud or Sales Cloud) and NetSuite.

We explore how to keep customers in sync between Oracle CX Sales and NetSuite when CX Sales is the source of truth. We will build this integration using Oracle Integration Cloud (OIC), which is an offering that helps customers build and orchestrate complex integrations between various systems.

The same principal can be applied to objects other than the Customer and to certain objects in Oracle ERP Cloud which support Business Events – triggers which notify OIC whenever an object is changed (Created, Updated, Deleted)

One of the challenge in syncing data between the two systems is that each system has it’s own primary identifier and mapping the two requires some way to store cross-reference – which ID in System 1 maps to which ID in System 2

We will explore how this problem can be solved easily in NetSuite using a concept called External ID.

Main Article:

We will build 2 integrations:

1. When a customer is created in Oracle CX Sales, it will be created in NetSuite

2. When a customer is updated in Oracle CX Sales, it will be UPSERTed in NetSuite.

An UPSERT operation is an attempt to make an update to a record. If the record does not exist, then it will be created. This scenario can happen if a record gets created in Oracle CX Sales and is not sync’ed to NetSuite. We use the UPSERT operation to ensure subsequent updates to that record propagate to NetSuite. Read the complete article here.

PaaS Partner Community

For regular information on Oracle PaaS become a member in the PaaS (Integration & Process) Partner Community please register here.

Blog Twitter LinkedIn Facebook Wiki

Technorati Tags: SOA Community,Oracle SOA,Oracle BPM,OPN,Jürgen Kress