Finance Data Conversion Best Practices

• Data Extraction: Use SQL scripts or stored procedures to extract chart of accounts, ledgers,
business units, and subledger data (GL, AP, AR, Fixed Assets) from JDE. Analyze legacy data to
determine the needed scope (e.g. up to cut‑off date) and map each source field to Fusion targets
1 . Capture master data (e.g. account hierarchies, calendars, currencies) first, then transactional

balances. Document all mappings and transformation rules in advance 2 1 .

• Transformation & Mapping: Cleanse and normalize data before loading. For example, reconcile and
merge duplicate suppliers/creditors in the GL/AP data, standardize names/codes, and convert date
and numeric formats to Fusion requirements. Use lookup tables or scripts to translate JDE codes
(e.g. cost centers, project IDs) to new Fusion values. Define cross‑validation rules and account
hierarchies in Fusion to mirror JDE policies. Robust data mapping and cleansing is essential to ensure
accuracy 2 .
• Loading (ETL): Load configuration (setup) data first (chart of accounts, ledgers, calendars, legal
entities, payment terms, etc.), then master and transactional data. Use Fusion’s standard integration
tools: for bulk uploads, leverage File-Based Data Import (FBDI) templates and processes. For
example, populate the provided XLSM templates, click Generate CSV, zip the output, then use the
Load Interface File for Import scheduled process and the corresponding import program to move
data into Fusion 3 4 . Use Oracle ADF Desktop Integration (Excel-based data loader) for additional
loads that benefit from spreadsheets (such as GL budgets or smaller batches of AP/AR data). In all
cases, load parent records before children (e.g. load GL accounts before journal entries).
• Historical Data: Choose an appropriate cut‐off date and load opening balances for that period. For
example, load year‑to‑date or prior‑year GL balances and subledger open transactions. Fusion
provides programs (e.g. Create Opening Balance Journals) to initialize ledgers, and you can use the
Consolidation Workbench or Transfer Balances processes if maintaining a secondary/alternate
ledger 5 . Load only open or relevant historical records; exclude obsolete or closed transactions to
reduce volume.
• Multi-Currency: Configure each primary ledger in its local currency and define any reporting
(consolidation) currencies needed 6 . Load currency conversion data: use Fusion’s FBDI template
Import Historical Rates to load legacy FX rates for each date and rate type 7 . Ensure the default
conversion rate type is assigned to business units or ledger. After loading transactions, run currency
revaluation or translation processes if required. For multiple subsidiaries, consider separate primary
ledgers per currency and use reporting currency ledgers to consolidate results 6 .
• Validation and Reconciliation: After loading, immediately run reconciliation reports. For example,
compare the Fusion GL Trial Balance to the JDE source, and ensure AP/AR balances in Fusion match
legacy totals. Use Fusion’s analytics or seeded reports to verify that transactional counts and sums
are complete. Oracle recommends creating reconciliation reports (e.g. via BI Publisher) to confirm
data integrity before and after each load 8 . Validate key balances by sampling (e.g. one vendor’s
open invoices, one customer’s receivables) and ensure GL subledger postings agree with parent
ledger. Also verify that mandatory fields (like combination segments, tax classifications) meet
compliance rules in the new system.
• Common Issues & Pitfalls: Be very careful with the FBDI/CSV templates: do not delete or reorder
columns in the downloaded templates, as any modification will cause the load to fail 9 . Use UTF‑8
encoding on CSV files to preserve special characters; otherwise, “fuzzy” characters or question marks

1
 will appear in Fusion 10 . Escape any commas or double‑quotes within data fields, since these are
reserved characters in CSV format 9 . Load data in manageable batches so errors can be isolated.
Validate lookup values (e.g. business unit, currency codes) exist in Fusion before loading dependent
records. Finally, remove obsolete or test data (e.g. inactive vendors) from the legacy extract to avoid
cluttering the new system.

Procurement Data Conversion Best Practices

• Data Extraction: Extract vendor master data (suppliers, supplier sites, payees) and related setup
(e.g. payment terms, purchasing categories) from JDE. Also extract open purchase orders,
requisitions, and receipts if carrying forward outstanding commitments. Filter legacy data to only
include active or relevant records. Document how JDE vendor IDs and site numbers will map to
Fusion suppliers and locations 1 .
• Transformation & Mapping: Cleanse and enrich supplier data: merge duplicate suppliers,
standardize addresses, tax IDs and banking information. Map JDE vendor attributes to Fusion
equivalent (e.g. vendor class, assignment rules). Convert any coded values (e.g. payment terms,
procurement categories) to new setup values. Ensure that all required Fusion attributes (like legal
name, DUNS number) are populated. Prepare to load address‑level and site‑level details after the
main supplier record is created.
• Loading (ETL): Use Fusion’s Procurement FBDI templates for bulk loading suppliers and sites.
Populate the Suppliers Import template(s) and follow the standard CSV generation and upload
process 3 4 . Once suppliers are loaded, load any related entities (e.g. procurement contracts,
category assignments). For purchase orders, Fusion may not have an FBDI import for open PO lines,
so consider using ADFdi (Excel spreadsheet import) or Oracle Integration (REST API) for large
volumes of transaction data. Always load master data (suppliers) before transactional data (POs,
receipts).
• Multi-Currency: Verify each supplier’s currency is supported and active in Fusion. Load any specific
foreign currency invoices or commitments using the appropriate currency codes. Ensure exchange
rates (loaded as above) are available for the PO dates. In Fusion setup, confirm that the default
conversion rate type for purchasing is correct. When loading POs in foreign currency, Fusion will
automatically calculate ledger currency amounts using the defined rates.
• Validation and Reconciliation: After loading, validate that the number of suppliers and sites in
Fusion matches the legacy count. Spot-check a sample supplier record for correct address, payment
terms, and currency. If POs were loaded, compare total PO commitments or open amounts in Fusion
to legacy reports. Run the seeded Supplier and PO summary reports to ensure no required field is
missing. Confirm any invoice tolerances or approval routing rules that should apply. As always, use
reconciliation reports or queries to verify that aggregates (e.g. total PO value by vendor) reconcile to
source data.
• Common Issues & Pitfalls: Keep FBDI templates intact – do not delete or move columns 9 . Use
UTF‑8 encoding, especially for supplier names or addresses with special characters 10 . Ensure
vendor number formats meet Fusion’s length limits. Beware of hidden validation: Fusion will reject
suppliers with missing tax/location codes or inactive country names. Schedule large data loads
during off-peak times to avoid performance issues 11 . Lastly, watch out for duplicate vendor
creation: merge legacy duplicates in JDE to avoid creating redundant supplier records in Fusion.

2
Project Management Data Conversion Best
Practices
• Data Extraction: Extract project definitions, task lists, and budgets from JDE. Include project master
attributes (project ID, name, status, start/end dates, project manager), as well as detailed tasks or
WBS elements and planned budgets. Also extract any actual costs (labor, expense, material) up to
cutover if loading historical project transactions. Document how legacy project numbers and
categories map to Fusion project keys.
• Transformation & Mapping: Clean and format project data: ensure project IDs conform to Fusion
naming rules, and remove obsolete projects. Map legacy cost categories and billing rules to Fusion’s
project cost and billing setup. Convert currencies for project budgets if project currency differs from
ledger. Verify that all required profile values (like work breakdown structure segments) exist in
Fusion before load.
• Loading (ETL): Use Fusion’s Project Management FBDI templates. For example, use the Project
Import template to create projects and tasks, and Budget Import templates for project budgets.
Populate each XLSM template, generate the CSV zip, and submit the Load Interface File for Import
process followed by the specific Project import processes 3 4 . Load projects (and tasks) before
loading budgets and costs. If you have very large data volumes (e.g. thousands of tasks), consider
splitting the data into multiple runs or directly using CSV loads instead of the Excel macro (as
recommended for high‑volume imports).
• Historical Data: If carrying forward project history, load all open and in-progress project costs as of
cut‑off. Use the Miscellaneous Costs or resource burdening interfaces to import actual labor/
expense transactions, if needed. Alternatively, you may load cumulative balances (earned value) for
projects via specific import programs if available. Ensure any open commitments or accruals in the
legacy system are either loaded or excluded consistently.
• Multi-Currency: For projects with a separate project currency, set the conversion rate type on the
project definition. Fusion will use the exchange rates (loaded earlier) to convert amounts. Verify that
the project’s currency conversion rules are correct so that budgets and costs translate to ledger
currency properly. If projects span multiple countries, consider using reporting currency budgets for
consolidated reporting.
• Validation and Reconciliation: After loading, verify that all projects and tasks appear as expected in
the Project Foundation work area. Check that project budgets sum correctly and match legacy totals.
For a sample project, compare a few budgeted and actual cost lines between JDE and Fusion. Run
the Project Issues report or other seeded reports to see if any errors occurred. Confirm that funded
projects have the correct funding sources loaded. As with other domains, ensure the total of
imported project costs (by type) reconciles to the legacy data.
• Common Issues & Pitfalls: As always, do not alter the FBDI templates’ structure 9 . Watch for
locked or expired project records – Fusion will not import projects with status values that do not exist
or with dates outside active ranges. Ensure that all referenced resources (employees) or tasks have
been loaded first. If loading budgets and transactions in multiple currencies, check that the legacy
exchange rates covered the date range; missing rates will cause import failures. Very large files can
cause timeouts; break them into smaller pieces if possible.

Sources: Oracle’s official implementation guides emphasize iterative extraction, mapping, and validation
1 8 . Use FBDI (and ADFdi/ETL) tools as prescribed, and reconcile data thoroughly. In one migration

example, experts highlight the importance of pre‑built templates and tools for migration and the need to

3
ensure complete, accurate data transfer with post‑load validation 12 2 . Oracle documentation and
best practices stress not modifying CSV templates and encoding in UTF‑8 10 9 , as well as treating
currency setups and ledgers carefully 6 7 . Following these steps and checks will help ensure data
accuracy, completeness, and compliance in the Fusion Cloud ERP system.

1 8 Data Conversion and Migration Overview

https://docs.oracle.com/en/industries/energy-water/shared/22c/cs-implementation-guide/CS_IMPLEMENTATION_22C/
Data_Upload_Support_Overview.11.2.html

2 How to Accelerate Oracle EBS to Fusion Cloud Migration

https://www.itconvergence.com/blog/easier-and-faster-migrations-moving-from-on-premise-to-oracle-fusion-cloud/

3 4 File-Based Data Import in Oracle Fusion Cloud Project Management

https://docs.oracle.com/en/cloud/saas/project-management/25b/oefpp/file-based-data-import-in-oracle-project-portfolio-
management-cloud.html

5 6 Primary Ledgers, Secondary Ledgers, and Reporting Currencies

https://docs.oracle.com/en/cloud/saas/financials/24c/faigl/primary-ledgers-secondary-ledgers-and-reporting-currencies.html

7 Import Historical Rates

https://docs.oracle.com/en/cloud/saas/financials/25a/oefbf/importhistoricalrates-3191.html

9 10 11 File-Based Data Import (FBDI)

https://docs.oracle.com/en/cloud/saas/supply-chain-and-manufacturing/25a/faips/file-based-data-import.html

12 Navigating an Oracle Fusion Migration: Tips and Tricks from an Expert - Surety Systems
https://www.suretysystems.com/insights/navigating-an-oracle-fusion-migration-tips-and-tricks-from-an-expert/