Search Results psb_ae_lines_all

Overview

PSB_AE_LINES_ALL is a table within the Public Sector Budgeting (PSB) product family of Oracle E-Business Suite, documented across releases 12.1.1 and 12.2.2. The ETRM metadata describes this object simply as "Accounting entry lines," which places it as the transactional detail layer beneath a corresponding header entity. In the PSB accounting-entry data model, the header (PSB_AE_HEADERS_ALL) carries the document-level context of an accounting entry batch, while PSB_AE_LINES_ALL stores the individual debit and credit lines that make up that entry. The "_ALL" suffix follows the standard EBS multi-organization convention, indicating the table is partitioned or filtered by operating unit through an ORG_ID column in typical deployments.

An important caveat applies: the ETRM metadata explicitly records "Not implemented in this database" for this object in the documented instance. PSB itself is flagged as "Obsolete" in the product classification. This means the table exists in the data dictionary and in the historical PSB code base, but may not be instantiated in every EBS environment, particularly newer or Oracle Public Sector-focused installations where the functionality has been superseded. Consultants encountering this object should first verify its physical presence before designing dependencies on it.

The heuristic Data Vault classification is satellite-leaning. This classification is derived from the foreign key topology: the table holds a surrogate primary key and points outward to a single parent header, making it a descriptive detail satellite hanging off the PSB_AE_HEADERS_ALL hub rather than a hub itself or a link resolving many-to-many relationships. Modeling this as a satellite is a reasonable suggestion where a Data Vault representation is desired.

Key Information Stored

Because the documented metadata exposes only a limited column set, the following list distinguishes confirmed columns from their inferred roles:

• AE_LINE_ID — The surrogate primary key, enforced by PSB_AE_LINES_ALL_PK. This is a system-generated identifier with no business meaning; it is the FK target for any child tables.
• AE_HEADER_ID — The foreign key to PSB_AE_HEADERS_ALL, linking each line to its parent accounting entry document. This is the primary join column and the most heavily used predicate in queries against this table.

Beyond these two documented columns, the table in a standard PSB implementation would be expected to carry the accounting distribution attributes typical of a line table: a line number for sequencing within the header, account combination identifiers (code combination IDs for the debit or credit account), entered and accounted amounts, currency codes, and descriptive text. None of these are confirmed in the ETRM documentation excerpt, so they should be verified against the actual database before use in production SQL.

No unique business-key index is documented. The only uniqueness constraint is the surrogate primary key; any business-key candidate would need to be derived from the combination of AE_HEADER_ID plus a line number, which is not documented here.

Common Use Cases and Queries

The principal use case is reconstructing the full detail of an accounting entry by joining lines to their header. A representative query pattern:

SELECT l.ae_line_id, l.ae_header_id, h.*
FROM   psb_ae_lines_all l,
       psb_ae_headers_all h
WHERE  l.ae_header_id = h.ae_header_id
AND    h.ae_header_id = :p_header_id;

Reporting scenarios include auditing accounting entry composition, reconciling PSB-derived budget entries against General Ledger balances, and extracting line-level detail for downstream ETL or data-warehouse loads. Because PSB is obsolete, a common practical use is migration or archival: extracting historical PSB accounting entries before decommissioning the module, and mapping them to GL or to a successor budgeting tool. When querying multi-org environments, filter on the operating unit column if the table is partitioned by ORG_ID, and always confirm the table is populated in the target instance given the "not implemented" notation.

Related Objects

• PSB_AE_HEADERS_ALL — The immediate parent; joined on PSB_AE_LINES_ALL.AE_HEADER_ID = PSB_AE_HEADERS_ALL.AE_HEADER_ID. This is the only FK relationship documented in the ETRM metadata.
• GL_JE_LINES / GL_JE_HEADERS — The General Ledger journal line and header tables, the likely downstream destination for accounting entries originated in PSB budgeting processes.
• GL_CODE_COMBINATIONS — Provides the account segment descriptions for any code combination ID referenced on the line.
• PSB_AE_HEADERS_ALL (PK) — The AE_HEADER_ID primary key on the header serves as the referential anchor for this satellite table.
• PSB budget/accounting entry API or concurrent programs — The PSB entry-generation logic that inserts header and line rows; these programs are the object's primary write path.

Given the obsolete status of PSB, dependency analysis should focus on identifying any remaining customizations or reports that still reference this table so they can be remediated ahead of module retirement.