Results for “set_id”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The OE_LINE_SETS table is owned by the ONT (Order Management) schema and is a valid table in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores information about Sets, specifically the association between individual order lines and the sets to which those lines belong. Within the Oracle Order Management data model, this table functions as an intersection or cross-reference entity, resolving a many-to-many relationship between order lines and sets at the line level.

Based on the foreign key structure detected in the ETRM metadata, the heuristic Data Vault classification for this object is a link. This modeling suggestion reflects that OE_LINE_SETS primarily captures relationships between other business entities rather than serving as a standalone hub of descriptive attributes. It links a line record to a set record, enabling grouping or bundling semantics within order processing.

Key Information Stored

The documented physical schema for ONT.OE_LINE_SETS contains four columns. The most significant are:

  • LINE_ID — The identifier of the order line. This column participates in a foreign key relationship to OE_ORDER_LINES_ALL, meaning it references the full order line record. It is a business-key candidate for the line side of the relationship.
  • SET_ID — The identifier of the set. This column participates in a foreign key relationship to OE_SETS, referencing the parent set record. It is a business-key candidate for the set side of the relationship.
  • SYSTEM_REQUIRED_FLAG — A flag indicating whether the set assignment is system-required, controlling behavior during order entry and processing.
  • INST_ID — The installation identifier, used to distinguish records across multiple Oracle EBS installations or operating units in a shared environment.

No surrogate primary key column is separately documented beyond these four columns, and the metadata does not identify a distinct unique index. In practice, the combination of LINE_ID and SET_ID typically forms the natural composite key for a given record.

Common Use Cases and Queries

This table is commonly queried when reporting on order line set membership, validating set assignments, or integrating order data with downstream fulfillment and pricing processes. Typical use cases include identifying all lines belonging to a specific set, or determining which sets a particular order line is associated with.

  • Retrieving all lines for a given set:
    • SELECT LINE_ID, SET_ID, SYSTEM_REQUIRED_FLAG FROM OE_LINE_SETS WHERE SET_ID = :set_id;
  • Joining to order lines to enrich reporting:
    • SELECT l.LINE_ID, l.ORDERED_ITEM, s.SET_ID FROM OE_LINE_SETS s, OE_ORDER_LINES_ALL l WHERE s.LINE_ID = l.LINE_ID;
  • Checking system-required set assignments: filter on SYSTEM_REQUIRED_FLAG to isolate lines whose set membership is mandated by the system.

Related Objects

The following objects are the most significant references based on the documented foreign key relationships:

  • OE_ORDER_LINES_ALL — Referenced through OE_LINE_SETS.LINE_ID. This is the primary order line table holding line-level order details.
  • OE_SETS — Referenced through OE_LINE_SETS.SET_ID. This table holds the set definitions to which lines are assigned.

Additional dependent or surrounding objects within the Order Management module include order headers (OE_ORDER_HEADERS_ALL), which provide the parent order context for lines in OE_ORDER_LINES_ALL, and the Order Management public APIs and concurrent programs that read and write set associations during order import and processing. Reporting solutions often join OE_LINE_SETS with OE_ORDER_LINES_ALL and OE_SETS to present complete set membership information across the order lifecycle.