Results for “line_num_display”

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

Overview

The PON_AUC_ITEMS_INTERFACE table is an Oracle E-Business Suite Sourcing (PON) staging interface used to hold imported negotiation line item information prior to validation and loading into the base negotiation schema. In Oracle EBS 12.1.1 and 12.2.2, negotiation records (RFQs, auctions, and sourcing events) can be created through bulk import utilities, including the Sourcing negotiation import program and the spreadsheet-based negotiation loaders. Data is first written to the interface family—PON_AUC_HEADERS_INTERFACE, PON_AUC_ITEMS_INTERFACE, and PON_AUC_SHIPMENTS_INTERFACE—and then processed by concurrent programs that validate and transfer the rows into the permanent PON_AUC_ITEMS and related tables.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign-key structure is satellite-leaning. The table records attribute-level descriptive detail (prices, quantities, descriptions) tied to a parent negotiation header and line, rather than serving as an independent hub of business entities. Its grain is one row per negotiation line item within an interface batch. All rows are transient by design: successful records are consumed and typically purged following the import, making this a short-lived staging object rather than a permanent transaction store.

Key Information Stored

The table contains 45 documented columns. The composite primary key, enforced by PON_AUC_ITEMS_INTERFACE_PK, is formed by INTERFACE_AUCTION_HEADER_ID and INTERFACE_LINE_NUMBER. The same column pair is also defined as unique index PON_AUC_ITEMS_INTERFACE_U1, making it the documented business-key candidate that ties each line back to its parent header and identifies it uniquely within the interface batch.

• INTERFACE_AUCTION_HEADER_ID – foreign key to PON_AUC_HEADERS_INTERFACE; identifies the parent negotiation header within the interface batch.
• INTERFACE_LINE_NUMBER – sequence number distinguishing each line item under a given header.
• LINE_TYPE_ID – foreign key to PO_LINE_TYPES_B, defining whether the line is goods, services, or another purchasable type.
• CATEGORY_ID / CATEGORY_NAME – purchasing category, with CATEGORY_ID referencing MTL_CATEGORIES_B.
• ITEM_ID, ITEM_NUMBER, ITEM_REVISION – the inventory item being negotiated.
• ORG_ID – operating unit context for the negotiation.
• QUANTITY, UOM_CODE – requested quantity and unit of measure.
• BID_START_PRICE and CURRENT_PRICE – pricing baselines used during auction/bidding.
• PRICE_BREAK_TYPE – indicates whether quantity-based price breaks apply.
• SOURCE_DOC_NUMBER, SOURCE_LINE_NUMBER, SOURCE_DOC_ID, SOURCE_LINE_ID – reference back to the originating sourcing document or requisition.
• HAS_SHIPMENTS_FLAG – indicates whether dependent shipment interface rows exist.
• CLM_* columns (e.g., CLM_OPTION_INDICATOR, CLM_CONTRACT_TYPE, CLM_FUNDED_FLAG) – contract-terms attributes for procurement contract integration.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE – standard audit columns populated by the import process.

Common Use Cases and Queries

Typical usage centers on import monitoring, error diagnosis, and reconciliation between the interface and the loaded negotiation. Administrators inspect staged rows to confirm that a bulk import populated expected fields before launching the Sourcing import concurrent program.

• Import status check – counting lines by header to verify the interface batch is complete before submission.
• Error diagnosis – joining to PON_AUC_HEADERS_INTERFACE to confirm header-line consistency, and to PON_AUC_SHIPMENTS_INTERFACE where HAS_SHIPMENTS_FLAG = 'Y'.
• Reconciliation – comparing staged QUANTITY and CURRENT_PRICE values against the loaded negotiation in PON_AUC_ITEMS.
• Pricing review – extracting BID_START_PRICE and PRICE_BREAK_TYPE for pre-auction validation.
• Purge auditing – identifying stale interface rows by CREATION_DATE and JOB_ID.

A representative query joins the header and shipment interface tables on the shared key columns:

SELECT i.INTERFACE_AUCTION_HEADER_ID, i.INTERFACE_LINE_NUMBER, i.ITEM_NUMBER, i.QUANTITY, i.BID_START_PRICE
FROM PON_AUC_ITEMS_INTERFACE i, PON_AUC_HEADERS_INTERFACE h
WHERE i.INTERFACE_AUCTION_HEADER_ID = h.INTERFACE_AUCTION_HEADER_ID;

Related Objects

• PON_AUC_HEADERS_INTERFACE – parent interface table; joined via INTERFACE_AUCTION_HEADER_ID.
• PON_AUC_SHIPMENTS_INTERFACE – child table; joined on INTERFACE_AUCTION_HEADER_ID and INTERFACE_LINE_NUMBER.
• PON_PRICE_DIFFER_INTERFACE – dependent table referencing the same header/line keys.
• PO_LINE_TYPES_B – referenced via LINE_TYPE_ID.
• MTL_CATEGORIES_B – referenced via CATEGORY_ID.
• PON_AUC_ITEMS – the permanent negotiation items table that receives validated rows.
• Sourcing Negotiation Import concurrent program – the process that consumes and transfers this interface data.

Because all interface rows are staged and consumed by import, referential integrity depends on the parent header row existing in PON_AUC_HEADERS_INTERFACE before dependent item rows are loaded.