FBDI File Based Data Import Process

FBDI File Based Data Import Process

File-Based Data Import (FBDI) is a process used in Oracle Cloud applications to facilitate bulk data upload from external systems or legacy applications. It’s a key tool for data migration and ongoing data integration. Here’s an overview of the FBDI process:

Step-by-Step FBDI Process

1. Download the FBDI Template:
1. Obtain the specific FBDI template for the Oracle Cloud application module you need (e.g., General Ledger, Accounts Payable) from the Oracle Cloud application.
2. Prepare the Data:
1. Fill in the required data in the template. This typically involves multiple sheets including a header and lines.
2. Ensure data accuracy and adherence to the required format, especially for dates and numeric fields.
3. Generate the CSV File:
1. Convert the filled-in template into a CSV file. Some templates come with macros to assist in this conversion.
4. Zip the CSV File:
1. Compress the CSV file(s) into a ZIP file. If the process requires multiple CSV files, they all need to be zipped together.
5. Upload the ZIP File:
1. Use the File Import and Export utility in Oracle Cloud to upload the ZIP file to the Oracle Universal Content Management (UCM) server.
6. Run the Import Process:
1. Navigate to the specific data import program for your module (e.g., ‘Import Payables Invoices’).
2. Submit the import job, ensuring to reference the correct file in UCM.
7. Monitor the Import Process:
1. Track the progress of the import job through the Scheduled Processes screen.
2. Once complete, review the process log and output for any errors or warnings.
8. Error Handling:
1. In case of errors, download the error report from Oracle Cloud.
2. Correct the errors in the original data file and repeat the process from the step where the CSV is generated.
9. Post-Import Review:
1. After a successful import, verify the data in the Oracle Cloud application to ensure accuracy and completeness.
10. Documentation and Record Keeping:
1. Document the process details, including any issues encountered and how they were resolved.