Results for “pabv_asset_lines”

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

Overview

PABV_ASSET_LINES is an Oracle EBS Projects (PA) view owned by the APPS schema and delivered as a valid database object in both release 12.1.1 and 12.2.2. It is a "Business View" (the "BV" naming convention) whose documentation is marked as retrofitted in the ETRM repository. The view exposes project asset line information drawn from the underlying transaction table PA_PROJECT_ASSET_LINES_ALL, presenting one row per project asset line together with cost, descriptive, and general ledger accounting attributes. Its role in Oracle EBS reporting and integration is to provide a secure, read-only projection of asset line data that can be referenced by Oracle Business Intelligence, custom reports, discoverer worksheets, and interface programs without exposing the full set of columns and auditing fields present on the base table.

The definition terminates with a WITH READ ONLY clause, so the view can be used strictly for query and reporting purposes; no DML may be issued against it. The presence of the ORG_ID security predicate ('_SEC:ORG_ID' IS NOT NULL) denotes that the view participates in Oracle's multi-organization access control model, restricting visibility to organizations to which the querying responsibility has been granted. Users searching on "gl_date" will find that this accounting date column is one of the view's principal columns, indicating that the view is frequently queried for asset line transactions by their general ledger date.

Underlying Base Objects

The view is defined over a single documented base object, the synonym PA_PROJECT_ASSET_LINES_ALL, which resolves to the APPS-owned base table that stores project asset line detail including capitalized and CIP-related cost information. The relationship is a straightforward projection: every column in PABV_ASSET_LINES maps to a corresponding column in PA_PROJECT_ASSET_LINES_ALL, with the exception of the lookup display columns, which are derived through Oracle lookups rather than stored directly on the base table.

• PA_PROJECT_ASSET_LINES_ALL (via synonym) — the sole documented referenced base object, providing project asset line identifiers, asset cost amounts, GL date, task and asset category references, CIP code combination, and organization/audit columns.

The view filters rows through the organization security predicate rather than through an unconditional WHERE clause on business data, so the row population mirrors the base table as constrained by the querying user's organization access.

Key Columns

• PROJECT_ASSET_LINE_ID — unique identifier for the project asset line; primary key of the underlying record.
• ORIGINAL_ASSET_COST / CURRENT_ASSET_COST — the original capitalized cost of the asset line and its current cost after adjustments.
• DESCRIPTION — free-text description of the asset line.
• GL_DATE — the general ledger date associated with the asset line, used for accounting period determination; this is the column most relevant to users searching on that term.
• _LA:TRANSFER_STATUS — a lookup-derived column resolving the transfer status code to its meaning via the PA_LOOKUPS lookup type "TRANSFER STATUS".
• TRANSFER_REJECTION_REASON — reason text recorded when an asset line transfer to fixed assets is rejected.
• _LA:AMORTIZE_FLAG — lookup-derived column resolving the amortize flag to Yes/No meaning via the FND_LOOKUPS YES_NO lookup type.
• PROJECT_ASSET_ID, TASK_ID, ASSET_CATEGORY_ID — foreign references to the project asset, task, and asset category.
• CIP_CCID — code combination identifier for the construction-in-process account.
• REV_PROJ_ASSET_LINE_ID — reference to the reversing project asset line, where applicable.
• ORG_ID — operating unit/organization identifier used by the security predicate.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard audit columns.
• INVOICE_ID — reference to the originating invoice, where the asset line derives from an invoice.

Common Use Cases and Queries

Typical scenarios include reconciling capitalized project costs by GL date, reviewing asset lines pending transfer to Oracle Assets, and auditing rejected transfers with their rejection reasons. Because the view is read-only and organization-secured, it is well suited to end-user reporting within a specific operating unit.

For example, to list asset lines for a given GL date range:

• SELECT project_asset_line_id, gl_date, original_asset_cost, current_asset_cost, description FROM apps.pabv_asset_lines WHERE gl_date BETWEEN :start_date AND :end_date AND org_id = :org_id ORDER BY gl_date;

To examine transfer status for capitalized lines:

• SELECT project_asset_line_id, gl_date, "_LA:TRANSFER_STATUS" transfer_status, transfer_rejection_reason FROM apps.pabv_asset_lines WHERE "_LA:AMORTIZE_FLAG" = 'Yes' AND org_id = :org_id;

Joins to PA_PROJECTS and PA_TASKS are commonly added to obtain project and task names, using PROJECT_ASSET_ID and TASK_ID respectively. All queries remain subject to the organization security predicate, ensuring results conform to the responsibility's organization access.