Results for “pon_auc_shipments_interface”

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

Overview

PON_AUC_SHIPMENTS_INTERFACE is an interface (staging) table in the PON – Sourcing product of Oracle E-Business Suite, residing in the PON schema. Its documented purpose is to store imported negotiation shipment information, meaning it acts as the landing area for shipment-level data that is loaded into Oracle Sourcing (Oracle Auctions) before the import process validates and transfers that data into the corresponding base negotiation tables. In both 12.1.1 and 12.2.2 the table retains the same role as a transient staging structure populated by external sources, supplier spreadsheet uploads, or custom integration programs, and then consumed by the Sourcing import concurrent program.

The metadata's heuristic Data Vault classification is satellite-leaning. Read as a modeling suggestion, this indicates that the table carries descriptive, attribute-level detail that is dependent on higher-level business keys rather than acting as an independent hub of unique business entities. The grain is defined by its composite key rather than by a standalone surrogate identifier.

Key Information Stored

The table is documented with fourteen columns and one unique index, PON_AUC_SHIPMENTS_INTERFACE_U1, defined on (INTERFACE_AUCTION_HEADER_ID, INTERFACE_LINE_NUMBER, INTERFACE_SHIP_NUMBER). These three columns together form the documented business-key candidate and also the primary key PON_AUC_SHIPMENTS_INTERFACE_PK. There is no separate single-column surrogate key; the composite identifier serves both functions.

• INTERFACE_AUCTION_HEADER_ID – Header-level identifier tying the shipment row to a specific negotiation header record.
• INTERFACE_LINE_NUMBER – Line-level identifier linking the shipment to an item/line within the negotiation.
• INTERFACE_SHIP_NUMBER – Shipment-level sequence completing the composite key.
• SHIPMENT_TYPE – Classifies the shipment (for example, quantity-based or amount-based).
• SHIP_TO_ORGANIZATION_ID – Inventory organization receiving the shipment.
• SHIP_TO_LOCATION_ID – Ship-to location; foreign-keyed to HR_LOCATIONS_ALL.
• QUANTITY – Quantity associated with the shipment line.
• PRICE – Price associated with the shipment line.
• ORG_ID – Operating unit / multi-org context for the staged row.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard WHO audit columns tracking record creation and modification.

Common Use Cases and Queries

Typical use cases center on pre-import validation and reconciliation of staged supplier or integration data. Users query this table to confirm that shipments loaded for a given header are complete before running the import, and to detect rows that failed validation.

• Verifying staged shipments for a header: SELECT * FROM PON_AUC_SHIPMENTS_INTERFACE WHERE INTERFACE_AUCTION_HEADER_ID = :p_header_id;
• Confirming shipment-to-line completeness by joining back to PON_AUC_ITEMS_INTERFACE on INTERFACE_AUCTION_HEADER_ID and INTERFACE_LINE_NUMBER.
• Resolving ship-to addresses by joining HR_LOCATIONS_ALL on SHIP_TO_LOCATION_ID.
• Reviewing audit activity and load dates through the WHO columns to trace integration runs.
• Extracting shipment-level price differential detail via PON_PRICE_DIFFER_INTERFACE.

Related Objects

• PON_AUC_HEADERS_INTERFACE – Referenced on INTERFACE_AUCTION_HEADER_ID; parent header staging table.
• PON_AUC_ITEMS_INTERFACE – Referenced on INTERFACE_LINE_NUMBER and INTERFACE_AUCTION_HEADER_ID; line staging table.
• HR_LOCATIONS_ALL – Referenced on SHIP_TO_LOCATION_ID for ship-to location details.
• PON_PRICE_DIFFER_INTERFACE – References this table on INTERFACE_SHIPMENT_NUMBER, INTERFACE_LINE_NUMBER, and INTERFACE_AUCTION_HEADER_ID.
• PON_AUC_SHIPMENTS_INTERFACE_PK / _U1 – Primary key and unique index enforcing the composite business key.