Search Results sys_c00204841

Overview

PO_ATTR_VALUES_TLP_INTERFACE is an Oracle Purchasing interface table owned by the PO schema. Its documented purpose is to serve as the interface table form PO_ATTRIBUTE_VALUES_TLP, acting as a staging area through which attribute value data — typically descriptive flexfield, catalog, and item attribute content — is loaded into the Purchasing transactional model before validation and import. The table holds 177 columns, the majority of which are generic attribute slots, reflecting its role as a wide, denormalized intake structure rather than a normalized business entity.

Rather than storing a purchasing document directly, the table stores candidate attribute rows keyed to an interface header and interface line, together with the processing context (action, process code, request identifier) needed by the concurrent import program that consumes it. Rows are transient in nature: they exist between the population of the interface and the completion of the import, after which they are validated, applied to the destination entities, and purged or archived according to site practice.

The ETRM metadata classifies this object by heuristic Data Vault analysis as standalone. As a modeling suggestion, this indicates the table is not treated as a hub, link, or satellite. It has no outgoing foreign keys to other EBS tables and is referenced by only one dependent table, PO_INTERFACE_ERRORS, confirming that it functions as an intake landing zone rather than a component of the conformed core model.

Key Information Stored

The documented unique index PO_ATTR_VALUES_TLP_INT_U1 and constraint SYS_C00204841 establish INTERFACE_ATTR_VALUES_TLP_ID as both the surrogate primary key and the sole documented business-key candidate. It provides the row identity used when the import process records and reports errors.

• INTERFACE_ATTR_VALUES_TLP_ID — surrogate primary key and unique business-key candidate for the interface row.
• INTERFACE_HEADER_ID — foreign reference to the corresponding interface header record that groups this attribute row.
• INTERFACE_LINE_ID — foreign reference to the interface line to which the attribute values belong.
• PROCESSING_ID — the processing run identifier that scopes the batch of rows handled by a given import request.
• ACTION and PROCESS_CODE — control flags describing the operation the import should perform and the processing path to follow.
• PO_LINE_ID — identifier of the destination purchasing line once the record is applied.
• IP_CATEGORY_ID and INVENTORY_ITEM_ID — category and item context against which the attribute values are interpreted.
• ORG_ID — the operating unit that owns the interface row and governs multi-org visibility.
• LANGUAGE — the language of the descriptive text carried in the row.
• DESCRIPTION, MANUFACTURER, COMMENTS, and ALIAS — principal descriptive fields accompanying the attribute payload.
• TL_TEXT_BASE_ATTRIBUTE1 … TL_TEXT_BASE_ATTRIBUTE100 and TL_TEXT_CAT_ATTRIBUTE1 … TL_TEXT_CAT_ATTRIBUTE50 — two large parallel sets of translated text attribute slots for base and catalog attribute values.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program audit columns identifying the loader run.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

The REQ_TEMPLATE_NAME and REQ_TEMPLATE_LINE_NUM columns, together with LONG_DESCRIPTION#1, further support template-driven and long-text intake scenarios.

Common Use Cases and Queries

The table is used almost exclusively in inbound conversion and integration work: external catalogs, supplier punchouts, and custom loaders populate interface rows, which are then processed by the Purchasing attribute import concurrent program. Validation failures are captured in PO_INTERFACE_ERRORS and reviewed before the batch is reprocessed.

A typical diagnostic query joins the interface table to the error table to surface rejected rows for a given request:

• SELECT a.INTERFACE_ATTR_VALUES_TLP_ID, a.INTERFACE_LINE_ID, a.ACTION, a.ORG_ID FROM PO.PO_ATTR_VALUES_TLP_INTERFACE a WHERE a.REQUEST_ID = :request_id;
• SELECT a.INTERFACE_ATTR_VALUES_TLP_ID, e.ERROR_MESSAGE FROM PO.PO_ATTR_VALUES_TLP_INTERFACE a JOIN PO.PO_INTERFACE_ERRORS e ON e.INTERFACE_ATTR_VALUES_TLP_ID = a.INTERFACE_ATTR_VALUES_TLP_ID;

Because the table carries 177 columns, reporting queries should project explicit column lists rather than selecting the full row. Counts grouped by PROCESSING_ID, ACTION, and ORG_ID are useful for monitoring backlog and confirming that a batch has been fully applied. When investigating attribute mapping, individual TL_TEXT_BASE_ATTRIBUTE and TL_TEXT_CAT_ATTRIBUTE columns can be inspected by ordinal to determine which slots a given integration is actually using.

Related Objects

• PO_INTERFACE_ERRORS — the only documented dependent table, joined on INTERFACE_ATTR_VALUES_TLP_ID; stores validation messages for rejected attribute rows.
• PO_ATTR_VALUES_INTERFACE / PO_ATTR_VALUES_TLP — the related interface and destination structures for attribute values that share the same intake model.
• PO_HEADERS_INTERFACE — referenced through INTERFACE_HEADER_ID; stores the header-level staging row.
• PO_LINES_INTERFACE — referenced through INTERFACE_LINE_ID; stores the line-level staging row.
• PO_LINES_ALL — the destination purchasing line identified by PO_LINE_ID once the interface row is imported.
• MTL_SYSTEM_ITEMS_B — source of the inventory item referenced through INVENTORY_ITEM_ID.
• FND_CONCURRENT_REQUESTS / FND_CONCURRENT_PROGRAMS — resolve REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID to the import program run.

In Oracle EBS 12.1.1 and 12.2.2 the object's definition and key structure are consistent; installations on either release can rely on the same column layout for interface population and error reconciliation.