Customer Integration from SFDC to Oracle fusion through OICS SCM: Account Integration SFDC to Oracle Fusion Cloud (Inbound)

Solution Design Document

SCM: Account Integration SFDC to Oracle Fusion Cloud (Inbound)

Document ID:

Document Control

Change Record

Date	Author	Version	Change Reference

11-Sep-2023		1.0	Initial Document
17-Oct-2023		2.0	Updated Integration Technical Flow diagram/details, Error Handling and Notification Process, and more queries in Open and Closed Issues tracker

Reviewers

Name	Position

For Information

Name	Position

Reference Documents

Document Name	Description

Contents

Document Control................................................................................................................ ii

Introduction........................................................................................................................... 1

Related Documents.............................................................................................................. 1

SCM : Account Integration from SFDC to Oracle Fusion Cloud ( Create or Update ).................................................................................................................................. 2

Business Requirement......................................................................................................... 2

Source & Target..................................................................................................................... 2

Source fields........................................................................................................................... 2

Business Rules & Extraction Logic.................................................................................... 3

Business Process................................................................................................................... 3

Pre-requisites......................................................................................................................... 5

Configuration Data............................................................................................................... 6

Integration Process Description......................................................................................... 6

Data Mapping between Oracle Cloud & SFDC............................................................. 7

Technical Design................................................................................................................... 7

High Level technical Architecture.................................................................................... 7

Future Process Flow (From SFDC to Oracle Cloud)..................................................... 7

Logic to upload data into Oracle Cloud (Inbound)....................................................... 8

Error Handling...................................................................................................................... 9

Resubmit Process.................................................................................................................. 9

Error Notification Alerts..................................................................................................... 9

Test Cases............................................................................................................................... 9

Open Issues & Closed Issue............................................................................................. 10

Introduction

The purpose of this document is to provide information about inbound & outbound Integrations between SFDC and Oracle Cloud. This document explains the functional requirements and provides technical solution for integrations.

This Interface design document defines the key mapping, rules, and logic that is needed to build integration and the process flows required for integrating the data between SFDC and Oracle Cloud.

SCM : Account Integration from SFDC to Oracle Fusion Cloud (Create or Update)

Business Requirement

A sales executive creates a new customer header and/or site(Bill To and Ship To) information in Salesforce.

The basic business need is that new customer header and/or site (Bill To and Ship To) information created in SFDC should be interfaced to Oracle Cloud by creating customer header and/or site (Bill To and Ship To) information in Oracle Cloud.

For New Customer header and Site (Bill To and Ship To) created in SF, data will be interfaced to create new customer header and Site(Bill To and Ship To) into Oracle Cloud.

For Existing Customer header and New Site (Bill To and/or Ship To) created in SF, data will be interfaced to find the existing customer header then create new Site (Bill To and/or Ship To) under the found existing customer header.

Source & Target

This section defines source & target systems and data objects.

Task	West_EU_Account_From_SFDC_To_Oracle_Cloud_Int
Source	SFDC
Source Object	Account
Target	Oracle Cloud
Target Object	Customer Tables

Source fields

This section defines source fields from SFDC system for inbound interface.

S.No	Source Fields (SFDC)	Description
1	SFDC_ID__c	Unique Id created for every customer record in SFDC system
2	Name	Customer Name
3	Type	Customer Type
4	Billing_Street	Customer Bill To Street
5	BillingCity	Customer Bill To City
6	BillingState	Customer Bill To State
7	BillingPostalCode	Customer Bill To Zip Code
8	BillingCountry	Customer Bill To Country
9	ShippingStreet	Customer Ship To Street
10	ShippingCity	Customer Ship To City
11	ShippingState	Customer Ship To State
12	ShippingPostalCode	Customer ShipTo Zip Code
13	ShippingCountry	Customer Ship To Country
14	Phone	Customer Phone No
15	Website	Customer website – URL
16	OwnerId	Salesperson_Code (SFDC_id : Unique Id created for every Salesperson record in SFDC system)
17	CurrencyIsoCode	Currency Code
18	Subsidiary__c	Business Unit , example ‘VTI Italy’
19	Parent_Account_Name__c	Corporate Account

Business Rules & Extraction Logic

The Business Rules for this integration:

· Only new customer records that have not been interfaced to Oracle Cloud will qualify to be interfaced.

· The interface will pick up a new customer record from SFDC system based on the following selection criteria.

Batch Process criteria in SFDC ‘Account‘ object fields:

1. ‘Create_Customer_in_Oracle__c’ is checked.

2. ‘Ship to site number’ is blank/Null.

3. ‘Update Date’ is greater than (>) last run date of the OICS Job.

· This process should run on pre-defined intervals (at least 15 minutes) or on-demand through a batch interface.

· This interface updates an existing customer record in Oracle cloud based on the following conditions.

· A new Ship to address is being created for an existing customer record in SFDC.

· A new Bill to address is being created for an existing customer record in SFDC.

Validation & Pseudo logic: Refer business process flow diagrams given in Business Process section for field validations and Pseudo logic.

Business Process

See below Business Process Flow diagram for details and link to the miro board:

(1) New Customer Creation Process

(2) Process to update an existing customer for a new ship to address and/or a new bill to address.

Customer Verification Process

Next Integration : Customer Update Outbound.

Pre-requisites

The pre-requisites for this integration:

· Salesperson conversion is completed, or Salesperson record is created in Oracle Cloud.

· Customer header record is already created in Oracle Cloud for the case a new customer site (Ship To and/or Bill To) need to be created in Oracle cloud.

Configuration Data

The Following configuration data will be required.

· Define of DFF at Ship to site level of customer in Oracle Cloud

1. Attribute 1: SFDC_id of SF Account (Customer Ship to Site)

2. Attribute 2 : SalesPerson Name

· Define DFF at employee header level to store salesperson data in case salesperson role is assigned to employee.

1. Attribute 1: SFDC_id of SalesPerson.

Integration Process Description

The Flow diagram illustrates the Interface from SFDC to Oracle system. Diagram highlights the basic flow for understanding different stages. The flow outlines the process of new customer creation.

Current Integration Process between SFDC and Navision

Future Integration Process between SFDC and Oracle Cloud

Data Mapping between Oracle Cloud & SFDC

Please see attached excel for Data mapping between Oracle Cloud & SFDC.

Technical Design

This Specification documents the detailed design for integration between Oracle Cloud and SFDC. This integration will load New Customer information Data from SFDC env to Oracle cloud using OICS integration.

High Level technical Architecture

This section describes the high-level technical architecture of the integrations and details the steps in the integration flow.

Integration Name	Source	Target	Version
West EU Account From SFDC To Oracle Cloud Int	SFDC	Oracle Cloud	1.0.0
West EU Account From Oracle Cloud Callback Int	Oracle Cloud	SFDC	1.0.0

Future Process Flow (From SFDC to Oracle Cloud)

The Diagram represents the process flow for integration from SFDC to Oracle Cloud via OICS.

Detailed Description of the workflow:

Steps	Detailed Description
1	OICS Integration for Customer Create or Update Inbound will be scheduled every 15 mins on daily basis for continuous load.
2	Call SFDC to fetch create customer data based on the below parameters: a. Create_Customer_in_Oracle__c = ‘true’ b. Ship to site number = blank/Null. c. Last Update Datetime > last Successful run datetime of the OICS Integration.
3	Update the ATP Stage table with the latest data.
4	Check if SFDC ID already exists in the XREF table. a. If does not exist, then goto Step 5. b. If exists, then go to step 12a
5	Check if Party Name already exists in the XREF table. a. If Party Name exists, then goto Step 6. b. If Party Name does not exist, then goto Step 10
6	Fetch the Party header details from the XREF table.
7	Check if the Ship to address already exists in XREF table. a. If Ship to address exists, then goto Step 12a. b. If Ship to address does not exist, then goto Step 8.
8	Check if the Bill to address already exists in XREF table. a. If Bill to address exists, then, create only Ship to Update request for the party. b. If Bill to address does not exists, then, create both Ship to and Bill to Update request for the party.
9	Call Fusion webservice for Location updates and go to step 12b.
10	Create the FBDI Files for New Customer create in Fusion.
11	Call the FBDI Bulk Load process and go to step 12b
12	Call Common notification process with the process details casewise as below: a. Send an email with duplicate details for enquiry. b. Send an email with Success scenarios

Logic to upload data into Oracle Cloud (Inbound)

This section describes the logic to upload data into Oracle cloud as per new approach using OICS.

FBDI Template : UploadCustomersTemplate.xlsm

ATP Staging Table : VJ_CUSTOMER_SFDC_STG

ATP XREF Table : VJ_CUST_ADD_FUSION_XREF

Custom Program Name & Logic : “Load Interface File for Import” with “Import Trading Community Data in Bulk” for Customer Create/Update in Fusion

Note: REST ERP Cloud Connection will be used to consume FBDI file into oracle Fusion.

Error Handling

In case of any Technical Errors in OICS process, it will be handled as below:

Error Logging Process

1. The Errors will get logged into the Error Table in ATP for future references and can be kept in ATP on need basis otherwise can be purged after an agreed upon 30-60-90 days accordingly.

Error Notification Alerts

1. Notification to the technical Support Team will be sent with the Error details including any corrective measures that can be taken to rectify the particular Error.

Error data flow and monitoring

1. Integration will halt the data processing to avoid any faulty data going into SFDC.

2. Technical users or Support personnels can go and check the Issue in the OICS Monitoring.

ID	Open Issue	Resolution	Responsibility	Target Date	Impact Date

1	Parent_Account_Name__c field from SFDC : Where will it be stored in Oracle Cloud system ? Oracle Cloud does not have any field in Customer record.	Customer Ship To Site Record DFF Attribute7?[SS2]
2	SalesPerson Name field from SFDC: We are not fetching the SalesPerson Name from SFDC. Do we need the Sales Person Name to be stored in a DFF field? If yes, then we will have to update the Source Fields section as well as decide on some DFF field to use for this purpose as Attribute1 and Attribute2 are already going to be used for other purposes.

ID	Closed Issue	Resolution	Responsibility	Target Date	Impact Date

1	Customer Type field from SFDC: What should be the value of Customr type ? Oacle cloud accepts either “Organization” of “Person”.	Organization
2	OwnerId (SFDC_id of saleperson) : SFDC_id will be stored in attribute2 of DFF at primary ship to site level. The requirement is to display salesperson name at primary ship to site level of customer record in Oracle Cloud front end screen. SFDC_id should be stored in Oracle cloud DB.

No.	Document Title	Description	Location
1	Integration Strategy	This document provides the design overview and integration patterns used for the integrations needed for the first phase of the Videojet project.

Erpzen

Search This Blog