Results for “pending_projfunc_inv_amount”

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

Overview

PA_PROJ_BILLING_DETAIL_VIEW is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the Projects (PA) product family. It is documented as the base view used to report billing status detail for projects. The view consolidates project-level billing attributes with draft invoice information, producing a single denormalized result set suitable for inquiry screens, concurrent reporting programs, and downstream integrations that require visibility into a project's current billing posture.

The view carries the status VALID in ETRM 12.2.2 and is also available in 12.1.1. Its structure is driven by a UNION ALL of two branches, both restricted to projects whose status permits the GENERATE_INV action, whose project type is flagged as direct-billed (DIRECT_FLAG = 'Y'), and whose project type organization matches the project organization. The first branch joins to PA_DRAFT_INVOICES to surface the most recently released draft invoice for each project; the second branch returns the project even where no released invoice number exists, supplying NULL invoice attributes. This design ensures every billable direct project appears exactly once, regardless of whether invoicing has begun.

Underlying Base Objects

The documented referenced base objects are PA_BILLING_CYCLES_PKG (PL/SQL package), PA_DRAFT_INVOICES, PA_DRAFT_INVOICE_ITEMS, PA_DRAFT_REVENUES, PA_DRAFT_REVENUE_ITEMS, PA_EVENTS, PA_PROJECTS, PA_PROJECTS_ALL, PA_PROJECT_TYPES_ALL, and PA_PROJECT_UTILS. The visible view text references the PL/SQL package functions PA_BILLING_CYCLES_PKG.GET_NEXT_BILLING_DATE and GET_LAST_RELEASED_INVOICE_NUM, and the utility function PA_PROJECT_UTILS.CHECK_PRJ_STUS_ACTION_ALLOWED. Base tables PA_PROJECTS_ALL, PA_PROJECT_TYPES_ALL, and PA_DRAFT_INVOICES are accessed through public synonyms. The additional referenced synonyms (PA_DRAFT_INVOICE_ITEMS, PA_DRAFT_REVENUES, PA_DRAFT_REVENUE_ITEMS, PA_EVENTS, PA_PROJECTS) reflect the broader object dependency tree registered for the view, supporting revenue and event-related billing detail.

Key Columns

• Invoice method indicator — a DECODE on P.INVOICE_METHOD returning 'EVENT' for event-based billing and 'WORK' otherwise.
• PROJECT_ID, SEGMENT1, NAME — project identifier, number, and name from PA_PROJECTS_ALL.
• Retention accounting flag — NVL(RETN_ACCOUNTING_FLAG,'N'), indicating whether retention accounting applies.
• DRAFT_INVOICE_NUM, INVOICE_DATE, BILL_THROUGH_DATE — converted to character, drawn from the last released draft invoice where one exists.
• Days elapsed — ROUND(TRUNC(SYSDATE) − NVL(INVOICE_DATE, project start or creation date)), a measure of aging since the last invoice.
• Next billing date — returned by PA_BILLING_CYCLES_PKG.GET_NEXT_BILLING_DATE using billing cycle, offset, and bill-through date.
• ENABLE_TOP_TASK_INV_MTH_FLAG — indicates whether the top task invoice method is enabled for the project.
• Placeholder numeric columns — ten literal zero columns retained for positional compatibility with report layouts.

Common Use Cases and Queries

The view is typically queried to produce billing status dashboards, identify projects nearing their next billing date, and reconcile released invoice activity against project setup.

• Projects with an active released invoice and aging detail.
• Projects awaiting their first invoice (NULL invoice columns).
• Event-based versus work-based billing segmentation.

Sample query:

SELECT PROJECT_ID, SEGMENT1, NAME, DRAFT_INVOICE_NUM, INVOICE_DATE, BILL_THROUGH_DATE, NEXT_BILLING_DATE FROM APPS.PA_PROJ_BILLING_DETAIL_VIEW WHERE INVOICE_METHOD_INDICATOR = 'WORK' ORDER BY PROJECT_ID;

Because the view embeds PL/SQL functions in its SELECT list and predicates, performance depends on the underlying function calls; filtering by PROJECT_ID or organization is advisable in high-volume reporting environments.