Results for “pa_budget_entry_methods_v”

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

Overview

PA_BUDGET_ENTRY_METHODS_V is an APPS-owned reporting view in the Oracle E-Business Suite Projects (PA) module, valid in releases 12.1.1 and 12.2.2. It exposes the set of currently active budget entry methods that determine how a project budget may be entered, and it decodes two of the underlying lookup-coded columns into their user-facing meanings. The view is a validated, read-only presentation layer: it does not store data, and it applies an effective-date filter at runtime so that only methods active on the current system date are returned.

From a reporting and integration standpoint the view serves as the reference list for budget entry method configuration. Revenue recognition, budgeting, and project performance reports, as well as inbound interfaces and concurrent programs that must validate a budget entry method before writing budget lines, can query this view instead of joining the base table to PA_LOOKUPS manually. Because the view is already restricted to currently effective rows, consumers avoid the date logic that would otherwise be required in every extract.

Underlying Base Objects

The view is defined over two documented objects: PA_BUDGET_ENTRY_METHODS (exposed through a synonym) and PA_LOOKUPS (itself a view). PA_BUDGET_ENTRY_METHODS is the driving table and supplies all attribute columns; PA_LOOKUPS is referenced twice, via aliases PL1 and PL2, to provide decoded meanings. The join to PL1 is restricted to lookup type 'BUDGET ENTRY LEVEL' and matches PBEM.ENTRY_LEVEL_CODE to the lookup code. The join to PL2 is restricted to lookup type 'BUDGET TIME PHASED TYPE' and matches PBEM.TIME_PHASED_TYPE_CODE to the lookup code. The active-row predicate is TRUNC(SYSDATE) BETWEEN PBEM.START_DATE_ACTIVE AND NVL(PBEM.END_DATE_ACTIVE, TRUNC(SYSDATE)), which also makes START_DATE_ACTIVE the effective lower bound and treats a null end date as open-ended. Rows in the base table whose entry level or time phased type code has no matching lookup row are excluded by the inner joins, as are methods that are not yet in effect or have expired.

Key Columns

• CODE — the budget entry method code (BUDGET_ENTRY_METHOD_CODE); the unique key used by budget entry transactions.
• NAME — the descriptive budget entry method name.
• ENTRY_LEVEL_CODE / ENTRY_LEVEL_NAME — the level at which the budget is entered, decoded from lookup type BUDGET ENTRY LEVEL.
• CATEGORIZATION_CODE — the categorization option applied to the budget entry method.
• COST_QUANTITY_FLAG, RAW_COST_FLAG, BURDENED_COST_FLAG — flags indicating whether quantities, raw cost, and burdened cost are entered.
• REV_QUANTITY_FLAG — flag indicating whether revenue quantities are entered; directly relevant to searches on revenue attributes.
• REVENUE_FLAG — indicates whether revenue amounts are entered for the method. This is the column most frequently used to identify revenue-bearing entry methods.
• TIME_PHASED_TYPE_CODE / TIME_PHASED_TYPE_NAME — the time-phasing type, decoded from lookup type BUDGET TIME PHASED TYPE.

Common Use Cases and Queries

The most frequent requirement is to identify which active methods accept revenue, either for report filters or to validate an interface parameter. The following query returns the revenue-enabled methods with their decoded lookups:

SELECT code, name, entry_level_name,
       time_phased_type_name, revenue_flag
  FROM pa_budget_entry_methods_v
 WHERE revenue_flag = 'Y'
 ORDER BY name;

A second pattern enumerates the full control set to confirm which combinations of cost, quantity, and revenue input are permitted:

SELECT code, name, entry_level_code, categorization_code,
       cost_quantity_flag, raw_cost_flag,
       burdened_cost_flag, rev_quantity_flag, revenue_flag
  FROM pa_budget_entry_methods_v;

Because the view already filters on effective dates, it is also suitable as a validation list in PL/SQL or in a Web ADI/interface lookup; a lookup by code such as SELECT name FROM pa_budget_entry_methods_v WHERE code = :p_code will return a row only when the code is currently active and its lookup decodes resolve.