Results for “so_notes”

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

Overview

The OE.SO_NOTES table is the master repository for standard notes that can be attached to sales orders and order lines within the Oracle Order Entry (OE) module of Oracle E-Business Suite. It stores reusable, predefined note text — distinct from ad-hoc or manually entered notes — along with the metadata that governs how and where each note is applied. In Oracle EBS 12.1.1 and 12.2.2, this table underpins the Standard Notes functionality used by order management personnel to apply consistent messaging to orders, lines, and related documents without re-keying free-form text.

From a Data Vault modeling perspective, the heuristic classification for SO_NOTES is hub-leaning. This suggests treating SO_NOTES as a hub entity keyed on NOTE_ID, with descriptive and versioned attributes (note text, activation dates, flexfield context) represented in an associated satellite. The classification is derived from the foreign-key topology, where SO_NOTES is referenced by multiple child tables rather than acting purely as a transactional link.

Key Information Stored

The table contains 32 documented columns. The most operationally significant include:

• NOTE_ID — the surrogate primary key, enforced by the SO_NOTES_PK constraint and also exposed as unique index SO_NOTES_U1. This is the identifier propagated to all dependent tables.
• NAME — the business-facing label used to select the note in Order Entry windows.
• NOTE — the actual note text applied to orders and lines.
• NOTE_TYPE_CODE — categorizes the note (for example, standard versus usage-specific variants).
• USAGE_ID — foreign key to SO_NOTE_USAGES, defining the usage context in which the note applies.
• OVERRIDE_ALLOWED_FLAG — controls whether users may edit the note text after it is applied.
• START_DATE_ACTIVE and END_DATE_ACTIVE — date-range gating that determines when the standard note is valid.
• DESCRIPTION — supplementary explanation of the note's purpose.
• DOCUMENT_ID and APP_SOURCE_VERSION — document linkage and source-version tracking.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield columns for extensibility.
• Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN).

Common Use Cases and Queries

Typical scenarios include validating active standard notes, retrieving note text for a given usage, and reconciling notes referenced on orders. Sample query patterns:

• Listing currently active standard notes by usage: SELECT NOTE_ID, NAME, NOTE FROM OE.SO_NOTES WHERE USAGE_ID = :usage AND SYSDATE BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE);
• Auditing recently modified notes: SELECT NOTE_ID, NAME, LAST_UPDATE_DATE, LAST_UPDATED_BY FROM OE.SO_NOTES ORDER BY LAST_UPDATE_DATE DESC;
• Finding rules that reference each note via the addition-rules link: SELECT n.NOTE_ID, n.NAME, r.NOTE_ID FROM OE.SO_NOTES n, OE.SO_NOTE_ADDITION_RULES r WHERE r.NOTE_ID = n.NOTE_ID;
• Reporting on descriptor flexfield usage: filter on CONTEXT and ATTRIBUTE columns to segment notes by custom classifications.

Related Objects

The following objects have documented relationships to SO_NOTES:

• SO_NOTE_USAGES — parent of SO_NOTES via SO_NOTES.USAGE_ID; defines usage classifications for notes.
• SO_NOTE_ADDITION_RULES — references SO_NOTES.NOTE_ID; determines when a note is automatically added to an order or line.
• SO_NOTE_REFERENCES — references SO_NOTES.NOTE_ID; tracks notes referenced by orders or other entities.