Search Results invoice_method_m

Overview

APPS.PA_TASK_BILLING_INFO_V is a supplementary database view in the Oracle E-Business Suite Projects (PA) module. In the context of the query term "invoice_method_m," this view is the canonical source for the invoice method code and its translated meaning at the task level for a given project. The view exposes the billing attributes associated with project tasks, specifically the revenue accrual method and invoice method, together with their decoded lookup meanings. The column INVOICE_METHOD_M provides the user-facing description corresponding to the INVOICE_METHOD code, which is precisely the identifier a user would search on when resolving what an invoice method value represents on a task.

The view type is documented in ETRM as a supplementary view used to simplify forms coding. Oracle explicitly warns that this view is not recommended for direct querying or data alteration and that it may change dramatically in subsequent minor or major releases. Accordingly, it should be treated as an internal, forms-oriented construct rather than a stable integration interface. Status is recorded as VALID, and the FND Design Data reference is PA.PA_TASK_BILLING_INFO_V.

Underlying Base Objects

The documented dependency list for APPS.PA_TASK_BILLING_INFO_V identifies two referenced base objects within the APPS schema:

• PA_TASKS (SYNONYM) — the tasks table that supplies the task and project identifiers (TASK_ID, PROJECT_ID) as well as the stored code columns.
• PA_LOOKUPS (VIEW) — the lookup view used to resolve the code columns into their meanings, populating REVENUE_ACCRUAL_METHOD_M and INVOICE_METHOD_M.

The view is not referenced by any other database object, confirming its role as a terminal, presentation-layer construct consumed by forms rather than a shared dependency. The join between PA_TASKS and PA_LOOKUPS is what allows the view to return both the raw lookup code (INVOICE_METHOD) and the decoded meaning (INVOICE_METHOD_M) in a single row.

Key Columns

• ROW_ID (ROWID) — Identifier for the row; the physical row address of the underlying task record.
• TASK_ID (NUMBER) — Identifier for the task.
• PROJECT_ID (NUMBER) — Identifier for the project to which the task belongs.
• REVENUE_ACCRUAL_METHOD (VARCHAR2) — The Revenue Accrual Method code stored against the task.
• REVENUE_ACCRUAL_METHOD_M (VARCHAR2) — The Revenue Accrual Method meaning, decoded from the code.
• INVOICE_METHOD (VARCHAR2) — The Invoice Method code stored against the task.
• INVOICE_METHOD_M (VARCHAR2) — The Invoice Method meaning. This is the column sought by the user term "invoice_method_m" and returns the descriptive invoice method associated with the task.

Common Use Cases and Queries

The principal use case is resolving the invoice method and revenue accrual method for tasks, particularly to obtain the human-readable INVOICE_METHOD_M description alongside the INVOICE_METHOD code. Because Oracle advises against querying this view directly, the recommended practice for reporting is to reproduce its logic against PA_TASKS and PA_LOOKUPS, or to use a supported public view. Where direct reference is unavoidable in a development or diagnostic context, the documented query text is:

• SELECT ROW_ID, TASK_ID, REVENUE_ACCRUAL_METHOD, REVENUE_ACCRUAL_METHOD_M, INVOICE_METHOD, INVOICE_METHOD_M, PROJECT_ID FROM APPS.PA_TASK_BILLING_INFO_V;

Filtering on PROJECT_ID or TASK_ID narrows results to a specific engagement, while filtering on INVOICE_METHOD_M supports lookup-driven searches for the invoice method description. Given the documented volatility warning, any dependency on this view should be reviewed against the target release during upgrades between 12.1.1 and 12.2.2.