Search Results pn_note_details




Overview
Explore in AI Chat

Overview

The PN_NOTE_DETAILS table is a core data object within the Oracle E-Business Suite (EBS) Property Manager (PN) module, specifically for versions 12.1.1 and 12.2.2. It functions as the detailed repository for multi-line textual notes associated with various entities managed by the application. Its primary role is to store the substantive content of notes, which are linked to a note type and header. This structure allows for the flexible attachment of descriptive, administrative, or contractual text to critical property-related records such as leases, locations, or terms, thereby providing essential context and auditability for property portfolio management.

Key Information Stored

The table's central purpose is to hold the text lines of a note. While the full column list is not detailed in the provided metadata, the documented relationships and keys reveal its critical structure. The primary key, NOTE_DETAIL_ID, uniquely identifies each line or segment of note text. The foreign key column, NOTE_HEADER_ID, is fundamental as it links each detail line to its parent record in the PN_NOTE_HEADERS table. This header record defines the note's context, including its type and the object (e.g., a lease) to which it is attached. The table presumably contains at least one column for the note text itself (e.g., NOTE_TEXT or DESCRIPTION) and likely includes standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) for tracking changes.

Common Use Cases and Queries

This table is primarily accessed to retrieve the full text of notes for reporting, auditing, or displaying within the application's user interface. A common scenario involves generating a report listing all notes for a specific lease agreement. The typical query pattern joins PN_NOTE_DETAILS to PN_NOTE_HEADERS and then to the relevant business entity table, such as PN_LEASES.

Sample Query Pattern:
SELECT h.note_type, d.note_text, d.creation_date
FROM pn_note_headers h,
pn_note_details d
WHERE h.note_header_id = d.note_header_id
AND h.reference_id = :lease_id -- Link to a specific lease
AND h.table_name = 'PN_LEASES'
ORDER BY d.creation_date;

Data maintenance is typically performed through the Property Manager application's note entry forms, which handle the creation of the header and insertion of the associated detail lines, ensuring referential integrity.

Related Objects

The PN_NOTE_DETAILS table has a direct and critical dependency on the PN_NOTE_HEADERS table, as defined by its documented foreign key relationship. This is the primary relationship for all queries.

  • PN_NOTE_HEADERS: This is the parent table. The foreign key PN_NOTE_DETAILS.NOTE_HEADER_ID references PN_NOTE_HEADERS. The header record provides the context (note type, referenced object) for the detail text.

Indirectly, PN_NOTE_DETAILS is related to all major PN module tables that support notes, such as PN_LEASES, PN_LOCATIONS, and PN_TERMS. This relationship is established through the PN_NOTE_HEADERS table, which contains columns (like REFERENCE_ID and TABLE_NAME) that identify the specific business object to which the note is attached.