Solution Design Document
SCM: Stock Transfer from SFDC_FSL to Oracle Fusion Cloud (Inbound)
Document ID: SCM: Stock Transfer from SFDC_FSL to Cloud
Document Author:
Issue Date:
Version Number:
Change Record
|
Date |
Author |
Version |
Change Reference |
|
|
|
|
|
|
11-Sep-2023 |
Anoop Kumar |
1.0 |
Initial Document |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Reviewers
|
Name |
Position |
|
|
Capgemini Tech Manager |
|
|
Capgemini Integration Lead |
|
|
Videojet IT Lead |
|
|
|
|
|
|
For Information
|
Name |
Position |
|
|
Videojet SCM Lead |
|
|
Videojet Solution Architect |
|
|
Videojet Enterprise Architect |
|
|
|
|
|
|
Reference
Documents
|
Document Name |
Description |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
SCM : Stock
Transfer from SFDC To Cloud (Inbound)
Business
Rules & Extraction Logic
Integration
Process Description
Data
Mapping between Oracle Cloud & SFDC
High Level
technical Architecture
Future
Process Flow (From SFDC to Oracle Cloud)
Logic to
upload data into Oracle Cloud (Inbound)
Error data
flow and monitoring
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.
Related Documents
This section
defines related documents for this interface.
|
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. |
|
Business Requirement
A Technician
can create a Transfer Order to transfer Item quantity from one subinventory to
other subinventory. The basic business need is that new transfer order
information created in SFDC (FSL) should be interfaced to Oracle Cloud.
This interface
automates the process of transferring Stock Transfer from SFDC to Oracle Cloud
Source & Target
This section
defines source & target systems and data objects.
|
Task |
Stock Transfer from SFDC To Cloud |
|
Source |
SFDC |
|
Source Object |
Transfer Order |
|
Target |
Oracle Cloud |
|
Target Object |
Inventory and Movement Request Tables |
Source fields
This section
defines source fields from FSL system for inbound interface.
|
S.No |
Source Fields (SFDC) |
Description |
|
1 |
Subsidary |
Subsidary |
|
2 |
Item Number |
Item
Number |
|
3 |
Serial No. |
Serial
No. |
|
4 |
From Technical Id |
From
Technical Id |
|
5 |
To Technical Id |
To
Technical Id |
|
6 |
Quantity |
Quantity |
|
7 |
Posting
Date |
Posting
Date |
|
8 |
Transfer
Status |
Transfer
Status |
|
9 |
Creation
Date |
Creation
Date |
|
10 |
Creation
Time |
Creation
Time |
|
11 |
Error
Code |
Error
Code |
|
12 |
Quantity
Posted |
Quantity
Posted |
|
13 |
Transaction
Id |
Transaction
Id |
Business Rules & Extraction Logic
The
Business Rules for this integration:
·
All the Stock Transfer Order created in SFDC are
transferd to Oracle Cloud.
·
The interface will pick up all the Stock Transfer record
from SFDC system.
·
This process should run on pre-defined
intervals (at least 15 minutes) or on-demand through a batch interface.
·
This interface created new Stock Transfer Order in
Oracle cloud.
<Data extraction Rules>[SS1] [SS2] [SS3]
Business Process
The business
process for this integration:
·
A Technician can create a Transfer Order to
transfer Item quantity from one subinventory to another sub inventory.
·
This transfer has to be synced to Oracle
Cloud environment.
Pre-requisites
The
pre-requisites for this integration:
·
All the Inventory Configuration
completed from Functional Team in Oracle Cloud.
Configuration Data
The Following
configuration data will be required.
·
All the Inventory Configuration
completed from Functional Team in Oracle Cloud.
Integration Process Description
The Flow diagram
illustrates the Interface from FSL to Oracle system.
Current Integration Process between FSL
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
<Mapping sheet to be attached>[SS1]
Technical Design
This
Specification documents the detailed design for integration between Oracle
Cloud and SFDC. This integration will load New Stock Transfer 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 |
|
FSL |
Oracle Cloud |
1.0 |
Future Process Flow (From SFDC to Oracle Cloud)
The Diagram represents the process flow for
integration from SFDC to Oracle Cloud via OICS.
<OIC Flow diagram to be updated>
Detailed Workflow
Detailed Description of the workflow:
<Will be updated based on the Integration Design Diagram>
|
Steps |
Detailed Description[SS6] |
|
|
|
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 Name :
Staging Table :
Custom Program Name & Logic : < TBD the Integration Name as per naming
Convention >
Note: REST
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 Fusion.
2. Technical users or Support personnels can go and check the Issue in
the OICS Monitoring.
Resubmission
Process
1. Retry/Resubmit is not required in this Outbound as the Interface is
scheduled for every 15 mins and will be fetching the From_Datetime from DB only
from the last successful run of the Interface.
2. In Case of any Errors, the Technical Support users can rectify the
issues with Data or systems if any to make sure the next run after 15 mins
should not fail with the same Error.
Test Cases
<UTP XL Sheet to be
attached as per the Test Cases decided for this Interface>[SS7]
Open Issues & Closed Issue
|
ID |
Open Issue |
Resolution |
Responsibility |
Target Date |
Impact Date |
|
|
|
|
|
|
|
|
1 |
|
|
|
|
|
|
2 |
|
|
|
|
|
|
3 |
|
|
|
|
|
|
4 |
|
|
|
|
|
|
5 |
|
|
|
|
|
|
ID |
Closed Issue |
Resolution |
Responsibility |
Target Date |
Impact Date |
|
|
|
|
|
|
|
|
1 |
|
|
|
|
|
|
2 |
|
|
|
|
|
|
3 |
|
|
|
|
|
|
4 |
|
|
|
|
|
|
5 |
|
|
|
|
|
Comments
Post a Comment