Oracle Fusion FBDI Load Time Estimator
Cutover plans fail on load times that were guessed. This estimator turns your record count, observed throughput and expected rejections into a duration you can put in the runbook.
Your numbers
Total rows across the object, such as items or on-hand balances.
Rows you place in each file. Choose a size that respects the file limits for your template.
Take this from a mock load of the same object, not from a guess.
Upload, scheduling, waiting and checking per file.
Share of rows rejected at validation on the first pass.
Analysis and correction time before the reload.
Your results
Throughput depends on object, environment, scheduled process load and your data. Use results from mock loads, and treat this as a planning estimate.
Load duration vs records
Sweeps Records to load from 10000 to 1000000, holding your other inputs fixed.
Want help reducing load rejections?
Optional expert review of your extract and cleansing approach before mock loads.
Optional. The tool and every export work without this. No spam.
How to use it
Enter the number of records for one object, the rows per file you plan to use, and the throughput you saw in a mock load. Add the overhead per file for uploading, submitting scheduled processes and checking results. Set the rejected row percentage and the time your team needs to analyse and correct errors. The primary output is total hours, which belongs in the cutover plan.
The formula
Files equal rows divided by rows per file, rounded up. Initial processing is rows divided by throughput. Overhead is files times overhead per file. Rejected rows are rows times the error percentage, and the reload adds correction time plus rejected rows divided by throughput plus one more file overhead. Total time is the sum, converted to hours. It assumes loads run in sequence.
Reading the chart
The chart sweeps record count and shows how total duration grows. It is roughly linear, but the rounding of files adds steps. Use it to decide whether to split a large object across parallel streams, or to move static data, like item master, to an earlier preload before the freeze.
- Preload static data before cutover
- Parallelise only independent objects
- Honour dependency order
- Re-measure throughput each mock load
Common mistakes
Using throughput from a small sample, ignoring downstream steps such as accounting or planning refresh that depend on loaded data, and assuming errors drop to zero on the second pass. Add a contingency to the result and compare estimates with actuals after every mock cycle.
Frequently Asked Questions
What is FBDI?
File Based Data Import is the Oracle Fusion method for bulk loading data from spreadsheet templates that are zipped as CSV files, uploaded and processed by scheduled processes into interface tables and then the application tables.
Can loads run in parallel?
Independent objects can often run in parallel, subject to environment capacity and Oracle limits. Dependent objects must follow order, such as items before structures. Test parallel runs in a mock cycle before trusting them.
Why do loads get slower than estimated?
Common causes are shared environment load, validation of large reference data, errors needing manual correction and extra post load processes. Capture timings per step in the mock cycles and use the slowest realistic case.
How do I choose rows per file?
Check the file size and row guidance for the specific template in Oracle documentation, then pick a size that balances manageable error analysis with fewer files. Smaller files make errors easier to isolate but add overhead.
If you want help profiling and cleansing source data to cut rejection rates before the first mock load, we can review the extract with you.
Related Tools
Oracle Fusion Data Migration Mapping Worksheet
Map legacy fields to Oracle Fusion objects and attributes, record the transform rule, and see how many records survive cleansing.
OracleOracle Fusion Cutover Plan Worksheet
Plan a go-live weekend task by task, with start offsets, durations, owners and a calculated end hour for each step.
OracleOracle Fusion Cloud SCM Fit Gap Worksheet
Log each requirement, classify it as standard, configuration, extension or gap, and total the effort and cost before the design workshops end.
OracleOracle Fusion SCM Implementation Statement of Work Template
A generic statement of work outline for an Oracle Fusion SCM implementation with scope, phases, assumptions, responsibilities and acceptance.
More Oracle tools
See all- Oracle Fusion FBDI Template Field Guide
- Oracle Fusion Item Class Design Worksheet
- Oracle Fusion Supply Planning Checklist
- Oracle Fusion BI Publisher Report Specification Template
- Oracle Fusion Quarterly Update Test Checklist
- Oracle Fusion Role Provisioning Worksheet
- Oracle Fusion Inventory Organization Design Worksheet
- Oracle Fusion SCM UAT Test Script Template
- Oracle Fusion Min-Max and Safety Stock Calculator