Search Results entry_level_code




Overview
Explore in AI Chat

Overview

The PA_ALLOC_BUDGET_ENTRY_METHOD_V view is a Projects (PA) module object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a filtered, date-effective subset of the budget entry methods defined in Oracle Projects, exposing only those methods that are currently active and that support at least one cost basis — quantity, raw cost, or burdened cost. The view is commonly surfaced in Oracle Forms LOVs, concurrent program parameters, and third-party integrations that must present a user with a valid list of budget entry methods when allocating or entering budget amounts. The user's search term, budget_entry_method_code, corresponds directly to the first and most important column in this view and is the primary join key against many downstream budgeting and allocation tables.

Underlying Base Objects

The view is defined over a single base object, PA_BUDGET_ENTRY_METHODS, which is referenced via a public synonym in the APPS schema. The view executes a deterministic filter against that table:

Because these predicates are embedded in the view text, no additional WHERE clause is required to enforce active-status filtering. Callers that require historical or inactive entry methods must query PA_BUDGET_ENTRY_METHODS directly. The view is read-only, non-updatable in practice, and inherits the security profile of its owning schema.

Key Columns

  • BUDGET_ENTRY_METHOD_CODE — The unique short code identifying the budget entry method; the primary key and the most commonly referenced column.
  • BUDGET_ENTRY_METHOD — The descriptive name shown to end users.
  • ENTRY_LEVEL_CODE — Indicates the level at which budget entries are accepted (for example, project, task, or resource).
  • CATEGORIZATION_CODE — Identifies the categorization rule applied when budget lines are entered.
  • COST_QUANTITY_FLAG, RAW_COST_FLAG, BURDENED_COST_FLAG — Y/N flags indicating which cost bases the method permits; at least one must be 'Y' for the row to appear.
  • TIME_PHASED_TYPE_CODE — Indicates whether the method permits time-phased, non-time-phased, or both styles of entry.

Common Use Cases and Queries

Typical uses include LOV population on budget entry forms, validation of user-supplied codes before insert into allocation or budget interface tables, and reference lookups in extracts. Because active-date and cost-flag filtering are baked in, queries are typically simple:

  • Select all currently active methods:
    SELECT BUDGET_ENTRY_METHOD_CODE, BUDGET_ENTRY_METHOD
    FROM APPS.PA_ALLOC_BUDGET_ENTRY_METHOD_V
    ORDER BY BUDGET_ENTRY_METHOD;
  • Restrict to methods that support burdened cost:
    SELECT BUDGET_ENTRY_METHOD_CODE, BUDGET_ENTRY_METHOD
    FROM APPS.PA_ALLOC_BUDGET_ENTRY_METHOD_V
    WHERE BURDENED_COST_FLAG = 'Y';
  • Validate a specific code supplied by an interface file:
    SELECT 1 FROM APPS.PA_ALLOC_BUDGET_ENTRY_METHOD_V
    WHERE BUDGET_ENTRY_METHOD_CODE = :p_code;
  • Join to budget or allocation facts on BUDGET_ENTRY_METHOD_CODE to attach descriptive attribute columns to reporting output.

In all cases, the view provides a safe, pre-filtered source suitable for both online and batch consumption.