Search Results revenue_accrual_method




Overview
Explore in AI Chat

Overview

PA_TASK_BILLING_INFO_V is a reporting and integration view owned by the APPS schema within the Oracle Projects (PA) module of Oracle E-Business Suite. It is documented as VALID in both 12.1.1 and 12.2.2 and is registered in the E-Business Suite Technical Reference Manual (ETRM). Its stated purpose is to provide billing information for tasks: specifically, the view consolidates the billing-related control attributes stored on a project task — the revenue accrual method and the invoice method — and resolves their internal lookup codes into user-facing lookup meanings.

Because the base PA_TASKS table stores revenue accrual and invoice methods as short lookup codes, a direct query against PA_TASKS returns values that are not self-describing. PA_TASK_BILLING_INFO_V joins PA_TASKS to PA_LOOKUPS twice, decoding the accrual method against the lookup type 'REVENUE ACCRUAL METHOD' and the invoice method against 'INVOICE METHOD'. The view therefore serves as a convenient, denormalized source for reporting on task-level billing behavior, for feeding downstream integrations, and for ad hoc investigation of why a given task accrues revenue or generates invoices in a particular way. The presence of REVENUE_ACCRUAL_METHOD among the exposed columns explains why the view is frequently surfaced in searches for that term: it is one of the few delivered objects that presents both the stored code and its translated meaning for task-level revenue accrual.

Underlying Base Objects

Per the documented view text, PA_TASK_BILLING_INFO_V is defined with a three-table join:

  • PA_TASKS (SYNONYM) — the primary source of task data, aliased as PT. All task identifiers, project identifiers, and method codes originate here. The view exposes PT.ROWID, meaning the underlying row identifier is carried through and can be used for row-level reference.
  • PA_LOOKUPS (VIEW, aliased LKP1) — joined on LOOKUP_TYPE = 'REVENUE ACCRUAL METHOD' and LOOKUP_CODE = PT.REVENUE_ACCRUAL_METHOD, supplying the MEANING for the accrual method.
  • PA_LOOKUPS (VIEW, aliased LKP2) — joined on LOOKUP_TYPE = 'INVOICE METHOD' and LOOKUP_CODE = PT.INVOICE_METHOD, supplying the MEANING for the invoice method.

Both joins are inner joins constrained by lookup type, so a task whose revenue accrual method or invoice method code has no corresponding lookup entry will not appear in the view. Similarly, because the lookup joins are inner, tasks with null billing methods are excluded. This behavior matters when reconciling counts between PA_TASKS and the view.

Key Columns

  • ROW_ID — the ROWID of the corresponding PA_TASKS row; useful for direct row access and for correlating back to the base task record.
  • TASK_ID — the unique identifier of the task; the primary correlation key to PA_TASKS and to other task-level views and tables.
  • REVENUE_ACCRUAL_METHOD — the lookup code stored on PA_TASKS that determines how revenue is accrued for the task.
  • REVENUE_ACCRUAL_METHOD_M — the translated MEANING of the revenue accrual method from PA_LOOKUPS, providing the descriptive value for reporting.
  • INVOICE_METHOD — the lookup code on PA_TASKS that governs how the task is invoiced.
  • INVOICE_METHOD_M — the translated MEANING of the invoice method from PA_LOOKUPS.
  • PROJECT_ID — the project to which the task belongs, enabling aggregation at the project level.

Common Use Cases and Queries

Typical scenarios include auditing task-level billing configuration, validating that revenue accrual methods conform to corporate policy, driving reports that display human-readable method descriptions, and supplying integration extracts.

List all tasks and their billing methods for a project:

SELECT task_id,
       revenue_accrual_method,
       revenue_accrual_method_m,
       invoice_method,
       invoice_method_m
FROM   apps.pa_task_billing_info_v
WHERE  project_id = :project_id;

Identify tasks by accrual method across projects:

SELECT project_id, task_id, revenue_accrual_method_m
FROM   apps.pa_task_billing_info_v
WHERE  revenue_accrual_method = 'FNLT'
ORDER BY project_id, task_id;

Summarize task counts by accrual and invoice method:

SELECT revenue_accrual_method_m, invoice_method_m, COUNT(*) task_count
FROM   apps.pa_task_billing_info_v
GROUP BY revenue_accrual_method_m, invoice_method_m;