Search Results interface_attr_values_id

Overview

PO.PO_ATTR_VALUES_INTERFACE is a Purchasing (PO) module interface table in Oracle E-Business Suite 12.1.1 and 12.2.2. It serves as the transient staging area through which attribute value records are loaded before the concurrent interface process validates and transfers them into the permanent PO_ATTRIBUTE_VALUES table. The object is documented as VALID with owner schema PO, and it contains 330 documented columns in the 12.2.2 physical schema.

Functionally, the table carries the descriptive and category-specific attribute values that accompany purchase order interface headers and lines. Records are written here by external systems, conversion programs, or custom loaders, and are consumed by the Purchasing interface programs that create or update purchasing documents. Because it is an interface staging object, the table is intended to be populated, processed, and purged on a recurring cycle rather than retained as a permanent transactional store.

Under the heuristic Data Vault classification derived from its foreign key structure, the table is modeled as standalone. This classification is a modeling suggestion rather than a documented Oracle fact: no parent table is identified through the mined foreign key relationships, and the object functions independently in the ETRM relationship map. In practical terms, the standalone classification reflects the fact that its identifying key is a locally assigned surrogate and its referential links are expressed by convention and by the consuming interface programs rather than by enforced database constraints.

Key Information Stored

The table's primary key is the system-named constraint SYS_C00204828, defined on the INTERFACE_ATTR_VALUES_ID column. A unique index, PO_ATTR_VALUES_INT_U1, is documented on the same column, making INTERFACE_ATTR_VALUES_ID both the surrogate primary key and the sole documented business-key candidate. The most significant columns fall into these groups:

• Identity and parent linkage: INTERFACE_ATTR_VALUES_ID (primary key), INTERFACE_HEADER_ID, INTERFACE_LINE_ID, PO_LINE_ID, PROCESSING_ID.
• Processing control: ACTION, PROCESS_CODE, and the standard concurrent request audit columns REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE.
• Item and category context: INVENTORY_ITEM_ID, ORG_ID, IP_CATEGORY_ID, REQ_TEMPLATE_NAME, REQ_TEMPLATE_LINE_NUM.
• Attribute value payload: the TEXT_BASE_ATTRIBUTE1 through TEXT_BASE_ATTRIBUTE100 and NUM_BASE_ATTRIBUTE1 through NUM_BASE_ATTRIBUTE100 columns, which carry descriptive flexfield base attribute values, plus the corresponding TEXT_CAT_ATTRIBUTE1–TEXT_CAT_ATTRIBUTE50 and NUM_CAT_ATTRIBUTE1–NUM_CAT_ATTRIBUTE50 columns for category-level attribute values.
• Descriptive and sourcing detail: MANUFACTURER_PART_NUM, SUPPLIER_URL, MANUFACTURER_URL, ATTACHMENT_URL, UNSPSC, AVAILABILITY, LEAD_TIME, PICTURE, THUMBNAIL_IMAGE.
• Audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical usage centers on diagnosing interface failures, reconciling staged rows against created purchasing documents, and clearing processed rows. A frequent diagnostic pattern joins the staging table to the error table on the shared interface key:

SELECT v.interface_attr_values_id,
       v.interface_line_id,
       v.action,
       v.process_code
FROM   po.po_attr_values_interface v
WHERE  v.processing_id = :processing_id;

Error inspection is performed by correlating staged rows with PO_INTERFACE_ERRORS:

SELECT v.interface_attr_values_id, e.message_text
FROM   po.po_attr_values_interface v,
       po.po_interface_errors     e
WHERE  v.interface_attr_values_id = e.interface_attr_values_id;

Reporting use cases include tracking load volumes by ACTION and PROCESS_CODE, confirming that category attribute values (*_CAT_ATTRIBUTE*) were staged completely before submission, and verifying that each staged row was ultimately applied to PO_ATTRIBUTE_VALUES. Purge and housekeeping scripts typically filter on REQUEST_ID or PROCESSING_ID to remove rows once the interface run completes successfully.

Related Objects

The documented referential relationship shows PO_INTERFACE_ERRORS referencing this table, with PO_INTERFACE_ERRORS.INTERFACE_ATTR_VALUES_ID mapping to PO_ATTR_VALUES_INTERFACE.INTERFACE_ATTR_VALUES_ID. Beyond that enforced link, the following objects participate in the same interface flow by convention:

• PO.PO_ATTRIBUTE_VALUES — the destination table populated by the interface process.
• PO.PO_INTERFACE_ERRORS — stores validation errors keyed by INTERFACE_ATTR_VALUES_ID.
• PO.PO_HEADERS_INTERFACE — source of header-level interface context linked through INTERFACE_HEADER_ID.
• PO.PO_LINES_INTERFACE — source of line-level context linked through INTERFACE_LINE_ID.
• PO.PO_LINES_ALL — the persistent line table referenced by PO_LINE_ID after processing.
• Purchasing interface concurrent programs and the PO Attribute Values Interface API — the execution layer that reads, validates, and clears this staging table.
• PO.PO_INTERFACE_CONTROLS — governs processing requests associated with staged interface rows.