Results for “pos_address_notes”

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

Overview

POS_ADDRESS_NOTES is a table within the POS schema, belonging to the iSupplier Portal product module in Oracle E-Business Suite 12.1.1 and 12.2.2. As its description states, the table stores notes associated with supplier addresses. In the iSupplier Portal flow, suppliers and internal buyers can propose, review, and approve changes to supplier addresses; POS_ADDRESS_NOTES captures the free-text annotations attached to those address records, providing the audit and communication trail that accompanies an address request or a registered party site.

The object carries a heuristic Data Vault classification of link, mined from its foreign key structure. This suggests that the table is best modeled as a relationship (link) entity connecting two hubs — the address request and the party site — rather than as a standalone hub or a pure descriptive satellite. The presence of a notes payload alongside two foreign keys supports this interpretation: the row exists because an address request and a party site are associated, and the note describes that association.

Key Information Stored

The documented physical schema for 12.2.2 lists nine columns. The most significant are:

• ADDRESS_NOTE_ID — the surrogate primary key for the note record, enforced by the unique index POS_ADDRESS_NOTE_U1. This is the column to use when joining to dependent child objects or performing targeted updates.
• ADDRESS_REQ_ID — foreign key to POS_ADDRESS_REQUESTS, identifying the address change request to which the note belongs. A unique index (POS_ADDRESS_NOTE_U2) exists on this column, reflecting the one-note-per-request business rule in the documented model.
• PARTY_SITE_ID — foreign key to HZ_PARTY_SITES, tying the note to the specific party site (supplier address) being referenced. A unique index (POS_ADDRESS_NOTE_U3) is also documented here.
• NOTES — the free-text content of the note itself, holding the substantive annotation.
• CREATED_BY, CREATION_DATE — standard WHO columns recording the user and timestamp of insertion.
• LAST_UPDATED_BY, LAST_UPDATE_DATE — standard WHO columns recording the most recent modification.
• LAST_UPDATE_LOGIN — the login identifier associated with the last update, used for session-level auditing.

The three unique indexes are notable as business-key candidates: the surrogate ADDRESS_NOTE_ID is the technical identifier, while ADDRESS_REQ_ID and PARTY_SITE_ID carry uniqueness constraints that encode business rules about how notes relate to requests and sites.

Common Use Cases and Queries

Typical usage centers on supplier address change workflows. A buyer or supplier administrator reviewing a pending address request will retrieve the associated note to understand the rationale for the change. A common query pattern joins the note to its request and party site:

• Retrieve notes for a given address request: SELECT n.NOTES, n.CREATED_BY, n.CREATION_DATE FROM pos.pos_address_notes n WHERE n.ADDRESS_REQ_ID = :req_id.
• Retrieve notes for a party site: SELECT n.* FROM pos.pos_address_notes n WHERE n.PARTY_SITE_ID = :site_id.
• Reporting on note activity over time: filter on CREATION_DATE or LAST_UPDATE_DATE to audit how frequently address notes are added or modified.

Because the table carries WHO columns, it is also useful for change-audit reports and for identifying which users are annotating supplier address records.

Related Objects

• POS_ADDRESS_REQUESTS — joined via POS_ADDRESS_NOTES.ADDRESS_REQ_ID; the parent request that the note annotates.
• HZ_PARTY_SITES — joined via POS_ADDRESS_NOTES.PARTY_SITE_ID; the supplier address (party site) the note describes.
• HZ_LOCATIONS and HZ_PARTIES — reachable through HZ_PARTY_SITES for reporting address context.
• POS_SUPPLIER_ADDRESSES (and related POS supplier-address views) — typically exposed through iSupplier Portal UI, which surfaces notes for end users.
• The iSupplier Portal address management APIs and concurrent programs that process address requests, which read and write through POS_ADDRESS_REQUESTS and, transitively, this notes table.