Search Results po_usage_attributes




Overview
Explore in AI Chat

Overview

The PO_USAGE_ATTRIBUTES table is a reference configuration object within the Oracle Purchasing (PO) module of Oracle E-Business Suite 12.1.1 and 12.2.2. It defines which note attributes are permitted for a given note usage, effectively binding the usage context of a note to the set of attributes that may be captured against it. The table resides in the PO schema and carries a VALID status in the data dictionary. Its functional purpose is to control the granularity and behavior of the Notes feature by governing the combination of a usage identifier and an associated note attribute.

From a dimensional modeling perspective, the ETRM relationship metadata classifies this object heuristically as a link table. This classification is a modeling suggestion rather than a physical constraint: the table sits between two parent reference tables and resolves the many-to-many relationship between note usages and note attributes. It is not a hub (it introduces no independent business key) nor a satellite (it carries no descriptive, time-variant measures beyond standard audit columns). Instead, it functions as an associative entity that clarifies which attributes apply within each usage context.

Key Information Stored

The documented physical schema contains eleven columns. The most significant are described below.

The surrogate-free primary key is defined by the constraint PO_USAGE_ATTRIBUTES_PK over (USAGE_ID, NOTE_ATTRIBUTE). A unique index, PO_USAGE_ATTRIBUTES_U1, mirrors the same column pair and serves as the business-key candidate, guaranteeing that a usage-attribute pairing is recorded only once. There is no single-column surrogate key; the composite pair carries full business meaning.

Common Use Cases and Queries

Typical scenarios include validating note configuration during implementation, troubleshooting Notes behavior where an expected attribute is unavailable in a given context, and auditing configuration changes for compliance. Because the table is a pure configuration object, query volumes are low, but accuracy is critical.

A representative query lists all attributes enabled for a specific usage:

  • SELECT ua.usage_id, ua.note_attribute FROM po.po_usage_attributes ua WHERE ua.usage_id = :usage_id ORDER BY ua.note_attribute;

To join with parent reference data and report descriptive usage and attribute names, the pattern expands to:

  • SELECT u.usage_id, u.usage_name, na.note_attribute, na.description FROM po.po_usage_attributes ua JOIN po.po_usages u ON u.usage_id = ua.usage_id JOIN po.po_note_attributes na ON na.note_attribute = ua.note_attribute;

For audit and change-analysis reporting, filtering on the audit columns identifies recently modified configuration:

  • SELECT usage_id, note_attribute, last_update_date, last_updated_by FROM po.po_usage_attributes WHERE last_update_date >= SYSDATE - 30;

Related Objects

The following objects are most significant in relation to PO_USAGE_ATTRIBUTES, based on the documented foreign key structure.

  • PO_USAGES — Parent of the link via PO_USAGE_ATTRIBUTES.USAGE_ID → PO_USAGES. Defines the note usage contexts available in the application.
  • PO_NOTE_ATTRIBUTES — Parent of the link via PO_USAGE_ATTRIBUTES.NOTE_ATTRIBUTE → PO_NOTE_ATTRIBUTES. Defines the note attributes that may be associated with usages.
  • PO_USAGE_ATTRIBUTES_PK — Primary key constraint over (USAGE_ID, NOTE_ATTRIBUTE).
  • PO_USAGE_ATTRIBUTES_U1 — Unique index serving as the business-key candidate over the same column pair.

These references establish PO_USAGE_ATTRIBUTES as the connective tissue between usage definitions and attribute definitions in the Purchasing Notes framework, and any extension or customization touching Notes configuration should account for both parent dependencies.