Overview of Importing Items

You can import items and item-related information from external sources to interface tables, and then move this data into the production tables. You can import the data using FBDI or import maps.

All the data present in the import will be processed based on the batch options. The way the data is present in the import file won't determine the sequence of how the import is processed. Style and SKU items are processed together. The item import data can be classified into two entities:

• Core Entity: Includes items, item revisions, item extensible flexfields, item revision extensible flexfields, and item supplier extensible flexfields.
• Peripheral Entity: Includes item revisions, category assignments, item child org assignments, relationships, item structures, and item packs.

The core entities and peripheral entities are imported separately with the core entity processed first followed by the peripheral entities. Failures in the core entity import automatically results in errors and peripheral entities aren't processed. If the core entity is successfully imported and if there's any failure when importing the peripheral entities, then it'll only result in errors for the peripheral entities. A batch import will be considered successful if the core entity import is successful.

Profiles for Importing Items

When importing items using FBDI or import map, the following profiles play a very important role in terms of how the data is processed:

• EGP_ITEM_IMPORT_ITEMS_PER_THREAD: Determines the number of items that are grouped and processed together
• EGP_ITEM_IMPORT_NUMBER_OF_THREADS: Determines the number of threads that are launched for import processing

Settings That Affect Item Data Conversion

To support data conversion and initial load to Product Hub, the profile option: Item Data Conversion Mode Enabled must be set to enabled.

When you perform data conversion from your legacy applications into Product Hub, you must set the profile option value to Yes. The default value is No. Setting the profile value to Yes will have the following effects:

• The Import process ignores all security checks. Data Privilege and Functional privileges are not considered.

• All items will be created as approved items irrespective of whether the item class is enabled for new item request or you select to Add All Items to a new item request in batch.

• All updates will be directly posted to production by not creating change orders, even if you select the Add All Items to change order option in the batch.

• All validation rules of type Needs Approval will be ignored. This means that items are updated in the production tables.

If the profile option values are incorrect, it can adversely affect performance. You should evaluate carefully before setting these options.