Results for “pon_auction_sections_u3”

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

Overview

PON.PON_AUCTION_SECTIONS is a transactional table in the Oracle E-Business Suite Procurement (PON) schema that stores the distinct sections defined for a sourcing auction within Oracle Sourcing. A section corresponds to a grouping of Requirements (Header Attributes) that the buyer presents to suppliers during a negotiation. Each row represents one section belonging to a specific auction header, and is associated with an attribute list that determines which requirements or attributes appear in that section. The table is stored in the APPS_TS_TX_DATA tablespace with PCT Free 10, and its indexes reside in APPS_TS_TX_IDX. The object is registered under FND Design Data as PON.PON_AUCTION_SECTIONS and is marked VALID across Oracle EBS 12.1.1 and 12.2.2 deployments.

From a Data Vault modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification. The table carries descriptive and contextual attributes (section name, line number, group sequencing, two-part section type) attached to parent auction and attribute-list hubs, rather than acting as an independent hub or a pure relationship link. This classification is a heuristic and should be validated against the enterprise's own modeling standards before adoption.

Key Information Stored

The primary key is SECTION_ID, a database sequence-generated surrogate identifier (index PON_AUCTION_SECTIONS_U3 enforces uniqueness on this column alone). Business-key candidates are documented through two composite unique indexes: PON_AUCTION_SECTIONS_U1 on (AUCTION_HEADER_ID, SECTION_ID) and PON_AUCTION_SECTIONS_U2 on (ATTRIBUTE_LIST_ID, SECTION_ID).

• SECTION_ID — Surrogate primary key; the db sequence generated id for the section.
• AUCTION_HEADER_ID — Foreign key to PON_AUCTION_HEADERS_ALL; identifies the parent auction.
• ATTRIBUTE_LIST_ID — Foreign key to PON_ATTRIBUTE_LISTS; defines the requirement/attribute set associated with the section.
• SECTION_NAME — VARCHAR2(240) display name of the section.
• LINE_NUMBER — Auction line number ordering the section within the negotiation.
• ATTR_GROUP_SEQ_NUMBER — Sequence number of the section/attribute group.
• PREVIOUS_SECTION_ID — Reference to the section in the previous round or amendment, supporting version tracking.
• TWO_PART_SECTION_TYPE — VARCHAR2(20) indicating whether the section belongs to the technical or commercial part.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns.

Common Use Cases and Queries

The table is typically queried to render the structure of a sourcing auction, to reconcile sections against their attribute lists, and to trace amendment history through PREVIOUS_SECTION_ID. A representative query joining to the auction header and attribute list follows:

• List all sections for an auction: SELECT SECTION_ID, SECTION_NAME, LINE_NUMBER, TWO_PART_SECTION_TYPE FROM PON.PON_AUCTION_SECTIONS WHERE AUCTION_HEADER_ID = :p_auction_header_id ORDER BY LINE_NUMBER;
• Join to attribute lists to confirm requirement coverage: SELECT s.SECTION_NAME, a.ATTRIBUTE_LIST_ID FROM PON.PON_AUCTION_SECTIONS s, PON.PON_ATTRIBUTE_LISTS a WHERE s.ATTRIBUTE_LIST_ID = a.ATTRIBUTE_LIST_ID;
• Trace amendment lineage: query PREVIOUS_SECTION_ID recursively to reconstruct prior-round sections.

Related Objects

• PON.PON_AUCTION_HEADERS_ALL — Parent auction header, joined on AUCTION_HEADER_ID.
• PON.PON_ATTRIBUTE_LISTS — Attribute/requirement list definition, joined on ATTRIBUTE_LIST_ID.
• APPS.PON_AUCTION_SECTIONS — The APPS synonym/view exposing this table to application code.
• Section attribute mappings and other PON sourcing tables that reference SECTION_ID as a dependent key.