Results for “psb_budget_revision_lines”

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

Overview

PSB_BUDGET_REVISION_LINES is a core table within the Public Sector Budgeting (PSB) module of Oracle E-Business Suite, present in both the 12.1.1 and 12.2.2 releases. The table is owned by the PSB schema and holds VALID status in the ETRM data dictionary. As documented, it functions as a matrix between PSB_BUDGET_REVISIONS and PSB_BUDGET_REVISION_ACCOUNTS, resolving the many-to-many relationship between budget revision headers and the account-level revision detail they contain. In practice, each row associates a single budget revision with a single revision account line, enabling the application to track which accounts participate in which revision, along with row-level state flags such as freeze and view indicators.

From a dimensional modeling perspective, the heuristic Data Vault classification mined from the foreign-key structure is link. This is a natural fit: the table carries no descriptive attributes of its own beyond audit and control columns, and its primary key is composed entirely of foreign-key references to the two parent entities. Modelers should therefore treat PSB_BUDGET_REVISION_LINES as an associative link table rather than a hub or satellite.

Key Information Stored

The table contains nine documented columns in the 12.1.1 physical schema. The most significant are:

• BUDGET_REVISION_ID — Foreign key to the budget revision header. Part of the composite primary key.
• BUDGET_REVISION_ACCT_LINE_ID — Foreign key to the revision account line. Also part of the composite primary key.
• FREEZE_FLAG — Controls whether the revision line is frozen against further modification, typically suppressing edits during approval or locking cycles.
• VIEW_LINE_FLAG — Indicates whether the line is visible in the budgeting workspace, supporting filtered display of revision detail.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns recording the most recent change.
• CREATED_BY, CREATION_DATE — Insert-time audit columns identifying the creating user and timestamp.

The surrogate primary key is PSB_BUDGET_REVISION_LINES_PK, defined over (BUDGET_REVISION_ID, BUDGET_REVISION_ACCT_LINE_ID). The unique index PSB_BUDGET_REVISION_LINES_U1 shares the same two columns, confirming that this pair is the business-key candidate: no account line may be mapped to the same revision more than once.

Common Use Cases and Queries

Typical usage centers on retrieving the set of account lines belonging to a revision, checking freeze status before allowing updates, and filtering visible lines for reporting. A representative query joins the link to both parents:

SELECT l.budget_revision_id,
       l.budget_revision_acct_line_id,
       l.freeze_flag,
       l.view_line_flag
FROM   psb_budget_revision_lines l
WHERE  l.budget_revision_id = :revision_id
AND    l.freeze_flag = 'N';

Reporting use cases include reconciling revision coverage across accounts, auditing who last touched a revision line, and identifying unfrozen lines pending approval. Because the table is a pure link, aggregations over account attributes should be driven from PSB_BUDGET_REVISION_ACCOUNTS, filtered through this table.

Related Objects

• PSB_BUDGET_REVISIONS — Parent header table. The FK PSB_BUDGET_REVISION_LINES.BUDGET_REVISION_ACCT_LINE_ID → PSB_BUDGET_REVISIONS links each line to its revision.
• PSB_BUDGET_REVISION_ACCOUNTS — Parent account-line table. The FK PSB_BUDGET_REVISION_LINES.BUDGET_REVISION_ID → PSB_BUDGET_REVISION_ACCOUNTS maps lines to accounts.
• PSB_BUDGET_REVISION_LINES_PK / PSB_BUDGET_REVISION_LINES_U1 — Primary key constraint and unique index enforcing uniqueness on the composite key.
• PSB Budgeting concurrent programs and forms — Revision maintenance and freeze/approval workflows that read and update FREEZE_FLAG and VIEW_LINE_FLAG.

Note that the documented FK metadata lists the columns with the parent tables reversed relative to intuitive naming; implementers should verify actual constraint definitions in the target instance before relying on join direction.