Search Results plan_adjustable_flag

Overview

PA_AMOUNT_TYPES_VL is a seeded, read-only view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Projects (PA) product family and exposes the set of implementation-defined amount types used throughout the Projects suite to classify and control monetary values carried against project transactions, budgets, and adjustments. Amount types are reference data rather than transactional data; they exist so that Oracle Projects can distinguish, for example, a raw cost amount from a burdened cost amount or a revenue amount, and can decide which of those amounts is eligible for planning adjustments.

Because the view carries the _VL suffix, it is a translated ("VL" = view with language) view. It joins the base table to its translation table and filters on the session language, returning exactly one row per amount type in the language of the current user session. This design makes the view the appropriate source for reports, concurrent program extracts, BI Publisher data templates, and integration interfaces that must present amount type names in the user's own language without embedding language-specific logic in the calling code. The object is documented as VALID in the ETRM repository for 12.2.2, and its column set is stable across the 12.1.1 and 12.2.2 releases.

Underlying Base Objects

The view is defined over two synonymous references to Projects base tables:

• PA_AMOUNT_TYPES_B — the base (non-translated) table holding the language-independent attributes of each amount type, including its identifier, code, class, audit columns, and the two planning-adjustment flags.
• PA_AMOUNT_TYPES_TL — the translation table holding the language-dependent amount type name, keyed by AMOUNT_TYPE_ID and LANGUAGE.

The view text joins the two on AMOUNT_TYPE_ID and restricts the translation rows with T.LANGUAGE = USERENV('LANG'), so that only the name for the caller's session language is returned. It also projects B.ROWID as ROW_ID, which gives downstream tools a stable row identifier for the underlying base row. The view is a pure projection and join; it adds no filtering of business rows and no derived columns, so its cardinality equals the number of defined amount types.

Key Columns

• ROW_ID — the ROWID of the corresponding row in PA_AMOUNT_TYPES_B, useful as a surrogate key in reporting extracts.
• AMOUNT_TYPE_ID — the internal primary key of the amount type; the value stored on transactional and budgeting tables that reference an amount type.
• AMOUNT_TYPE_CODE — the user-visible, language-independent short code for the amount type, commonly used as the join or lookup value in interfaces.
• AMOUNT_TYPE_CLASS — classifies the amount type into one of the functional categories recognized by Oracle Projects (for example, raw cost, burdened cost, or revenue). It drives how the amount is treated in costing and summarization logic.
• AMOUNT_TYPE_NAME — the translated display name, sourced from PA_AMOUNT_TYPES_TL and filtered to the session language.
• PLAN_ADJUSTABLE_FLAG — indicates whether amounts of this type can be adjusted within project planning.
• PLAN_ADJ_AMOUNT_FLAG — indicates whether the amount type is itself used as a planning adjustment amount.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN, carried from the base table for change tracking and audit reporting.

Common Use Cases and Queries

Typical uses include building a value set or LOV over available amount types, resolving an AMOUNT_TYPE_ID seen on a transaction table into a printable name, and driving conditional logic in extracts based on AMOUNT_TYPE_CLASS or the planning flags.

• List all amount types in the user's language:

  SELECT amount_type_id, amount_type_code, amount_type_name, amount_type_class
  FROM   apps.pa_amount_types_vl
  ORDER BY amount_type_code;

• Resolve identifiers found on a transaction table:

  SELECT t.project_id, t.amount_type_id, a.amount_type_name
  FROM   pa_transaction_interface t, apps.pa_amount_types_vl a
  WHERE  t.amount_type_id = a.amount_type_id;

• Identify amount types eligible for planning adjustments:

  SELECT amount_type_code, amount_type_name
  FROM   apps.pa_amount_types_vl
  WHERE  plan_adjustable_flag = 'Y';

Because the view resolves the language at query time, callers should never hard-code a language predicate; that would defeat the purpose of the VL layer. Reports that require all languages simultaneously must query PA_AMOUNT_TYPES_TL directly instead. As with any APPS-owned object, grants and synonyms must be in place for custom schemas, and the view should be treated as reference data that is queried but never modified directly.