Search Results po_attr_values_int_u1

Overview

The PO.PO_ATTR_VALUES_INTERFACE table is a staging and open-interface table in the Oracle Purchasing module of Oracle E-Business Suite. It serves as the inbound landing area for attribute values associated with purchasing documents before they are validated and transferred into the base application tables, most notably PO_ATTRIBUTE_VALUES. Records are populated by external systems, feeder programs, or iProcurement flows, and are subsequently consumed by the Purchasing Documents Open Interface (PDOI) and related concurrent programs for processing. The table resides in the APPS_TS_TX_DATA tablespace in both the 12.1.1 and 12.2.2 releases.

The table carries a documented physical schema of 330 columns, dominated by generated attribute columns. Based on the foreign-key and column profile, the heuristic Data Vault classification is standalone, though a modeling exercise could reasonably treat it as a staging link that connects interface header, interface line, and item contexts. Its primary key is the system-generated constraint SYS_C00204828 on INTERFACE_ATTR_VALUES_ID.

Key Information Stored

The most significant columns fall into identification, processing-control, and descriptive attribute groups:

• INTERFACE_ATTR_VALUES_ID — Surrogate primary key and the single documented unique-index candidate (PO_ATTR_VALUES_INT_U1). Uniquely identifies each staged attribute-values row.
• INTERFACE_HEADER_ID — Foreign key linking the row to its parent interface header record.
• INTERFACE_LINE_ID — Foreign key linking the row to its parent interface line record.
• PROCESSING_ID — Identifier grouping records to be processed by a specific PDOI run.
• ACTION — The action to be taken on the record during interface processing.
• PROCESS_CODE — Interface record status code indicating the current processing state.
• PO_LINE_ID — Populated with a positive value when the row is a child of a blanket line or quotation line; otherwise set to -2.
• REQ_TEMPLATE_NAME and REQ_TEMPLATE_LINE_NUM — Requisition template identifiers, populated when applicable and -2 otherwise.
• INVENTORY_ITEM_ID and ORG_ID — Inventory item and organization context for the attribute value.
• IP_CATEGORY_ID — Item category used by iProcurement.
• MANUFACTURER_PART_NUM, PICTURE, THUMBNAIL_IMAGE, SUPPLIER_URL, MANUFACTURER_URL, ATTACHMENT_URL, UNSPSC, AVAILABILITY, and LEAD_TIME — Descriptive and punchout-related attributes.
• Extensive sets of TEXT_BASE_ATTRIBUTE1-100, NUM_BASE_ATTRIBUTE1-100, TEXT_CAT_ATTRIBUTE1-50, and NUM_CAT_ATTRIBUTE1-50 — Flexible descriptive flexfield values for base and category attribute contexts.
• Standard audit columns such as CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and REQUEST_ID.

Common Use Cases and Queries

The table is primarily queried for interface monitoring, troubleshooting failed loads, and reconciliation. Because records are transient, administrators frequently inspect rows by processing run or by parent interface identifiers.

• Monitoring a PDOI run: SELECT interface_attr_values_id, interface_header_id, interface_line_id, process_code FROM po_attr_values_interface WHERE processing_id = :run_id;
• Locating records for a specific header: SELECT * FROM po_attr_values_interface WHERE interface_header_id = :header_id;
• Retrieving punchout attributes: Querying MANUFACTURER_PART_NUM, SUPPLIER_URL, and UNSPSC for iProcurement catalogue integration review.
• Reconciliation against base tables: Joining on INTERFACE_ATTR_VALUES_ID after a successful run to confirm that base attribute values were created.
• Purging stale rows: Identifying interface records older than a cutoff using CREATION_DATE.

The composite indexes PO_ATTR_VALUES_INT_N1 (interface line/header) and PO_ATTR_VALUES_INT_N2 (processing ID) are the most efficient access paths for these queries.

Related Objects

• PO_INTERFACE_ERRORS — References this table via INTERFACE_ATTR_VALUES_ID; holds validation error messages generated during interface processing.
• PO_ATTRIBUTE_VALUES — The base application table into which validated rows are ultimately transferred.
• Interface header and interface line tables — Referenced through INTERFACE_HEADER_ID and INTERFACE_LINE_ID, forming the parent hierarchy for staged attribute values.
• Purchasing Documents Open Interface (PDOI) — The concurrent program that consumes rows filtered by PROCESSING_ID and updates PROCESS_CODE.
• MTL_SYSTEM_ITEMS — Joined through INVENTORY_ITEM_ID to resolve item descriptions.
• PO_ATTRIBUTE_VALUES_INTERFACE indexes — PO_ATTR_VALUES_INT_U1 through _N4, supporting retrieval by identifier, processing run, and organization.