Search Results po_usage_attributes_u1

Overview

PO.PO_USAGE_ATTRIBUTES is a seed data table in the Oracle Purchasing (PO) schema that defines the relationship between note usages and note attributes. In Oracle E-Business Suite, notes attached to purchasing documents such as purchase orders, requisitions, and RFQs are governed by two independent classification constructs: the usage (who or what context consumes the note, such as 'Vendor') and the attribute (the action performed on the note, such as 'PRINTPO' for printing on a purchase order). PO_USAGE_ATTRIBUTES serves as the associative table that resolves these two dimensions into a valid combination.

The table resides in the APPS_TS_SEED tablespace, confirming its role as installation and upgrade seed data rather than transactional data. Oracle Purchasing populates the table automatically during installation or upgrade; end users and functional administrators do not normally maintain rows manually, and the object does not correspond to any Oracle Forms screen. From a dimensional modeling perspective, the heuristic Data Vault classification for this table is a link, since it resolves a many-to-many relationship between two independent reference entities (PO_USAGES and PO_NOTE_ATTRIBUTES) via its composite key.

Key Information Stored

The table comprises eleven documented columns. The most significant are the two business-key columns that also form the primary key and the unique index PO_USAGE_ATTRIBUTES_U1:

• USAGE_ID (NUMBER) — Identifier of the note usage, referencing PO_USAGES. This column participates in the concatenated primary key PO_USAGE_ATTRIBUTES_PK.
• NOTE_ATTRIBUTE (VARCHAR2(30)) — The note attribute name, such as 'PRINTPO'. It references PO_NOTE_ATTRIBUTES and completes the concatenated primary key.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns recording when, by which application user, and under which operating system login the row was last modified.
• CREATION_DATE, CREATED_BY — Standard WHO columns capturing the original insertion timestamp and creating user.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program WHO columns identifying the concurrent request, application, and program that last touched the row, together with the program update timestamp.

The surrogate-vs-business-key distinction is explicit here: the documented unique index PO_USAGE_ATTRIBUTES_U1 is defined on (USAGE_ID, NOTE_ATTRIBUTE), making that pair the business key, and the same two columns constitute the primary key PO_USAGE_ATTRIBUTES_PK. No separate surrogate column exists.

Common Use Cases and Queries

Typical usage centers on confirming which note attributes are enabled for a given note usage, supporting diagnostics when note text fails to print or display on a purchasing document.

• Listing all attributes for a usage: SELECT usage_id, note_attribute FROM po_usage_attributes WHERE usage_id = :usage_id;
• Resolving the 'Vendor' usage to the 'PRINTPO' attribute, the canonical seeded example in which Oracle Purchasing prints Note to Supplier on purchase orders.
• Joining to PO_USAGES and PO_NOTE_ATTRIBUTES to produce a readable catalog of usage-attribute combinations for the configured instance.
• Auditing an upgrade: comparing row counts and attribute combinations before and after patching, since rows are seeded only at install or upgrade.

Related Objects

• PO.PO_USAGES — joined on PO_USAGE_ATTRIBUTES.USAGE_ID = PO_USAGES.USAGE_ID; the usage master.
• PO.PO_NOTE_ATTRIBUTES — joined on PO_USAGE_ATTRIBUTES.NOTE_ATTRIBUTE = PO_NOTE_ATTRIBUTES.NOTE_ATTRIBUTE; the attribute master.
• FND_USER — implicit reference for CREATED_BY and LAST_UPDATED_BY.
• FND_LOGINS — implicit reference for LAST_UPDATE_LOGIN.
• FND_CONCURRENT_REQUESTS — implicit reference for REQUEST_ID.
• PO_HEADERS / PO_LINES note features — downstream consumers of seeded usage and attribute combinations through the note framework.