Results for “entity_message_code”

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

Overview

PON_INTERFACE_ERRORS is a transactional table in the PON (Sourcing) schema of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. As its name implies, the table serves as the central error repository for the Sourcing module's outbound and inbound integration points with other applications. When interface programs attempt to move auctions, bids, payments, price elements, or shipment data between Oracle Sourcing and downstream or upstream systems, any validation, mapping, or processing failures are captured here rather than being silently discarded or written only to log files. This makes the table the authoritative record for diagnosing interface failures.

From a Data Vault modeling perspective, the heuristic classification for PON_INTERFACE_ERRORS is a link. The table's numerous foreign key relationships — to auction headers, payment shipment records, and price element types — support treating it as an associative construct that connects multiple business entities while carrying descriptive error attributes of its own.

Key Information Stored

The table contains 42 documented columns. The most operationally significant include:

• INTERFACE_TYPE – Identifies the interface category that produced the error, allowing rapid filtering by integration point.
• ERROR_MESSAGE_NAME and ENTITY_MESSAGE_CODE – The message identifier or code used to look up the precise failure reason.
• ERROR_VALUE, ERROR_VALUE_DATE, ERROR_VALUE_NUMBER, ERROR_VALUE_DATATYPE – The offending value and its datatype, which are critical for diagnosing data-format and validation failures.
• TABLE_NAME and COLUMN_NAME – Pinpoint the target object and column where the error occurred.
• ATTRIBUTE_NAME and ENTITY_ATTR_NAME – Provide the business attribute context for the rejected value.
• BATCH_ID, INTERFACE_LINE_ID, REQUEST_ID – Runtime correlation keys linking the error to a specific concurrent request or batch run.
• PAYMENT_ID and BID_PAYMENT_ID – Foreign keys to PON_AUC_PAYMENTS_SHIPMENTS and PON_BID_PAYMENTS_SHIPMENTS respectively.
• AUCTION_HEADER_ID – Foreign key to PON_AUCTION_HEADERS_ALL, anchoring the error to an auction.
• PRICE_ELEMENT_TYPE_ID – Foreign key to PON_PRICE_ELEMENT_TYPES.
• BID_NUMBER, LINE_NUMBER, SHIPMENT_NUMBER, PRICE_DIFFERENTIAL_NUMBER – Business-key context identifying the exact bid line or shipment.
• TOKEN1_NAME through TOKEN5_VALUE – A set of ten token name/value pairs used to substitute dynamic values into error message templates.
• APPLICATION_SHORT_NAME, WORKSHEET_NAME, WORKSHEET_SEQUENCE_NUMBER – Identify the originating application and worksheet context.
• Audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

No explicit surrogate primary key or unique business key is documented in the available metadata; the table functions primarily as a staging/diagnostic repository rather than a master entity.

Common Use Cases and Queries

Typical use cases include troubleshooting failed Sourcing interface runs, reconciling auction and bid payment uploads, and building error dashboards for integration monitoring. A common query pattern joins the table to its parent entities to enrich the error with business context:

• Retrieve all errors for a concurrent request: SELECT * FROM PON.PON_INTERFACE_ERRORS WHERE REQUEST_ID = :req_id ORDER BY CREATION_DATE DESC;
• Group errors by interface and message: SELECT INTERFACE_TYPE, ERROR_MESSAGE_NAME, COUNT(*) FROM PON.PON_INTERFACE_ERRORS GROUP BY INTERFACE_TYPE, ERROR_MESSAGE_NAME;
• Join to auction headers: SELECT e.*, a.AUCTION_HEADER_ID FROM PON.PON_INTERFACE_ERRORS e, PON.PON_AUCTION_HEADERS_ALL a WHERE e.AUCTION_HEADER_ID = a.AUCTION_HEADER_ID;
• Correlate payment errors: join PAYMENT_ID to PON_AUC_PAYMENTS_SHIPMENTS or BID_PAYMENT_ID to PON_BID_PAYMENTS_SHIPMENTS.

Reporting typically focuses on error frequency by interface type, aging of unresolved errors, and trends across batch runs.

Related Objects

The table is linked through foreign keys to the following documented objects:

• PON_AUC_PAYMENTS_SHIPMENTS (via PAYMENT_ID).
• PON_BID_PAYMENTS_SHIPMENTS (via BID_PAYMENT_ID).
• PON_AUCTION_HEADERS_ALL (via AUCTION_HEADER_ID).
• PON_PRICE_ELEMENT_TYPES (via PRICE_ELEMENT_TYPE_ID).

These relationships make the table a useful link between Sourcing auction, bid, payment, and price element data and the error diagnostics that arise during their interface processing.