Search Results pspbv_enc_lines

Overview

PSPBV_ENC_LINES is a read-only database view within the Oracle E-Business Suite (EBS) Labor Distribution module (product code PSP). It exposes encumbrance line data associated with labor cost encumbrances generated during the Labor Distribution encumbrance accounting process. The view is defined over the base table PSP_ENC_LINES joined to GL_CODE_COMBINATIONS, providing a reporting-friendly representation of encumbrance lines with decoded lookup meanings and code combination details. The "WITH READ ONLY" clause confirms that the view is intended strictly for query and reporting purposes and cannot be used for DML operations. In the Oracle EBS 12.1.1 and 12.2.2 releases, this view supports reconciliation and audit reporting where labor encumbrances, their suspense handling, and accounting distributions must be examined. The search term "suspense_reason_code" corresponds directly to the SUSPENSE_REASON_CODE column exposed by this view, which documents the reason an encumbrance line was routed to a suspense account rather than a valid distribution account.

Underlying Base Objects

According to the documented view text, PSPBV_ENC_LINES is defined over two underlying objects:

• PSP_ENC_LINES (aliased PEL) — the primary base table storing labor encumbrance line records.
• GL_CODE_COMBINATIONS (aliased GCC) — the General Ledger code combination table, joined on PEL.GL_CODE_COMBINATION_ID = GCC.CODE_COMBINATION_ID.

The join to GL_CODE_COMBINATIONS is required so that the view can expose the "_KF:GL_ACCOUNT" key flexfield display value, derived from the GCC segment columns via the SQLGL:GL#:GCC:_CO key flexfield reference. Lookup-derived columns such as the debit/credit flag and encumbrance line type are translated at runtime using Oracle Application Object Library lookup references (_LA:), specifically GL_LOOKUPS (DR_CR) and PSP_LOOKUPS (PSP_ENC_LINE_TYPES). The ETRM metadata states the view is "Not implemented in this database," meaning it may not be deployed in every environment, and no additional base objects beyond those in the view text are documented.

Key Columns

The view exposes the full column set of PSP_ENC_LINES plus two derived columns. Notable columns include:

• ENC_LINE_ID — primary identifier for the encumbrance line.
• ENCUMBRANCE_DATE / ENCUMBRANCE_AMOUNT — date and monetary value of the encumbrance.
• SUSPENSE_ORG_ACCOUNT_ID and SUSPENSE_REASON_CODE — the suspense account used when a valid account could not be derived, and the reason code explaining the suspense condition. SUSPENSE_REASON_CODE is the column most closely matching the user's search term.
• DEFAULT_REASON_CODE — the reason code applied by default for the encumbrance line.
• STATUS_CODE — current processing status of the line.
• ENC_ELEMENT_TYPE_ID, ENC_SUMMARY_LINE_ID, ENC_CONTROL_ID — links to the encumbrance hierarchy.
• GL_PROJECT_FLAG — indicates whether the encumbrance is project-related.
• "_LA:DEBIT_CREDIT_FLAG" and "_LA:ENC_LINE_TYPE" — decoded lookup meanings for the debit/credit indicator and encumbrance line type.
• "_KF:GL_ACCOUNT" — the concatenated GL account flexfield display value from GL_CODE_COMBINATIONS.
• Context columns (PERSON_ID, ASSIGNMENT_ID, AWARD_ID, TASK_ID, PROJECT_ID, EXPENDITURE_TYPE, PAYROLL_ID, TIME_PERIOD_ID) that describe the labor source of the encumbrance.

Common Use Cases and Queries

This view is typically used to report labor distribution encumbrances, investigate suspense postings, and reconcile encumbrance lines to the General Ledger. A representative query to isolate suspense encumbrances is:

• SELECT enc_line_id, encumbrance_date, encumbrance_amount, suspense_reason_code, suspense_org_account_id, default_reason_code, status_code FROM pspbv_enc_lines WHERE suspense_reason_code IS NOT NULL;

A broader audit query joining the decoded GL account is straightforward because the view already exposes "_KF:GL_ACCOUNT":

• SELECT enc_line_id, "_KF:GL_ACCOUNT", "_LA:ENC_LINE_TYPE", encumbrance_amount, suspense_reason_code FROM pspbv_enc_lines WHERE status_code = 'P' ORDER BY encumbrance_date;

Because the view is read-only and pre-joins GL_CODE_COMBINATIONS, it eliminates the need for consumers to reconstruct the account flexfield join themselves. Note that documented metadata lists no referenced base objects beyond the view text, so any additional joining must be performed by the report author using the ID columns provided.