Search Results inv_mthd_code

Overview

APPS.PA_TASK_INV_METHODS_LOV_V is a lookup view in the Oracle E-Business Suite Projects (PA) module. It exposes the list of values for the invoice method attribute used in Project Billing and task-level billing configuration. The view surfaces the set of valid invoice method codes and their user-facing meanings defined in the PA_LOOKUPS lookup set with the lookup type INVOICE_METHOD. In EBS 12.1.1 and 12.2.2, this object is typically consumed by Oracle Forms-based LOV (List of Values) fields and by reporting or integration layers that require a normalized, human-readable list of invoice methods without directly querying the underlying lookup table.

The view functions as a presentation-layer abstraction. Rather than reading PA_LOOKUPS directly and filtering on the lookup type in each query, developers and form definitions reference PA_TASK_INV_METHODS_LOV_V, which already applies the INVOICE_METHOD filter. This reduces duplication of the filter predicate and standardizes the column names exposed to callers.

Underlying Base Objects

The documented metadata identifies the single referenced base object as PA_LOOKUPS. In the EBS data dictionary, PA_LOOKUPS is itself a view (not a base table), which is common for lookup constructs in the PA schema. The definition of PA_TASK_INV_METHODS_LOV_V is:

• SELECT LKP1.LOOKUP_CODE INV_MTHD_CODE, LKP1.MEANING INVOICE_METHOD, LKP1.DESCRIPTION DESCRIPTION FROM PA_LOOKUPS LKP1 WHERE LKP1.LOOKUP_TYPE LIKE 'INVOICE_METHOD'

The join between the view and its base object is therefore a simple, single-source projection with a WHERE filter on LOOKUP_TYPE. Because the view references PA_LOOKUPS and PA_LOOKUPS derives from the core lookup tables (FND_LOOKUP_VALUES and related seed data), changes to lookup codes or meanings flow through immediately. There is no aggregation, no outer join, and no dependency on project or task transaction data; the view is purely definitional.

Key Columns

• INV_MTHD_CODE — Derived from LOOKUP_CODE in PA_LOOKUPS. This is the stored, canonical code value persisted in task or project billing attributes and referenced by downstream logic. Examples of typical invoice method codes include values denoting work, cost, event, and labor based billing, depending on configuration.
• INVOICE_METHOD — Derived from the MEANING column. This is the translated, user-visible label displayed in LOV windows, reports, and user interfaces.
• DESCRIPTION — Derived from the DESCRIPTION column. Provides supplementary explanatory text for the invoice method, frequently used in tooltips, help text, and detailed reporting.

Because the view selects only these three attributes, consumers cannot obtain additional lookup attributes such as start/end dates, enabled flags, or tag from this view; those would require querying PA_LOOKUPS or FND_LOOKUP_VALUES directly.

Common Use Cases and Queries

The primary use case is driving LOV fields on task and project billing forms, where users select an invoice method. Reporting teams also use the view to translate stored invoice method codes into readable labels, and integration layers may reference it to validate that a supplied code is a legitimate invoice method.

A representative query returning all invoice methods is:

• SELECT INV_MTHD_CODE, INVOICE_METHOD, DESCRIPTION FROM APPS.PA_TASK_INV_METHODS_LOV_V ORDER BY INVOICE_METHOD;

To resolve a single code to its meaning, a caller may filter on the code column. Because the predicate compares lookup codes, the query is index-friendly against the underlying lookup structures. For reporting joins, the view is often joined to task-level billing tables on the code column, for example equating a stored invoice method column to INV_MTHD_CODE, in order to display INVOICE_METHOD alongside transaction detail.

Organizations should note that the view reflects only lookup values that exist for the INVOICE_METHOD lookup type at query time. When lookups are end-dated or disabled in the underlying lookup maintenance framework, behavior depends on how PA_LOOKUPS filters them; standard EBS lookup views typically restrict to currently effective, enabled values. Developers should therefore not treat the view as a complete historical record of invoice methods.