# Oracle Fusion FBDI Template Field Guide

> Source: https://netray.co/tools/oracle-fusion-fbdi-template-field-guide
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Map every FBDI column to its source, rule and owner before you load. Editable worksheet that exports to Excel.

## Category

oracle

## Erp

Oracle Fusion Cloud SCM

## Audience

- Oracle Cloud consultant
- Data migration lead
- Functional analyst

## Tool

**Kind:** worksheet

**Mode:** editable

**Columns:**

#### FBDI template

**Key:** template

**Type:** text

#### Sheet / interface table

**Key:** sheet

**Type:** text

#### Column

**Key:** column

**Type:** text

#### Required

**Key:** required

**Type:** select

**Options:**

- Yes
- No
- Conditional

#### Source system field

**Key:** source

**Type:** text

#### Transformation / validation rule

**Key:** rule

**Type:** text

#### Data owner

**Key:** owner

**Type:** text

#### Status

**Key:** status

**Type:** select

**Options:**

- Not started
- Mapped
- Tested
- Signed off

**Rows:**

**Template:** Item import

**Sheet:** EGP_SYSTEM_ITEMS_INTERFACE

**Column:** ITEM_NUMBER

**Required:** Yes

**Source:** Legacy.PartNo

**Rule:** Uppercase, trim, max length per your item number format

**Owner:** Engineering

**Status:** Mapped

**Template:** Item import

**Sheet:** EGP_SYSTEM_ITEMS_INTERFACE

**Column:** ORGANIZATION_CODE

**Required:** Yes

**Source:** Plant mapping table

**Rule:** Must match an existing inventory organization

**Owner:** Supply chain

**Status:** Mapped

**Template:** Item import

**Sheet:** EGP_SYSTEM_ITEMS_INTERFACE

**Column:** DESCRIPTION

**Required:** Yes

**Source:** Legacy.PartDesc

**Rule:** Remove tabs and line breaks, truncate to allowed length

**Owner:** Engineering

**Status:** Not started

**Template:** Item import

**Sheet:** EGP_SYSTEM_ITEMS_INTERFACE

**Column:** PRIMARY_UOM_CODE

**Required:** Yes

**Source:** Legacy.UoM

**Rule:** Map to Fusion UOM codes via a cross reference

**Owner:** Supply chain

**Status:** Tested

**Template:** Item import

**Sheet:** EGP_SYSTEM_ITEMS_INTERFACE

**Column:** TEMPLATE_NAME

**Required:** Conditional

**Source:** Item type decision table

**Rule:** Use only item templates that exist in the target pod

**Owner:** Functional lead

**Status:** Not started

**Notes:** The sample rows show the shape of an item import mapping. Column names and required flags change between releases, so always copy the real list from the FBDI workbook for your update and the Oracle Help Center import guide, then use this sheet to track decisions around it.

## Content

**Intro:** File Based Data Import is how most Oracle Fusion Cloud SCM data gets loaded during implementation and cutover. This worksheet keeps the mapping decisions for each FBDI column in one place so loads stop failing for avoidable reasons.

**Sections:**

#### How to use the field guide

**Body:** Start from the macro-enabled FBDI workbook for your release. For each sheet, list every column you will populate, whether it is required, where the value comes from, the rule that transforms it and the person who owns it. Add columns you decide to leave blank so reviewers can see that blanks were intentional. Export to Excel and share it with the business data owners so sign off is recorded against a specific column, not a general feeling.

#### How an FBDI load works

**Body:** You fill the workbook, generate the zip of CSV files, upload it to the Universal Content Management account used by the integration, and run the Load Interface File for Import scheduled process. Then you run the import process for the business object. Errors appear in the interface tables and in the process log. Because the load is staged, you can fix the source file and rerun without touching production tables until the import step succeeds.

**Bullets:**

- Generate zip from the workbook
- Upload to the correct UCM account
- Run Load Interface File for Import
- Run the object import and review rejects

#### Typical mapping problems

**Body:** Most rejected rows come from reference data that does not exist yet: organization codes, units of measure, item templates, catalog categories and lookup values. Load order matters, so set up and load reference data before transactional objects. Other common causes are dates in the wrong format, text with embedded commas or line breaks, and numbers with thousand separators. Put a validation rule on every column that touches a lookup.

#### Cutover discipline

**Body:** Keep one worksheet row per column, one status per row, and review the Not started count daily in the weeks before a mock load. Re-run mock loads with the same file structure so you measure rejection rates truthfully. Freeze the mapping a few days before the final load and record any changes with who approved them.

**Cta:** Netray can help check legacy ERP extracts against your mapping rules before they reach the FBDI workbook, on your own infrastructure if needed. The worksheet is complete without it.

**Faq:**

#### Where do I get the official FBDI template?

**Answer:** From the Oracle Help Center, in the File Based Data Import guide for your Fusion Cloud SCM release. Download the workbook for the object you are loading and use the version that matches your update, since columns change over time.

#### Why do my rows load into the interface table but fail on import?

**Answer:** The first step only stages the data. Import runs the business validations such as valid organization, UOM, category and lookup values. Read the error messages on the interface rows and the import process log, then fix the source data.

#### Should I edit the CSV files directly?

**Answer:** Avoid it. Regenerate from the workbook so structure stays correct, and keep your mapping in a controlled sheet. Hand edited CSV files are the usual cause of mysterious header or delimiter errors during mock loads.

#### Is FBDI the only way to load data?

**Answer:** No. REST services suit smaller or ongoing integrations, and some objects have spreadsheet loaders. FBDI is usually preferred for large initial volumes because it is staged, repeatable and supports bulk loads.

## Search terms

oracle fusion fbdi template, fbdi field mapping template, oracle fusion file based data import, fbdi item import template, oracle cloud data migration mapping sheet, fbdi excel template guide, oracle fusion fbdi mapping worksheet, fbdi load errors

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json