Results for “pn_note_details”

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

Overview

PN_NOTE_DETAILS is a transactional table in the PN (Property Manager) module of Oracle E-Business Suite, holding the individual lines of free-form text that make up a note. In Property Manager, notes are used to attach narrative information to leases, properties, tenants, and other real estate objects. A note is modeled as a header-detail structure: PN_NOTE_HEADERS captures the note type and header-level attributes, while PN_NOTE_DETAILS stores the body text, broken into one or more lines and maintained per language.

The table is owned by the PN schema and is documented as VALID in both 12.1.1 and 12.2.2. It is a standard multi-language (MLS) dependent object: each note header can carry detail rows for multiple installed languages, with a base language row and translated rows distinguished by the LANGUAGE and SOURCE_LANG columns. From a Data Vault modeling perspective, the mined foreign-key structure classifies this table as satellite-leaning. It should generally be treated as a descriptive satellite attached to the PN_NOTE_HEADERS parent rather than as an independent hub or link; the header reference, not the detail row itself, carries the business identity.

Key Information Stored

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

• NOTE_DETAIL_ID — the surrogate primary key, enforced by the index PN_NOTE_DETAILS_PK. It uniquely identifies each detail line.
• NOTE_HEADER_ID — the foreign key to PN_NOTE_HEADERS, tying each text line to its parent note. This is the principal join column in any query.
• TEXT — the actual note content for the row. This is the descriptive payload of the satellite.
• LANGUAGE — the language of the stored text. Together with NOTE_DETAIL_ID it forms the unique business-key candidate PN_NOTE_DETAILS_U1 (NOTE_DETAIL_ID, LANGUAGE), which guarantees at most one row per detail per language.
• SOURCE_LANG — the language of the original (base) text from which a translated row was derived; equals LANGUAGE on the base row.
• CREATED_BY, CREATION_DATE — standard audit columns recording who inserted the row and when.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns recording the most recent change and the login session that performed it.

No descriptive attributes beyond the text and language controls are documented, confirming the table's narrow, append-oriented role.

Common Use Cases and Queries

Typical usage centers on reconstructing the full text of a note and on reporting note activity against property objects. A basic retrieval joins the detail to its header:

• Fetch all lines for a note: SELECT d.note_detail_id, d.text FROM pn_note_details d WHERE d.note_header_id = :header_id AND d.language = USERENV('LANG') ORDER BY d.note_detail_id;
• Full note with header context: SELECT h.note_header_id, h.note_type, d.text FROM pn_note_details d JOIN pn_note_headers h ON h.note_header_id = d.note_header_id WHERE h.note_header_id = :header_id;
• Audit of note changes: SELECT note_detail_id, last_updated_by, last_update_date FROM pn_note_details WHERE last_update_date >= :from_date;
• Translation inventory: SELECT note_header_id, language, source_lang FROM pn_note_details ORDER BY note_header_id, language;

These patterns support lease abstract reports, note history extracts, and data-migration validation. Because text may be split across several rows, concatenation or ordered aggregation is normally required before display. Multi-language queries should join FND_LANGUAGES via LANGUAGE and SOURCE_LANG when language descriptions rather than codes are needed.

Related Objects

The dominant relationship is to the parent note header; other dependencies are indirect and reached through that parent.

• PN_NOTE_HEADERS — mandatory parent. Join on PN_NOTE_DETAILS.NOTE_HEADER_ID = PN_NOTE_HEADERS.NOTE_HEADER_ID. This is the only documented foreign key.
• PN_NOTE_TYPES / note-type lookup — reached through the header; defines the classification of each note and, by extension, its detail text.
• PN_LEASES_ALL, PN_PROPERTIES_ALL, PN_TENANTS_ALL — business owners of notes; the header associates a note with these entities, and detail rows supply the visible text.
• FND_LANGUAGES — language validation for LANGUAGE and SOURCE_LANG.
• FND_USER — resolves CREATED_BY and LAST_UPDATED_BY to user names for audit reporting.

No PL/SQL API is documented as attaching directly to PN_NOTE_DETAILS; applications normally manipulate notes through their header and let the detail rows follow.