Search Results po_note_references

Overview

PO_NOTE_REFERENCES is a Purchasing (PO) module table in the Oracle E-Business Suite 12.1.1 and 12.2.2 data model that stores the associations between purchasing notes and the specific documents or entities to which they are attached. Its documented description is simply "Document/notes references." Whereas a note record itself (stored in PO_NOTES) carries the note text, PO_NOTE_REFERENCES holds the pointer information that ties a note to a source document such as a purchase order, release, or quotation, and records how that note is attached through the STORAGE_TYPE and ATTACHED_DOC_ID columns. This makes the table a supporting detail table rather than a transaction-driving table; it is queried primarily during note rendering, document printing, and XML/BI Publisher output generation.

The ETRM metadata describes the Data Vault classification as "satellite-leaning." As a modeling suggestion, this reflects the table’s role as a dependent, descriptive structure keyed to a parent business entity (PO_NOTES) rather than a hub or a link. It does not establish an independent business key; it qualifies an existing note.

Key Information Stored

The table contains 34 documented columns. The most significant are:

• PO_NOTE_REFERENCE_ID – the surrogate primary key, enforced by PO_NOTE_REFERENCES_PK. It is also the column in the unique index PO_NOTE_REFERENCES_U1, making it the documented business-key candidate.
• PO_NOTE_ID – foreign key to PO_NOTES; identifies the note that this reference row qualifies. This is the principal join column.
• TABLE_NAME and COLUMN_NAME – identify the target entity and attribute to which the note applies, providing the polymorphic link used throughout the purchasing data model.
• FOREIGN_ID – the identifier value of the referenced document in the target table.
• SEQUENCE_NUM – controls ordering, and therefore display order, of multiple notes against a single document.
• STORAGE_TYPE and ATTACHED_DOC_ID – describe how the note is stored and reference any associated attachment document.
• APP_SOURCE_VERSION, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE – standard concurrent program audit context recording which program created or last touched the row.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN – the standard who-columns used for auditing and multi-user concurrency tracking.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 – ATTRIBUTE15 – the standard descriptive flexfield (DFF) columns, enabling client-specific extensions without schema change.

Columns not listed above consist of the remaining DFF segments and audit fields documented in the physical schema.

Common Use Cases and Queries

Typical usage is reporting on notes attached to purchasing documents and diagnosing missing or misplaced notes. A representative query joins PO_NOTE_REFERENCES to PO_NOTES to retrieve note text for a given document:

• SELECT n.NOTE_TEXT, r.TABLE_NAME, r.FOREIGN_ID, r.SEQUENCE_NUM FROM PO.PO_NOTE_REFERENCES r, PO.PO_NOTES n WHERE r.PO_NOTE_ID = n.PO_NOTE_ID AND r.TABLE_NAME = 'PO_HEADERS_ALL' AND r.FOREIGN_ID = :po_header_id ORDER BY r.SEQUENCE_NUM;
• Auditing which concurrent program last modified note references, using PROGRAM_ID and LAST_UPDATE_DATE.
• Extracting client-specific note attributes via ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 for downstream reporting.
• Verifying duplicate or orphaned references where FOREIGN_ID has no matching row in the target table.

Related Objects

The documented foreign key relationship anchors this table to PO_NOTES via PO_NOTE_ID. The following are the most significant related objects:

• PO_NOTES – parent table storing note text; joined on PO_NOTE_ID.
• PO_HEADERS_ALL – the principal document target identified by TABLE_NAME/FOREIGN_ID.
• PO_LINES_ALL – line-level note attachments.
• PO_LINE_LOCATIONS_ALL – shipment-level note attachments.
• PO_DISTRIBUTIONS_ALL – distribution-level note attachments.
• PO_RELEASES_ALL and PO_QUOTATIONS – additional document targets.
• PO_NOTE_REFERENCES_PK / PO_NOTE_REFERENCES_U1 – the primary-key constraint and unique index governing uniqueness.

No additional public API is documented for this object; it is maintained through the standard Purchasing note-attachment flows.