Supplier Conversion from Oracle EBS or any Other On-Premise/Cloud system to Oracle Fusion with FBDI/OIC

Converting supplier data from Oracle E-Business Suite (EBS) or any Other On-Premise/Cloud system to Oracle Fusion Procurement Cloud involves careful planning and execution. Below are high levels design process that we usually implement and execute for Conversion. This is a generic layout of conversion process , you should always consider specific requirements and configurations of your organization while designing conversion process.

Feel free to reach us at inquiry@bizinsightinc.com for any additional information on this Integration

Step#1 - Preparation

1. Analyze data: Analyze your EBS supplier data to identify records for conversion. we usually focus on active suppliers with accurate and complete information. Consider excluding inactive or incomplete records to avoid data issues in Fusion.

2. Map data fields: Create field mapping between EBS and Fusion. Ensure field names and data formats align to avoid mapping errors during import. 

3. Data cleansing: Cleanse your EBS supplier data. Address inconsistencies, duplicates, and missing values ( this is a golden opportunity to get rid of duplicate data as well as supplier consolidation before we start using Oracle Fusion). Oracle has tools like Data Quality to ensure data integrity.

4. Choose conversion method: Select the appropriate conversion method based on your volume and complexity of data , and then work with Business/IT to load the data as per required Fusion templates. We usually use below 2 options :

• File-based Data Import (FBDI): Suitable for moderate-sized datasets requiring manual file generation and upload.

• Oracle Integration Cloud (OIC): Handles complex integrations and high-volume data transfers, majority of time we create OIC orchestration flow to do complex validation and mapping and then call FBDI jobs to load data in Oracle Fusion

Step#2 -Conversion

1. Extract data: Extract the supplier data from EBS or any source system based on your requirement ( for example you might be interested in converting Active Supplier). While extracting the data we usually take care of couple of things 

1. Make sure that you have all the elements that are required for FBDI template for Supplier.

2. If some of required data elements are not available in source system/EBS then make note of that and we might beed to add those 

1. either manually in FBDI template 

2. Or if we are planning to use integration tool like OIC then we derived these missing values in OIC

2. Transform data (optional): Depending on your data mapping setup, perform any necessary data transformations during extraction or as a separate step ( Manual updates in FBDI or Transformation in OIC flow) .

   At the end of this Step you have data ready for Supplier /Site/Address/Site Assignment/Contact as per respective FBDI Template ( if you are planning to load manually ) or But if we are calling the Load jobs from OIC then OIC will create FBDI file and call the Load ESS Jobs.

3. Load data: 

1. for manual Import ,Run the FBDI jobs for 

1. Import Supplier 

2. Import Addresses

3. Import Site

4. Import Site Assignments

5. Import Contacts

6. Import Supplier Business classification

7. Import Supplier Attachment ( If any)

2. For loading data with FBDI +OIC then execute following Steps

1. Set up SaaS + File datapters+DB connection in OIC.

2. Create OIC orchestration for 3.1.1/3.1.2/3.1.3/3.1.4/3.1.5/3.1.6/3.1.7.Most of time we create Scheduled Orchestration for Supplier conversions and Run one OIC job at a time , in above sequence. Also Mark the errors records. 

3. One of advantage of doing OIC jobs is , in case there is requirements to load supplier on regular basis from external system  then we can convert these Scheduled orchestration into App based orchestration and use same integrations for real time Supplier load.

4. I am working on a separate blog with Technical details especially for OIC flow. 

4. Validate data: Validate the imported data for accuracy and completeness. Leverage Fusion's validation tools and review error logs to identify and address any inconsistencies.

Step#3 - Post-conversion:

1. Reconciliation: Reconcile the migrated data with your original EBS supplier records. Ensure all critical information is transferred correctly and reflects the latest updates.

2. Testing: Test supplier functionalities in Fusion, verify supplier profiles, address creation, purchase order workflows, and other key activities.