Supplier master is foundational — Payables, Procurement and spend all depend on it. This guide covers importing suppliers into Oracle Fusion via the Supplier Import FBDI (the POZ supplier interface), the supplier/address/site/contact hierarchy, deduplication, and how to reconcile counts and balances.
The Fusion supplier model is hierarchical — supplier, supplier address, supplier site and supplier contact — and the import loads through the POZ supplier interface tables. Getting the hierarchy and keys right is the whole job.
You map legacy vendors to the Fusion supplier hierarchy, decide a dedup strategy (legacy masters are full of duplicates), and load through the Supplier Import FBDI, which stages into the POZ supplier interface tables before creating suppliers, addresses, sites and contacts.
Migration is the right moment to cleanse: merge duplicates, retire inactive vendors and standardize tax/bank details. After load, reconcile supplier counts and, where AP open items are migrated, supplier balances.
The Fusion supplier hierarchy.
The top-level party — name, tax registration, classifications.
Reusable addresses associated with the supplier.
Business-unit-specific purchasing/payment sites.
Contacts linked to the supplier and sites.
Supplier Import FBDI stages here before creating records.
Merge duplicate vendors and retire inactive ones before load.
The mechanical sequence.
Pull the legacy vendor master with addresses, sites, contacts, tax and bank details; profile for duplicates.
Merge duplicates, retire inactive vendors, standardize tax IDs and banking.
Map legacy fields to supplier, address, site and contact templates.
Populate the Supplier Import templates and load (stages into POZ interface tables).
Run the import, review rejections (tax, country, BU, duplicates) and re-load iteratively.
Match supplier/site counts to the cleansed source and, if AP is migrated, supplier balances.
What trips teams up.
Loading legacy duplicates pollutes Fusion — dedup first.
Address/site/contact must reference the right supplier.
Bad tax registrations and country codes fail validation.
Sites must map to valid business units.
Payment/bank data must be valid for net pay to suppliers.
Pre-built extraction, dedup and FBDI generation with count reconciliation.
Map your legacy vendor master to the Fusion supplier hierarchy (supplier, address, site, contact), deduplicate and cleanse, then load via the Supplier Import FBDI, which stages into the POZ supplier interface tables before creating the records. Finally, reconcile supplier and site counts (and balances if AP is in scope).
POZ is the Oracle Fusion supplier interface area (e.g. POZ_SUPPLIERS_INT and related tables) that the Supplier Import FBDI stages data into before the import process creates suppliers, addresses, sites and contacts. Errors surface against these staged rows for correction.
Deduplicate before loading — profile the legacy master, merge duplicates, retire inactive vendors and standardize tax/bank details. Migration is the best opportunity to clean the supplier base rather than replicate legacy mess.
Supplier (AP) open balances are migrated through the Payables open-invoice load, not the supplier master FBDI. Suppliers are loaded first, then open AP invoices reference them; both are reconciled.
Yes — Syntra ETL automates vendor extraction, deduplication, mapping to the supplier hierarchy, Supplier Import FBDI generation and count reconciliation.
Tell us your source system and we'll cleanse, dedup and load your suppliers into Oracle Fusion with reconciliation.