Import Items with FBDI

The set of Product Hub interface tables includes the main EGP_SYSTEM_ITEMS_INTERFACE table in which item data can be inserted and 13 other interface tables in which data of the item's child entities such as revisions, categories, and extensible flexfields can be inserted.

You can use the control files provided to load data from a .csv file into interface tables using the Load Interface File for Import process.

The following table lists the interface table and the related control files and objects.

Control File	Interface Table	Object
EgpSystemItemsInterface.ctl	EGP_SYSTEM_ITEMS_INTERFACE	Items Assign Items to Child Orgs
EgpItemRevisionsInterface.ctl	EGP_ITEM_REVISIONS_INTERFACE	Item Revisions
EgpItemCategoriesInterface.ctl	EGP_ITEM_CATEGORIES_INTERFACE	Item Categories
EgoItemAssociationsIntf.ctl	EGO_ITEM_ASSOCIATIONS_INTF	Item Supplier Associations
EgpItemRelationshipsIntf.ctl	EGP_ITEM_RELATIONSHIPS_INTF	Item Relationships
EgoItemIntfEffb.ctl	EGO_ITEM_INTF_EFF_B	Item level flexfields
EgoItemIntfEfftl.ctl	EGO_ITEM_INTF_EFF_TL	Item level flexfields
EgoItemRevisionIntfEffb.ctl	EGO_ITEM_REVISION_INTF_EFF_B	Item Revision flexfields
EgoItemRevisionIntfEfftl.ctl	EGO_ITEM_REVISION_INTF_EFF_TL	Item Revision flexfields
EgoItemSupplierIntfEffb.ctl	EGO_ITEM_SUPPLIER_INTF_EFF_B	Item Supplier flexfields
EgoItemSupplierIntfEfftl.ctl	EGO_ITEM_SUPPLIER_INTF_EFF_TL	Item Supplier flexfields
EgoStyleVariantAttrvsIntf.ctl	EGO_STYLE_VARIANT_ATTR_VS_INTF	Style Variant Attribute
EgpTradingPartnerItemsIntf.ctl	EGP_TRADING_PARTNER_ITEMS_INTF	Trading Partner Items
EgoItemAttachments.ctl	EGP_ITEM_ATTACHMENTS_INTF	Item Attachments

As the details of the mapping between the data of a source system and Product Hub might vary significantly based on the source system, the scope of these recommendations is limited to a best practices approach.

• Build an export file in the same format as the Product Hub interface described in the template. You will need to create staging tables and a spreadsheet that mirrors the tabs contained in this template. Then, a mapping needs to be decided as to which data of the source system goes into which Product Hub interface columns and tables. Based on the mapping, you should extract the relevant data from the source system. You can use SQL, ODI, or a similar tool to extract data into your staging tables.

• Your spreadsheet must have the same columns, and the columns must be in the same order, as in the template. The value in the first column is always the interface table name.

• Once you have extracted the data into your temporary spreadsheet, cut and paste the data into the relevant sheets provided in the template.

• For ID columns, you will need to develop a mapping between existing values and Oracle Fusion values. Use the implementation pages in the Setup and Maintenance work area to extract the identifier. For columns where you will need to use the Setup and Maintenance work area to get the Oracle Fusion values, the comments in the column header of the spreadsheet mentions the task name which you should navigate to in Setup and Maintenance work area.

• For key flexfields, you will also need to develop a way to map the values in the source system that correspond to the unique combinations in Product Hub. For key flexfield columns in the spreadsheet that require internal IDs, use the related Oracle Fusion implementation pages to export the internal IDs and the segment values in order to map to the source system values. The Items interface table has six columns that get their values from Key flexfields:

  • Process Supply Locator

  • Process Yield Locator

  • WIP Supply Locator

  • Sales Account

  • Expense Account

  • Asset Category

Import Data

After you successfully load your data, you must submit the Item Import process to import the data into the application tables to create Items and its child entities.

To submit the Item Import process:

1. Navigate to Manage Item Batches task in the Product Information Management work area.

2. Make sure that appropriate Batch Options are set for the batch.

3. Navigate to the Scheduled Processes task.

4. Click on Schedule New Process and select Item Import Process.

5. Enter the value for Batch ID and submit the process.

6. Monitor the process in the Search Results section.

7. If the Item Import Process ends in error or warning, review the log file for details.

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 is created. The other key columns for updating the item are:

• Item Number
• Organization Code
• Batch ID
• Batch Number

Correct Errors

To correct import errors:

1. Click on the Manage Item Batches task in the Product Information Management work area.

2. Search for the batch for which the Item Import process was run.

3. Click on the batch name to navigate to batch details.

4. Review the errors for each item.

5. Select the item rows that are in error and click on Manage in Spreadsheet to export Item data to spreadsheet.

6. Once all the rows are corrected, resubmit the process by clicking Upload and then submit the Item Import process.

7. Repeat the submit and error correction steps in this section until all rows are imported successfully and the items along with their child entities are created.