What is File-Based Data Import (FBDI

is a bulk data import tool that allows users to import high volumes of data from external systems into
Oracle Fusion Applications.

FBDI templates

are essentially spreadsheets designed to gather data in a specific format that can be used by the FBDI
tool. The templates correspond to various entities in Oracle Fusion SCM,FIN,CRM such as items,
suppliers, purchase orders, etc

The steps to use templates:

1. Download the FBDI Template: From the Oracle Application homepage, navigate to ‘Scheduled
Processes’ under ‘Tools’. Here, search for a process with the name ‘Load Interface File for
Import’ and download the zip file for the relevant entity (e.g., ‘Item Import’).

2. Prepare the Data: Open the downloaded spreadsheet and populate it with the data to be
imported. Each sheet in the spreadsheet corresponds to a different table in the Oracle Fusion
database.

3. Generate CSV File: After populating the data, go to the ‘Instructions’ sheet within the template
and click ‘Generate CSV’. This will create a CSV file of your data, which can be uploaded to the
Oracle Fusion application.

4. Upload the CSV File: Back on the Oracle Application homepage, navigate to ‘File Import and
Export’ under ‘Tools’. Here, upload the generated CSV file.

5. Run the Import Process: Finally, navigate back to ‘Scheduled Processes’. Search for the relevant
import process (e.g., ‘Import Items’) and run it, selecting the uploaded file as the input.

Implementation steps

Organize Your Data in the FBDI Spreadsheet Import Template

To organize the data in the FBDI import template:

Download the FBDI template for the object you want to import.

1. Open the File-Based Data Import for SCM guide on Oracle Help Centre.

here
  Within the Contents panel in the guide, scroll to the object you need to import and click the
name (Example: Item). You can also use the search bar to search within the book. For example,
search for Item Import to navigate directly to the appropriate page.

 In the topic for the object, click the XLSM file link to download the template (for example,
ItemImportTemplate.xlsm).

After downloading the appropriate template, open it and confirm that macros are enabled.
2. Fill in all the required data and any optional data as desired on any or all worksheets.

 The ItemImportTemplate.xlsm template file contains multiple tabs, each a worksheet. The first
tab contains the instructions for using the template and generating the CSV ZIP file. The other
tabs, also called Control Files correspond to each of the Item interface tables. Each worksheet or
control file corresponds to an interface table. For example, the tab named:
“EGP_SYSTEM_ITEMS_INTERFACE” corresponds to the interface table used for the import of
items.
  The Interface table names are very important because after you load items to the interface you
can check from the backend if items have been loaded or you can track any errors that occurred
during the upload. Each interface table is represented as a separate Excel sheet.

Important considerations before you start filling the file:

 The interface table tabs contain sample data, that can be used as a guideline to understand how
to populate the fields.

 You will see sample data in all worksheets. Please consider that these are samples only and you
do not need to upload this information. You can review how sample data has been populated
and then delete all sample data from all worksheets.

 The first row in each sheet contains column headers that represent the interface table columns.
The columns are in the order that the control file expects them to be in the data file.

DO NOT:

 change the order of the columns in the Excel sheets. Changing the order of the columns will
cause the load process to fail.

 delete columns not being used. Deleting columns will cause the load process to fail. You can
hide columns that you do not intend to use; if needed, during the data creation process, but
please reset to unhidden before upload.
  Each column header contains expected data type and, in some cases, instruction text.

Tips for entering data into the template:

 The first row in each sheet contains column headers that represent the interface table columns.
The columns are in the order that the control file expects them to be in the data file.

 Don't change the order of the columns in the Excel sheets. Changing the order of the columns
will cause the load process to fail.

 You can hide columns that you don't intend to use, but you can't delete columns. Deleting
columns will cause the load process to fail.

 You must enter data that conforms to what the control file can accept and process for the
associated database column: 1.Date fields must be entered in YYYY/MM/DD format. 2.Amount
columns must not contain a thousand separator and must use a period (.) as the decimal
separator. 3.Columns that must be whole numbers have data validation to allow only whole
numbers to be entered.

 Refer to the bubble text on each column header for information on the data and data type the
column requires.

 The predefined source system code PIMDH (for Product Information Management Data Hub) is
used when you want to import items that don't originate from an external source system, such
as a supplier.

 The provided item class is called Root Item Class, this item class will be used for imports.

 Items are always created in a master organization. Organizations are created during initial setup
of the environment using the Setup and Maintenance task.

 Provide a numeric Batch ID. Non-Product Hub customers don't have access to create batches, so
any ID is sufficient.

 The system identifies the items that must be updated based on the Transaction Type column. If
Transaction Type is set to Sync, during import if the item exists in the database, then the item is
updated. If the item doesn’t exist in the database, then it’s created. The other key columns for
updating the item are: Item Number, Organization Code, Batch ID, Batch Number.
  To delete values of attributes, including individual values of multirow attributes, set the
Transaction Type to Delete for the values you want to delete.

Now as instructions are clear let me go through the important columns in System_Items_Interface sheet
and explain how they should be filled:

 Transaction Type: Choose Create if it is the first time you are uploading the items

 Batch ID: Enter a random number for your batch. The ID does not need to be unique, you will
use the same ID for the whole batch and also you will use this batch ID in uploading
Item_Categories worksheet. Please remember this ID as you will need it while loading items
from interface to main table.

 Item number: Enter unique Item number associated with each item (each number should be
unique)

 Organization Code: You need to enter Organization code, not the Organization name. To get
Organization Code go to Setup and Maintenance work area and the Manage Inventory
Organizations task.

 Description: Enter item description

 Template Name: If you already have a template for items, it will be very comfortable to include
just template name as you will not be able to fill other columns if you apply templates. All fields
will be applied from the template. In order to get the template name, go to Setup and
Maintenance work area, and the Manage Item Classes task.
 Item Class Name: Enter Item Class name which you can derive from Manage Item Classes (Setup
and Maintenance area)

 Primary Unit of Measure: Enter the primary Unit of measure for the item. If you want to make
sure that you have entered the correct UOM, you can go to Manage Units of Measure from
Setup and Maintenance are and check for the UOM names field.

 Lifecycle phase: Enter lifecycle phase name which is defined in Manage Lifecycle Phase from
Setup and Maintenance area.
  Item Status: Enter Item status as Active. You can review Item statuses from Manage Item Status
> setup and Maintenance Work Area.

You do not need to fill the rest columns in this Sheet as all fields will be populated from the template.

Now let us fill Item_Categories_Interface worksheet with necessary information.

 Batch ID: Enter a Batch ID which you have entered in Item Interface worksheet. They should be
the same.

 Item Number: Copy Item numbers from Item_Interface worksheet

 Catalog: Enter catalogue name. You can check the catalogue name from Manage Catalogue
Task> Setup and Maintenance Work Area.

 Category Name: Enter Category name which you want to assign the item. can check the category
name from Manage Catalogue Task> Setup and Maintenance Work Area.

Generate the CSV File

After you complete entering data in the item import template file, generate a .CSV file that will be used
for importing the data.

In the FBDI import template file, on the Instructions and CSV Generation tab, click Generate .CSV File to
generate the file. Save the file to your local drive
The macros in the spreadsheet will generate the CSV files and combine them into a zip file for each tab
completed in the item import template file.

Upload the CSV File to Oracle WebCenter Content

After you’ve created the CSV file, upload the CSV file to the designated location within the Oracle
WebCenter Content system.

The Oracle WebCenter Content system is an enterprise content management system that manages web
content, documents, imaging management, and digital assets for Oracle Fusion applications.

Note: You must have the correct functional privileges to support the upload of the CSV zip file to the
Oracle WebCenter Content system and have access to the WebCenter Content account scm/item/import
for items and scm/changeOrder/import for change orders.

To upload the data to the Oracle WebCenter Content system:

 From the Navigator link, go to Tools and click File Import and Export.
The Overview page is displayed.

 From the Actions menu, click Upload.

The Upload File dialog box is displayed.

 Click Browse and select the CSV file to be imported.

 From the Account drop-down list: For Items: Select scm/item/import For Change Orders: Select
scm/changeOrder/import

 Click Save and Close.

Next, you can load the data from Oracle WebCenter Content to the interface tables.

Load Data from Oracle WebCenter Content to Interface Tables

Once the CSV file is uploaded to Oracle WebCenter Content, you use the Load Interface File for Import
scheduled process to move the data from the Oracle WebCenter Content folder to the interface tables.

To move the data to the interface tables:

 In Oracle Fusion Cloud, go to Navigator > Tools > Scheduled Processes.

 In the Schedule New Process dialog box, select the following: Type: Job Name: Load Interface
File for Import

 Click OK.

 In the Process Details dialog box, specify the following: Import Process: Select Item Import. This
determines which interface tables will be populated from the file upload. Data File: Name of the
CSV ZIP file you uploaded to Oracle WebCenter Content.

 Click Submit to start the process.

Import Data from Item Management Interface Tables to Item Management Production Tables

 At this point in the import process, the data is loaded into the Item Management interface tables
and is ready to be moved into the Item Management production tables.

 You can use the Item Import scheduled process to move this data to the production tables. This
process performs all the validations necessary to ensure that the data is correct prior to moving
the data into the production tables. After successful completion of this process, the data will be
available in the user interface.
  To move the data from the interface tables to production tables:

 From the Navigator link, go to Tools and click Scheduled Processes.

 Click Scheduled New Process.

 In the Schedule New Process dialog box, select the following: Type: Job Name: Item Import

 Click OK.

 In the Process Details dialog box, enter item import for the import process.

Specify the following information in the Process Details dialog:

 Batch ID: Enter a unique identifier of the batch used to import the items. It should be the same
as the batch ID in the FBDI excel file.

 Process All Organizations: Select Yes to import items from all organizations. Select No to not
import items from all organizations.
  Process only: Indicate which transaction-type records need to be processed for an item batch.
Values are Create, Sync, or Update.

 Delete Processed Rows: Indicates if the rows in the interface tables must be deleted after the
processing of an item batch. Values are Yes or No.

Click Submit to start the process.

A configuration dialog box is displayed with the process ID. Make a note of the ID.

 Multiple processes are created for all the steps in importing the item. Various child process such
as Preprocessing, Data Quality Matching, Gather Stats, Definition-Reference Org Processing, Item
Import and Post Item Import are involved.

 View the log file for any errors (if applicable), by selecting the row in the Search Results table and
clicking View Log.