Results for “attr_group_seq_number”

50+ results




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

Overview

PON_AUCTION_SECTIONS is a transactional table within the PON (Sourcing) product family of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It stores the distinct sections that organize Requirements, specifically the Header Attributes presented to suppliers during an auction or negotiation event. Each row defines a logical grouping of attributes — for example a "Commercial Terms" section or a "Technical Compliance" section — that structures how an auction header's attribute list is displayed and evaluated.

The table sits beneath PON_AUCTION_HEADERS_ALL as a child detail entity, scoped to a single auction header, and additionally references PON_ATTRIBUTE_LISTS, which supplies the reusable attribute-set definition that populates the section. Based on the mined foreign-key structure, the heuristic Data Vault classification for this object is satellite-leaning — that is, it behaves functionally as a descriptive satellite anchored to the auction header hub, carrying section-level descriptive and ordering attributes rather than representing an independent business concept or a many-to-many relationship link. This classification should be treated as a modeling suggestion rather than a normative design statement.

Key Information Stored

The table is documented with 13 columns in the 12.2.2 physical schema. The most significant are:

The three unique indexes identify business-key candidates: (AUCTION_HEADER_ID, SECTION_ID), (ATTRIBUTE_LIST_ID, SECTION_ID), and SECTION_ID alone.

Common Use Cases and Queries

Typical reporting and integration scenarios include reconstructing the ordered section layout for a given auction, validating that every section resolves to a valid attribute list, and identifying duplicate or orphaned section definitions.

Listing sections for an auction header:

  • SELECT s.section_id, s.section_name, s.line_number, s.attribute_list_id FROM pon_auction_sections s WHERE s.auction_header_id = :p_header_id ORDER BY s.line_number;

Joining sections to their attribute lists to reconcile section content:

  • SELECT a.auction_header_id, s.section_name, al.attribute_list_id FROM pon_auction_sections s JOIN pon_attribute_lists al ON al.attribute_list_id = s.attribute_list_id WHERE s.auction_header_id = :p_header_id;

Detecting attribute lists used across multiple sections or auctions supports reuse analysis, while checking for null or dangling PREVIOUS_SECTION_ID values supports data-quality validation of ordered layouts.

Related Objects

  • PON_AUCTION_HEADERS_ALL — parent entity; joined on AUCTION_HEADER_ID. Every section is scoped to exactly one auction header.
  • PON_ATTRIBUTE_LISTS — referenced via ATTRIBUTE_LIST_ID, supplying the attribute definitions rendered inside the section.
  • PON_AUCTION_ATTRIBUTES (and related attribute-detail tables) — the header-attribute rows that are grouped by the sections defined here.
  • PON_AUCTION_SECTIONS (self) — PREVIOUS_SECTION_ID creates an intra-table ordering chain.
  • PON_AUCTION_SECTIONS_PK1 / _U1 / _U2 / _U3 — the primary and unique constraints that enforce identity and the business-key candidates.
  • Sourcing UI and negotiation APIs that read section metadata to render header attributes to suppliers, and concurrent programs that clone auction definitions, all depend on this table's ordering and naming columns.