Results for “note_header_id”

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

Overview

PN_NOTE_DETAILS_VL is a validation view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PN – Property Manager product family. In EBS 12.1.1 and 12.2.2 it presents note detail records together with the parent note header they belong to, exposing translatable text content for a specific language. The "_VL" suffix denotes a language (translation) view, meaning the view filters rows against the session language so that each query returns the text appropriate to the logged-in user's locale.

The view is not a standalone entity: it is a read-only projection over the note detail and note header tables. Its principal role is to support the Oracle Property Manager notes feature, where free-text notes are attached to business entities such as leases, properties, and space assignments. Reports, concurrent programs, and integration extracts use the view rather than the underlying tables to obtain already-joined, language-filtered note content.

Underlying Base Objects

The documented ETRM metadata lists two referenced objects, both exposed to APPS as synonyms:

• PN_NOTE_DETAILS — the primary base table holding individual note text rows, one per note detail record.
• PN_NOTE_HEADERS — the parent table holding the note header; each header can have multiple detail lines.

The view is a join between these two tables on NOTE_HEADER_ID, with an additional predicate that restricts ND.LANGUAGE to USERENV('LANG'), the current session language. Because the language filter is applied on the detail table, the view returns only detail rows whose language matches the environment language at the time of execution.

Key Columns

• NOTE_DETAIL_ID — the primary key of the underlying detail record; the column most commonly referenced in user searches.
• NOTE_HEADER_ID — the foreign key linking the detail to its parent note header.
• TEXT — the actual note body content, in the session language.
• ROW_ID — the ROWID of the PN_NOTE_DETAILS row, useful for direct row addressing.
• CREATED_BY, CREATION_DATE — audit columns identifying who created the note and when.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard "WHO" audit columns tracking the most recent modification.

Note that the view does not expose the LANGUAGE column itself, nor header-level descriptive attributes; it exposes header identity only through NOTE_HEADER_ID.

Common Use Cases and Queries

Typical uses include note extraction for reporting, validating note detail IDs during data conversion, and joining note content to Property Manager leases or other parent entities via the header. A representative query retrieving note text for a specific detail ID is:

• SELECT note_detail_id, note_header_id, text FROM apps.pn_note_details_vl WHERE note_detail_id = :p_detail_id;
• SELECT note_header_id, text FROM apps.pn_note_details_vl WHERE note_header_id = :p_header_id ORDER BY note_detail_id;
• SELECT note_detail_id, creation_date, created_by FROM apps.pn_note_details_vl WHERE last_update_date >= :p_since;

Because the view is language-filtered, integrations running under a language with no matching detail rows return no data; source language rows must exist in PN_NOTE_DETAILS for the session language. When reporting requires all languages irrespective of session, the base tables should be queried directly.