Search Results ego_import_option_sets




Overview
Explore in AI Chat

Overview

The EGO_IMPORT_OPTION_SETS table belongs to the EGO schema within the Oracle E-Business Suite Advanced Product Catalog (APC) module. Its documented purpose is to store default import options for either a source system or an import batch. These options govern how product and item data originating from an external source system or a discrete batch is validated, matched, and loaded into the catalog during the import process. From a modeling perspective, the ETRM data vault classification heuristic identifies this table as standalone, meaning it does not participate in significant foreign-key-driven link or satellite relationships beyond a single reference to BOM_STRUCTURE_TYPES_B. The table is relatively wide, containing 35 documented columns, and is available in both EBS 12.1.1 and 12.2.2 as a validated object.

Key Information Stored

The primary surrogate key is OPTION_SET_ID, which is also enforced as a unique business-key candidate through the index EGO_IMPORT_OPTION_SETS_U1. A second unique index, EGO_IMPORT_OPTION_SETS_U2, enforces uniqueness on BATCH_ID, ensuring a single option set per import batch. The SOURCE_SYSTEM_ID column ties an option set to its originating source system, while BATCH_ID associates it with a specific import batch. Several flag columns drive import behavior, including APPLY_DEF_MATCH_RULE_ALL, MATCH_ON_DATA_LOAD, CONFIRM_SINGLE_MATCH, CONFIRM_NO_MATCH, IMPORT_ON_DATA_LOAD, and IMPORT_XREF_ONLY. Data-matching rules are configured through DEF_MATCH_RULE_CUST_APP_ID, DEF_MATCH_RULE_CUST_CODE, DEF_MATCH_RULE_RN_APP_ID, and DEF_MATCH_RULE_RN_CODE. Product structure handling is controlled by STRUCTURE_TYPE_ID (which references BOM_STRUCTURE_TYPES_B), STRUCTURE_NAME, STRUCTURE_EFFECTIVITY_TYPE, STRUCTURE_CONTENT, and EFFECTIVITY_DATE. Change management options are captured via CHANGE_ORDER_CREATION, CHANGE_MGMT_TYPE_CODE, CHANGE_TYPE_ID, and related change notice fields, while audit columns include CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE.

Common Use Cases and Queries

Functional consultants and integration developers query this table to understand or troubleshoot the default behavior applied when importing item and product data. A typical query retrieves all option sets associated with a given batch:

SELECT option_set_id, source_system_id, batch_id,
       match_on_data_load, confirm_single_match,
       revision_import_policy, structure_type_id
FROM   ego.ego_import_option_sets
WHERE  batch_id = :p_batch_id;

Reporting use cases include auditing which source systems apply default match rules across all imports, and verifying import policy configuration before running a scheduled load. Reverse lookups by source system assist with diagnosing why a particular import chose to create a change order or to bypass cross-reference validation.

Related Objects

  • BOM_STRUCTURE_TYPES_B — referenced via STRUCTURE_TYPE_ID; defines valid product structure types applied during import.
  • EGO_SOURCE_SYSTEMS — related through SOURCE_SYSTEM_ID; identifies the originating system.
  • EGO_IMPORT_BATCHES — related through BATCH_ID; groups records belonging to a single import run.
  • EGO_ITEM_IMPORT and related import APIs — consume the option set configuration at runtime.
  • EGO_CHANGE_ORDERS / CHANGE-related tables — affected when CHANGE_ORDER_CREATION is enabled.