Search Results ego_import_option_sets_u2




Overview

EGO.EGO_IMPORT_OPTION_SETS is a transactional configuration table in the Oracle E-Business Suite EGO (Engineering) schema. It stores the default import and match options applied when product data is loaded into the EGO schema from an external source system or within a specific import batch. Each row defines a discrete option set that governs how records are matched, imported, revised, and routed through change management during a data-load operation.

The table is registered in FND Design Data as EGO.EGO_IMPORT_OPTION_SETS and holds a VALID status in both 12.1.1 and 12.2.2. It resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10. With 35 documented columns, it is a moderate-width configuration object rather than a high-volume transactional table.

From a Data Vault modeling perspective, the heuristic classification for this object is standalone, meaning no inbound foreign-key dependency chain was mined beyond the outbound reference to BOM_STRUCTURE_TYPES_B. This suggests modeling the table as a hub keyed on OPTION_SET_ID, with its descriptive attributes (match flags, import flags, change-management settings) carried as satellite columns. Because the option set is scoped either to a source system or to an import batch, BATCH_ID and SOURCE_SYSTEM_ID act as secondary business keys that make the table effectively a link between import control and structure-definition context.

Key Information Stored

The surrogate primary key is OPTION_SET_ID, enforced by the unique index EGO_IMPORT_OPTION_SETS_U1. The second unique index, EGO_IMPORT_OPTION_SETS_U2, is defined on BATCH_ID and represents the business-key candidate most relevant to users searching for ego_import_option_sets_u2: it guarantees that any given import batch has at most one option set. The non-unique index EGO_IMPORT_OPTION_SETS_N1 on SOURCE_SYSTEM_ID supports lookups of defaults defined at the source-system level.

The most significant columns include:

Standard EBS audit columns (OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and the default match-rule pairs (DEF_MATCH_RULE_CUST_APP_ID/CODE and DEF_MATCH_RULE_RN_APP_ID/CODE) complete the row.

Common Use Cases and Queries

Typical usage centers on diagnosing why an import behaved a certain way, or on reviewing which automation flags are set for a batch or source system.

  • Retrieve the option set for a specific import batch: SELECT * FROM ego.ego_import_option_sets WHERE batch_id = :batch_id;
  • List source-system-level defaults: SELECT option_set_id, match_on_data_load, import_on_data_load FROM ego.ego_import_option_sets WHERE source_system_id = :source_id;
  • Report on change-management automation: SELECT batch_id, change_order_creation, change_type_id, change_notice FROM ego.ego_import_option_sets WHERE change_order_creation IS NOT NULL;
  • Audit effectivity settings: SELECT option_set_id, structure_name, structure_effectivity_type, effectivity_date FROM ego.ego_import_option_sets;
  • Identify rows using a non-default revision policy: SELECT * FROM ego.ego_import_option_sets WHERE revision_import_policy = 'N';

Related Objects

  • BOM_STRUCTURE_TYPES_B – referenced through STRUCTURE_TYPE_ID, supplying the valid structure type for the option set.
  • EGO_IMPORT_BATCHES – parent context for BATCH_ID.
  • EGO_SOURCE_SYSTEMS – parent context for SOURCE_SYSTEM_ID.
  • EGO_IMPORT_OPTION_SETS_U2 – unique index on BATCH_ID, the object most commonly queried by name.
  • BOM_CHANGE_TYPES / change-type lookup tables – resolve CHANGE_TYPE_ID.
  • EGO Item Import / PIM APIs – consume these option sets at load time to drive matching and import behavior.