Results for “so_note_references”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

SO_NOTE_REFERENCES is an Order Entry (OE) transactional table in the Oracle E-Business Suite schema OE. It stores the association between a note defined in the notes repository and the specific order or order line to which that note applies. In EBS 12.1.1 and 12.2.2 the object retains the same structural role: it is the attachment bridge that binds a reusable note body to an Order Management entity. A single order header may carry multiple notes, a single note may be reused across many orders, and the same pattern applies at the line level, making this table the operational record of note placement rather than note content.

The ETRM relationship metadata classifies this object heuristically as a link in a Data Vault model. This is a modeling suggestion rather than a physical property: the table resolves many-to-many relationships among notes, note usages, order headers, order lines, and FND attachments, so it behaves as a junction or associative entity. Granularity is one row per note reference occurrence.

Key Information Stored

The surrogate primary key is NOTE_REFERENCE_ID, enforced by SO_NOTE_REFERENCES_PK and duplicated by unique index SO_NOTE_REFERENCES_U1. Because the unique index covers only the surrogate identifier, no natural composite business key is documented; business identity is expressed through the combination of NOTE_ID and the parent entity columns.

• NOTE_REFERENCE_ID – system-generated primary key for each note reference row.
• NOTE_ID – foreign key to SO_NOTES, identifying the note text being referenced.
• USAGE_ID – foreign key to SO_NOTE_USAGES, indicating the usage or context classification of the note.
• HEADER_ID – foreign key to SO_HEADERS_ALL; populated when the note applies to an order header.
• LINE_ID – foreign key to SO_LINES_ALL; populated when the note applies to an order line.
• ATTACHED_DOCUMENT_ID – foreign key to FND_ATTACHED_DOCUMENTS, linking the reference to the attachment framework.
• AUTOMATICALLY_ADDED_FLAG – distinguishes notes inserted by system defaulting or workflow from notes entered manually.
• SEQUENCE_NUMBER – orders multiple note references on the same parent entity.
• APP_SOURCE_VERSION – source application version stamp for the record.
• CONTEXT and ATTRIBUTE1–ATTRIBUTE15 – the standard EBS descriptive flexfield columns for capturing client-specific note attributes.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – audit columns identifying who created and last changed the reference.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID – concurrent program context that last touched the row.

Common Use Cases and Queries

The principal use case is retrieving the notes presented to users on the Sales Orders window and in order reports. A typical query joins the reference table to SO_NOTES to surface note text for a specific order:

• List all notes for an order header: SELECT n.note_id, n.note_text FROM so_note_references r, so_notes n WHERE r.note_id = n.note_id AND r.header_id = :header_id ORDER BY r.sequence_number;
• List notes for an order line: filter on r.line_id = :line_id using the same join.
• Identify automatically applied notes: add WHERE r.automatically_added_flag = 'Y' to isolate system-generated notes.
• Reconcile attachment framework records: join r.attached_document_id = d.attached_document_id against FND_ATTACHED_DOCUMENTS.
• Order-level note reporting: group by HEADER_ID to count notes per order or to audit note coverage across a date range using CREATION_DATE.

Because HEADER_ID and LINE_ID are both present but typically mutually exclusive, reporting logic should test which parent column is populated.

Related Objects

The FK metadata identifies the tables that this object depends on; the inverse relationships are what most queries traverse.

• SO_NOTES – joined on NOTE_ID; supplies the note text and note metadata.
• SO_NOTE_USAGES – joined on USAGE_ID; defines the usage category applied to the note.
• SO_HEADERS_ALL – joined on HEADER_ID; the order header a note is attached to.
• SO_LINES_ALL – joined on LINE_ID; the order line a note is attached to.
• FND_ATTACHED_DOCUMENTS – joined on ATTACHED_DOCUMENT_ID; integrates note references with the EBS attachment framework.

Together these objects form the note-handling path in Order Management: notes are authored in SO_NOTES, categorized through SO_NOTE_USAGES, and placed against orders or lines through SO_NOTE_REFERENCES.