Results for “view_line_flag”

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

Overview

PSB_WS_LINES_POSITIONS is a Public Sector Budgeting (PSB) intersection table in Oracle E-Business Suite 12.1.1 and 12.2.2. It is documented as the "matrix between PSB_WORKSHEETS and PSB_WS_POSITION_LINES," meaning it resolves the many-to-many relationship between budgeting worksheets and the position lines they contain. In the PSB module, worksheets aggregate budget data that users review and manipulate, while position lines represent individual budgeted positions. This table records which position lines belong to which worksheet and carries per-worksheet attributes such as freeze and view-line flags.

The PSB product is flagged obsolete in the ETRM documentation, and the table is noted as "Not implemented in this database" in the reference environment. Customers on 12.1.1 or 12.2.2 should treat it as a legacy object of historical or migration interest rather than an actively maintained functional table. Mined from its foreign key structure, the heuristic Data Vault classification for this table is a link, which is a reasonable modeling suggestion: it exists purely to connect two parent entities and stores relationship-level descriptive attributes rather than serving as a standalone hub or satellite.

Key Information Stored

The documented physical schema (ETRM 12.1.1) lists nine columns owned by PSB. The most significant are:

• WORKSHEET_ID — identifies the parent PSB_WORKSHEETS record. Part of the composite primary key PSB_WS_LINES1_PK and a foreign key to PSB_WORKSHEETS.
• POSITION_LINE_ID — identifies the parent PSB_WS_POSITION_LINES record. Also part of the composite primary key and a foreign key to PSB_WS_POSITION_LINES.
• FREEZE_FLAG — relationship-level indicator controlling whether the position line is frozen (protected from modification) within the worksheet context.
• VIEW_LINE_FLAG — indicator governing whether the position line is displayed when the worksheet is viewed.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS Who columns capturing the last change audit trail.
• CREATED_BY, CREATION_DATE — standard EBS Who columns capturing record creation.

There is no single surrogate key: the primary key is the composite (WORKSHEET_ID, POSITION_LINE_ID), which is also enforced by unique index PSB_WS_LINES_POS_U1. Because the unique index mirrors the primary key columns exactly, the primary key itself serves as the business-key candidate — no separate alternate key exists. The two identifier columns therefore function as the natural business key of the link.

Common Use Cases and Queries

Because the object is obsolete in current releases, its principal uses are data migration, historical reporting, and impact analysis during upgrades. A typical pattern is to resolve which position lines are attached to a given worksheet, or to filter by freeze status for audit purposes. For example:

• Listing position lines for a worksheet: SELECT p.POSITION_LINE_ID, p.FREEZE_FLAG, p.VIEW_LINE_FLAG FROM PSB_WS_LINES_POSITIONS p WHERE p.WORKSHEET_ID = :worksheet_id;
• Finding worksheets containing a specific position line: SELECT p.WORKSHEET_ID FROM PSB_WS_LINES_POSITIONS p WHERE p.POSITION_LINE_ID = :position_line_id;
• Auditing frozen or hidden lines: filter on FREEZE_FLAG or VIEW_LINE_FLAG within a worksheet scope.

Contributors such as CREATED_BY, CREATION_DATE, and LAST_UPDATE_DATE support audit and lineage reporting, particularly valuable when reconciling migrated PSB data against legacy extracts.

Related Objects

The following objects are most significant in relation to this table, based on the documented FK and PK relationships:

• PSB_WORKSHEETS — parent entity; joined via PSB_WS_LINES_POSITIONS.WORKSHEET_ID = PSB_WORKSHEETS.WORKSHEET_ID.
• PSB_WS_POSITION_LINES — parent entity; joined via PSB_WS_LINES_POSITIONS.POSITION_LINE_ID = PSB_WS_POSITION_LINES.POSITION_LINE_ID.
• PSB_WORKSHEETS (via PSB_WS_LINES1_PK context) — the composite key enforces worksheet-to-position-line integrity across both parents.

No further dependent views or APIs are documented in the supplied metadata; because the table is marked obsolete and unimplemented, additional references should be confirmed directly against the target instance before relying on them. Given its role as a link, PSB_WS_LINES_POSITIONS has no child tables of its own — it is consumed by the worksheet and position-line entities it connects.