Search Results raw_cost_flag




Overview
Explore in AI Chat

Overview

APPS.PA_ALLOC_BUDGET_ENTRY_METHOD_V is a reporting and validation view in Oracle EBS Project Accounting (Oracle Projects). It exposes the set of budget entry methods that are currently active and that support the entry of at least one monetary or quantity measure — cost quantities, raw costs, or burdened costs. The view is defined on the PA_BUDGET_ENTRY_METHODS table and filters rows by both functional capability and effective dating, returning only methods where the current system date falls within the method's active date range.

In Oracle EBS 12.1.1 and 12.2.2, budget entry methods govern how budgets are captured for a project or project template. The three flags referenced in the view — COST_QUANTITY_FLAG, RAW_COST_FLAG, and BURDENED_COST_FLAG — identify which budget line types are permitted for a given entry method. Because the view applies an OR condition across these flags, any method that enables cost quantities, raw costs, or burdened costs is returned. The view is therefore intended to present a complete, date-valid list of usable entry methods for allocation and budgeting purposes, rather than the full contents of the underlying setup table.

Underlying Base Objects

The view is defined exclusively over a single base object, PA_BUDGET_ENTRY_METHODS, referenced through an APPS synonym. No joins to other tables are present in the supplied view text. All filtering is performed against columns of PA_BUDGET_ENTRY_METHODS, including the three capability flags and the standard effective-dating columns START_DATE_ACTIVE and END_DATE_ACTIVE.

The effective-dating predicate is notable: the view compares TRUNC(SYSDATE) against TRUNC(START_DATE_ACTIVE) and TRUNC(NVL(END_DATE_ACTIVE, SYSDATE)). This means methods with a null end date are treated as open-ended and remain visible, while methods whose end date precedes the current day are excluded. This behavior aligns the view with the standard Oracle Projects convention of filtering date-effective setup data at query time rather than relying on a separate active-flag column.

Key Columns

  • BUDGET_ENTRY_METHOD_CODE — the unique identifier for the budget entry method, used as the primary key reference in project and template setup.
  • BUDGET_ENTRY_METHOD — the user-facing name or description of the entry method.
  • ENTRY_LEVEL_CODE — indicates the level at which budget entries are made, such as project or task level.
  • CATEGORIZATION_CODE — defines whether the method is categorized, controlling whether resources are grouped into cost categories.
  • COST_QUANTITY_FLAG — when set to 'Y', permits budget entry in cost quantities (units of measure) in addition to monetary amounts; this is the column of greatest interest in the supplied search context.
  • RAW_COST_FLAG — when set to 'Y', permits entry of raw, unburdened costs.
  • BURDENED_COST_FLAG — when set to 'Y', permits entry of burdened costs inclusive of indirect components.
  • TIME_PHASED_TYPE_CODE — specifies whether the budget is time-phased and the phasing convention applied.

Common Use Cases and Queries

The view is commonly used in LOV (list of values) queries, concurrent program parameters, and custom reporting where only capable, currently effective budget entry methods should be selectable. It is also used to audit which methods permit cost quantity entry, which is directly relevant to searches on COST_QUANTITY_FLAG.

The following query lists all methods that permit cost quantity entry:

  • SELECT budget_entry_method_code, budget_entry_method, cost_quantity_flag, raw_cost_flag, burdened_cost_flag FROM apps.pa_alloc_budget_entry_method_v WHERE cost_quantity_flag = 'Y';

A broader query retrieves all methods supporting monetary entry:

  • SELECT budget_entry_method_code, budget_entry_method, time_phased_type_code FROM apps.pa_alloc_budget_entry_method_v WHERE raw_cost_flag = 'Y' OR burdened_cost_flag = 'Y';

When joining to project setup tables such as PA_PROJECTS or PA_BUDGET_TYPES, the view should be keyed on BUDGET_ENTRY_METHOD_CODE. Because the view already enforces effective dating, consumers do not need to reapply the start and end date predicates, though additional filtering by ENTRY_LEVEL_CODE or CATEGORIZATION_CODE may be applied to narrow results to a specific budgeting scenario.