Search Results num_cat_attribute1

Overview

PO_ATTR_VALUES_MERGE_V is a Purchasing (PO) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the item and supplier attribute values maintained by the Oracle Purchasing attribute-value framework, consolidating rows that originate in both the published attribute value table and the corresponding draft (unpublished) table. Its purpose is to present a single, merged result set so that consumers — Oracle Forms, concurrent programs, and external integrations — see attribute data that reflects both committed and in-progress sourcing, catalog, and item descriptive content without having to union the two sources themselves.

The view is commonly encountered when users search on text_base_attribute1 or one of the related TEXT_BASE_ATTRIBUTEn columns. These are the generic, "flexfield-like" attribute slots used for item and supplier attribute personalization in the Purchasing attribute value model. Because the view carries the full set of TEXT_BASE_ATTRIBUTE1 through TEXT_BASE_ATTRIBUTE(n) columns, it is the practical entry point for reporting on attribute content that has been captured against purchase lines, sourcing rules, ASLs, and requisition templates.

Underlying Base Objects

The documented metadata for 12.2.2 lists four referenced base objects, each accessed through a public synonym in APPS:

• PO_ATTRIBUTE_VALUES — the published / committed attribute value rows.
• PO_ATTRIBUTE_VALUES_DRAFT — attribute values held in draft (not yet published) state.
• PO_DRAFTS — the draft header/container that aggregates changes pending publication.
• PO_LINES_ALL — the purchasing document lines to which attribute values are linked via PO_LINE_ID.

The view text selects primarily from PAVD, the alias for the attribute-values draft source, with the merge behavior implemented by joining draft rows back to the published and line-level tables. This is why the view is described as a "merge" view: it surfaces draft attribute values alongside published values, keyed on the underlying INTERFACE_ATTR_VALUES_ID and ATTRIBUTE_VALUES_ID identifiers.

Key Columns

• ATTRIBUTE_VALUES_ID — primary identifier for a published attribute value row.
• INTERFACE_ATTR_VALUES_ID — identifier from the interface/draft staging table, used to correlate a merged row with its draft origin.
• PO_LINE_ID — foreign key to the purchasing line whose attributes are being described.
• ASL_ID — approved supplier list reference for supplier-item attribute values.
• REQ_TEMPLATE_NAME / REQ_TEMPLATE_LINE_NUM — the requisition template and line to which the attribute set applies.
• INVENTORY_ITEM_ID / IP_CATEGORY_ID / ORG_ID — item, category, and operating unit context.
• MANUFACTURER_PART_NUM, UNSPSC, LEAD_TIME, AVAILABILITY — descriptive sourcing attributes.
• THUMBNAIL_IMAGE, SUPPLIER_URL, MANUFACTURER_URL, ATTACHMENT_URL — supplier-facing catalog presentation fields.
• TEXT_BASE_ATTRIBUTE1 … TEXT_BASE_ATTRIBUTE50 — the generic attribute slots, each a VARCHAR2, populated per the attribute setup for the relevant context.

Common Use Cases and Queries

The view is used to report the current value of a specific generic attribute slot for a line, ASL entry, or template line, and to inspect draft attribute changes before publication. A typical query against TEXT_BASE_ATTRIBUTE1 is:

• SELECT PO_LINE_ID, INVENTORY_ITEM_ID, ASL_ID, TEXT_BASE_ATTRIBUTE1, TEXT_BASE_ATTRIBUTE2 FROM APPS.PO_ATTR_VALUES_MERGE_V WHERE INVENTORY_ITEM_ID = :item_id;
• Filter by ORG_ID to scope reporting to a single operating unit.
• Filter by PO_LINE_ID to retrieve all attribute slots for one purchasing line.
• Join ASL_ID to the ASL tables to combine attribute values with supplier qualification data.
• Use the presence of INTERFACE_ATTR_VALUES_ID to distinguish draft-sourced rows from fully published ones.

Because the view includes both published and draft attribute values, queries used for reconciliation should be explicit about whether draft data is acceptable in the output.