1. How do I link sales accounts to back-office records to show customer 360 information?
  2. Why do you need to link accounts?

Why do you need to link accounts?

Oracle Fusion Cloud Applications use the party model to manage business entity data. Party is a business relationship agnostic term encompassing individuals, organizations, and households, interacting with the deploying company. Parties can have different roles in relation to the deploying company, such as customer, supplier, or partner.

In Oracle Sales, the sales account of a party is used to conduct front-office transactions as part of the sales process. Transactional items such as opportunities are associated with the sales account of a party.

In Oracle Financials, the customer account of the same party is used to conduct back-office transactions as part of the financial process. Transactional items such as invoices, belong to customer accounts associated with the party.

Thus, we see that using the party model the same business entity is represented by a Sales Account in Oracle Sales but by a Customer Account in Oracle Financials.

Now consider the problem being faced by the fictitious company from our case study, Vision Corp., that has implemented both Enterprise Resource Planning (ERP) and Customer Experience (CX) systems. The company contains different sales and financial party records that pertain to the same entities because the data was loaded from various legacy systems. Therefore, a sales representative of Vision Corp. doesn’t have a complete view of their account and back-office transactions because invoices, subscriptions, and orders aren’t associated with the sales account.

The best solution for this situation is to use linksets to manage the relationships between parties in both ERP and CX. The duplicate identification functionality of customer data management enables Vision Corp. to automatically identify and suggest matching back-office (BO) party records such as orders, invoicing, payments, and revenue recognition, and front office (FO) party records that can be used to create BOFO link sets.

Here's a visual representation of the problem and its resolution:This image depicts the account details scattered across the application before linking them.This image depicts the account details after linking them.