Results for “ip_category_id”

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

Overview

PON_ATTRIBUTES_INTERFACE is a temporary (staging) table in the PON schema belonging to the Oracle Sourcing module (PON). It holds the attribute details that are transferred from Oracle Purchasing's blanket purchase agreement (BPA) functionality into a negotiation document. In Oracle EBS, negotiation documents — RFQs, RFPs, and auctions — carry sourcing attributes (name/value pairs used to describe or qualify lines and lots). When those attributes originate in a BPA rather than being entered directly in the negotiation UI, they are first loaded into this interface table before the Sourcing concurrent programs validate and move them into the permanent negotiation structures.

From a heuristic Data Vault classification, the table is characterized as standalone. This suggests a modeling treatment in which PON_ATTRIBUTES_INTERFACE functions primarily as a staging or dependent structure keyed to its parent interface header rather than as an independent hub. In practice it behaves as a satellite-like staging object: transaction-oriented, transient, and purged once the loading process completes.

Key Information Stored

The table contains eight documented columns. The most operationally significant are:

• INTERFACE_AUCTION_HEADER_ID — the foreign key linking each attribute row to its parent record in PON_AUC_HEADERS_INTERFACE. It groups all attribute rows belonging to a single negotiation being staged.
• INTERFACE_LINE_NUMBER — identifies the negotiation line to which the attribute applies.
• INTERFACE_SEQUENCE_NUMBER — orders attribute rows within a line or header, preserving the sequence in which attributes should be presented or applied.
• ATTRIBUTE_NAME — the name of the sourcing attribute being transferred.
• DATATYPE — the declared data type of the attribute (for example, text, number, or date), used for validation on load.
• VALUE — the actual attribute value supplied from the BPA.
• IP_CATEGORY_ID — identifier of the associated category in the sourcing attribute/category framework, where categorization applies.
• IP_DESCRIPTOR_ID — identifier of the attribute descriptor in the Purchasing/Sourcing attribute descriptor model, tying the name to a defined attribute definition.

The combination of INTERFACE_AUCTION_HEADER_ID, INTERFACE_LINE_NUMBER, and INTERFACE_SEQUENCE_NUMBER serves as the effective business key for a staged row. No separate surrogate primary key is documented in the metadata provided; the header ID is the principal relational anchor.

Common Use Cases and Queries

Typical usage centers on diagnosing attribute transfers from BPA to negotiation. Common patterns include:

• Verifying that all BPA attributes reached the negotiation header, by counting rows grouped by INTERFACE_AUCTION_HEADER_ID.
• Investigating load failures by examining rows still present in the interface table after processing — persistent rows usually indicate validation or datatype mismatch issues.
• Auditing attribute values against the source BPA to reconcile differences after transfer.

A representative query pattern joins the interface table to its header parent:

• SELECT h.interface_auction_header_id, a.interface_line_number, a.interface_sequence_number, a.attribute_name, a.datatype, a.value FROM pon.pon_auc_headers_interface h, pon.pon_attributes_interface a WHERE h.interface_auction_header_id = a.interface_auction_header_id ORDER BY a.interface_line_number, a.interface_sequence_number;

Because this is a temporary table, reporting should generally target the post-load negotiation tables rather than this interface object.

Related Objects

• PON_AUC_HEADERS_INTERFACE — parent interface table; joined on INTERFACE_AUCTION_HEADER_ID. This is the only documented foreign key relationship.
• PON_AUC_LINES_INTERFACE — the line-level interface staging table, correlating with INTERFACE_LINE_NUMBER.
• PON_AUC_HEADERS / PON_AUC_LINES — the permanent negotiation tables that receive the validated attribute rows.
• PON_AUC_ATTRIBUTES / negotiation attribute tables — final destination for attribute name/value pairs after the interface load.
• Purchasing attribute descriptor and category tables — referenced conceptually by IP_DESCRIPTOR_ID and IP_CATEGORY_ID.
• Sourcing concurrent programs — the loaders and validators that read this table and publish results into the permanent negotiation model.

Together these objects form the inbound path by which BPA attribute content becomes a live sourcing negotiation.