Results for “line_sequence_id”

50+ results




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

Overview

PSBBV_ACCOUNT_SET_LINES is a read-only database view belonging to the PSB (Public Sector Budgeting) product family, which Oracle classifies as obsolete within the EBS 12.1.1 and 12.2.2 application stacks. The view exposes the line-level definition of account position sets: the ordered lists of account ranges and inclusion rules that determine which accounts participate in a given budgeting or account structure operation. Its name combines the PSB product prefix, the "BV" view-designating token, and the ACCOUNT_SET_LINES entity, indicating that it is a reporting-facing projection of the account set line table.

Functionally, the view presents a denormalized surface over the underlying account position set line table so that reports, concurrent programs, and integration extracts can read the composition of an account set without directly querying the base transactional table. Each row represents one line within an account set, carrying the include/exclude instruction, ordering information, and the parent account set reference alongside standard audit columns.

Underlying Base Objects

The view text is defined solely over PSB_ACCOUNT_POSITION_SET_LINES (aliased LN), queried with the WITH READ ONLY clause:

  • PSB_ACCOUNT_POSITION_SET_LINES — the single base table referenced. No joins are present; the view is a straight column projection.
  • The WITH READ ONLY qualifier enforces that no DML may be issued against the view, ensuring that account set maintenance occurs only through the supported PSB forms or APIs that write to the base table.

Because column names in the view differ in places from the base table (for example, INCLUDE_OR_EXCLUDE_TYPE is surfaced as INCLUDE_OR_EXCLUDE, and ACCOUNT_POSITION_SET_ID is surfaced as ACCOUNT_SET_ID), the view acts as a stable, renamed interface layer. Queries written against the view remain insulated from the base table's internal naming.

Key Columns

  • INCLUDE_OR_EXCLUDE (base: INCLUDE_OR_EXCLUDE_TYPE) — flags whether the associated account range or position is included in or excluded from the account set. This column is the anchor for the searched term and is central to how account set membership is evaluated.
  • LINE_SEQUENCE_ID — the sequence identifier that orders lines within an account set. Sequence governs the evaluation order when include/exclude rules overlap.
  • ACCOUNT_SET_ID (base: ACCOUNT_POSITION_SET_ID) — foreign key to the parent account position set header; the join key used to group lines under their owning set.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE — the standard EBS WHO audit columns, supporting change tracking and audit reporting.

Note that the metadata does not document additional range or account-flex columns on this view; the columns listed above are the complete projection in the view text.

Common Use Cases and Queries

The primary practical use is to report or extract the include/exclude composition of account sets for budgeting diagnostics and migration audits. A typical query lists all lines of a given account set in evaluation order:

  • Account set composition report — join the view to the account position set header table on ACCOUNT_SET_ID to produce a set-to-line listing.
  • Include/exclude rule audit — filter on INCLUDE_OR_EXCLUDE to enumerate which ranges are included versus excluded for a set.
  • Change tracking — order by LAST_UPDATE_DATE to identify recently modified account set lines.

Illustrative SELECT statements:

SELECT line_sequence_id, include_or_exclude, account_set_id
FROM psbbv_account_set_lines
WHERE account_set_id = :set_id
ORDER BY line_sequence_id;

SELECT include_or_exclude, COUNT(*)
FROM psbbv_account_set_lines
GROUP BY include_or_exclude;

Because PSB is documented as obsolete and the view is not implemented in the reference database, these queries should be validated against the target instance before use. Where the view is absent, equivalent data may reside in the base table PSB_ACCOUNT_POSITION_SET_LINES if it has been deployed, and any replacement must respect the read-only contract of the original view.