Schedule Catalog Import Job
Use the Schedule Catalog Import Job scheduled process to import catalog and category data into Oracle Product Hub tables.
You can import quantities of catalog, category, and attachment data into your production tables using file-based data import (FBDI).
Prepare the data in the EgpCatalogImportTemplate.xlsm workbook and use the load interface file for the import process to load the data into the interface table before using the Schedule Catalog Import Job. When the Schedule Catalog Import Job process finishes, check the log files for status and errors during the import.
When to Use
Schedule Catalog Import Job can create a complete catalog and can update existing catalog data using file-based data import (FBDI) template into the interface tables.
Privileges Required
- Manage File Import and Export (FND_MANAGE_FILE_IMPORT_AND_EXPORT_PRIV)
- Import Item (EGP_IMPORT_ITEM_PRIV)
Specifications
Review the following before setting up this scheduled process:
| Specification | Description |
|---|---|
| Job Type | Ad hoc job or scheduled Most catalog imports jobs are run as an ad hoc job. The Purge option can be scheduled to reduce the storage if multiple catalog import jobs are run often. |
| Frequency | On a need basis |
| Time of Day | After work hours. |
| Duration | Duration can depend heavily on data volumes, such as number of categories in the catalog or the extent of the update operation on an existing catalog, making it difficult to predict. |
| Compatibility | None |
Parameters
Use this table format for parameters:
| Parameter | Optional or Required | Description | Parameter Values | Special Combinations Required | Notes |
|---|---|---|---|---|---|
| Batch ID | Required | The batch ID number that you’ve assigned in the worksheets of the XLSM template workbook that’s not already in use. | Batch ID | None | You don’t have to create a batch. The number is for tracking purpose only. |
| Reprocess Errors | Optional | Reruns the import and checks the errors. |
Yes No |
None | N/A |
| Purge | Optional | Removes rows in the catalog interface table. |
All rows Error rows Processed rows |
None | N/A |
Troubleshooting Information
- You can view the errors in Schedule Catalog Import Job process log file.
- Review the text preceding each column header in the catalog XLSM template workbook on preparing the data for the column, description of the data, and the data type that the column requires.
- Catalogs are defined based on the combination of catalog name and catalog code. You must provide both the values.
- Start date is required when creating catalogs.
- Categories are defined based on a combination of category name and category code. You must provide both the values.
- Category hierarchy is created by populating the Parent Category Code column for the catalog. If not populated, the categories will be created at the first level in the catalog.
- Category code values are unique across all catalogs.
- Category name may be repeated in separate catalogs or in the different hierarchical levels within the same catalog.