Search Results psb_ws_account_line_notes




Overview
Explore in AI Chat

Overview

PSB_WS_ACCOUNT_LINE_NOTES is a table in the Public Sector Budgeting (PSB) module of Oracle E-Business Suite, documented for releases 12.1.1 and 12.2.2. The PSB product itself is flagged as obsolete in the ETRM documentation, and this table is explicitly noted as "Not implemented in this database." The table's stated purpose is to store notes associated with account lines in the budgeting worksheet model. Its seven documented columns comprise a lightweight text-annotation store keyed to worksheet account line records maintained elsewhere in the PSB schema.

The mined relationship data classifies this object heuristically as standalone under a Data Vault modeling suggestion, meaning no foreign keys were detected in the documented physical schema. In Data Vault terms this surface as a candidate satellite (or possibly a hub) rather than a link, since it captures descriptive, mutable note text attached to a parent account line rather than modeling a many-to-many business relationship. It is worth emphasizing that the standalone classification reflects the absence of mined FK evidence and should be treated as a modeling hint, not a definitive statement about the logical intent of the table.

Key Information Stored

The table's documented physical schema (ETRM 12.1.1) records seven columns owned by the PSB schema:

  • NOTE_ID — The surrogate primary key, enforced by PSB_WS_ACCOUNT_LINE_NOTE_PK and additionally backed by unique index PSB_WS_ACCOUNT_LINE_NOTES_U1. This column is the only documented unique business-key candidate.
  • NOTE — The note text itself, holding the free-form annotation content entered for an account line. This is the only substantive descriptive payload column in the table.
  • LAST_UPDATE_DATE — Standard EBS audit column recording the timestamp of the most recent modification to the row.
  • LAST_UPDATED_BY — Standard EBS audit column identifying the user who performed the most recent update.
  • LAST_UPDATE_LOGIN — Standard EBS audit column capturing the login session associated with the last update.
  • CREATED_BY — Standard EBS audit column identifying the user who created the row.
  • CREATION_DATE — Standard EBS audit column recording the row creation timestamp.

The column set is dominated by the five standard "Who" audit columns, leaving NOTE_ID and NOTE as the only functional data. Notably, no explicit foreign-key column to a parent account line is documented, and no account line identifier appears among the seven columns, so the linkage to the parent entity is not represented in the documented schema.

Common Use Cases and Queries

Because PSB_WS_ACCOUNT_LINE_NOTES is documented as not implemented in the reference database and belongs to an obsolete module, production use cases are largely historical, migration-oriented, or investigative. Typical activities include:

  • Verifying whether the table exists and is populated in a given environment before an upgrade or consolidation, since presence varies by installation.
  • Retrieving annotation history for account lines by ordering on CREATION_DATE or LAST_UPDATE_DATE to reconstruct the sequence of notes.
  • Attributing note authorship and modification activity using CREATED_BY and LAST_UPDATED_BY, often joined to per-schema user views for names.
  • Auditing stale or orphaned notes where the parent account line no longer exists, given the absence of an enforced parent reference.

A representative retrieval pattern is: select NOTE_ID, NOTE, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE from PSB_WS_ACCOUNT_LINE_NOTES where NOTE is not null order by CREATION_DATE. A change-tracking query might filter on LAST_UPDATE_DATE greater than a cutoff and group by LAST_UPDATED_BY to summarize editor activity. Because no parent key column is documented, any join back to worksheet account line tables must be established through application logic or supplemental discovery rather than a declared constraint.

Related Objects

The documented metadata records no foreign keys for this table, and the object is classified as standalone. As a result, the set of related objects below is inferred from the table's name and PSB module context rather than from declared referential constraints, and should be validated against the actual data dictionary at the target release:

  • PSB_WS_ACCOUNT_LINES — The presumed parent worksheet account line entity whose rows this table annotates. No documented join column exists; linkage is by convention and application code rather than constraint.
  • PSB_WS_ACCOUNT_LINE_NOTE_PK — The primary key constraint on NOTE_ID, the authoritative uniqueness mechanism for the table.
  • PSB_WS_ACCOUNT_LINE_NOTES_U1 — The unique index on NOTE_ID, offering an alternate retrieval path and confirming the column's uniqueness.
  • FND_USER — The standard reference for resolving CREATED_BY and LAST_UPDATED_BY into user names.
  • FND_LOGINS — The standard reference for interpreting LAST_UPDATE_LOGIN session values.

Given the standalone classification and the absence of documented foreign keys, integrators should treat any relationships beyond the primary key and unique index as inferred. Confirmation through the target environment's data dictionary is advisable before building dependent interfaces or reports.