Results for “pa_adjust_type_v”

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

Overview

PA_ADJUST_TYPE_V is a Projects (PA) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes configuration flags that govern how a project's financial plan amounts are adjusted or burdened during cost, revenue, and quantity processing. Specifically, the view joins financial plan amount sets, budget versions, and project financial plan options to return adjustment-type indicators such as BURDEN_RATE_FLAG, COST_RATE_FLAG, BILL_RATE_FLAG, REVENUE_QTY_FLAG, ALL_QTY_FLAG, and COST_QTY_FLAG.

The view plays a supporting role in reporting and integration, allowing users and external systems to inspect which rate and quantity adjustment behaviors are enabled for a given budget version of a project. Because it surfaces the BILL_RATE_FLAG — the column most commonly searched by implementers — it is frequently referenced when diagnosing whether bill rates are applied to a plan version. In 12.2.2 the definition is documented in ETRM, and the object remains VALID across both the 12.1.1 and 12.2.2 release lines.

Underlying Base Objects

The view is defined over three base objects, all referenced through APPS synonyms:

• PA_FIN_PLAN_AMOUNT_SETS (alias A) — supplies the rate and quantity adjustment flags, including BURDEN_RATE_FLAG, COST_RATE_FLAG, BILL_RATE_FLAG, REVENUE_QTY_FLAG, ALL_QTY_FLAG, and COST_QTY_FLAG.
• PA_BUDGET_VERSIONS (alias B) — supplies BUDGET_VERSION_ID and links a project and financial plan type to a specific budget version.
• PA_PROJ_FP_OPTIONS (alias C) — supplies FIN_PLAN_PREFERENCE_CODE, TRACK_WORKPLAN_COSTS_FLAG, and PROJECT_ID, and drives the join through FIN_PLAN_TYPE_ID and FIN_PLAN_VERSION_ID.

The join restricts results to rows where the financial plan option level code equals 'PLAN_VERSION' and where the amount set is resolved through NVL(C.ALL_AMOUNT_SET_ID, NVL(C.COST_AMOUNT_SET_ID, C.REVENUE_AMOUNT_SET_ID)). This precedence means the ALL amount set takes priority, falling back to COST and then REVENUE amount sets. Consequently, the flags returned reflect the amount set actually applied at the plan version level.

Key Columns

• FIN_PLAN_PREFERENCE_CODE — the financial plan preference associated with the plan option.
• BURDEN_RATE_FLAG — indicates whether burden rates apply to the amount set.
• COST_RATE_FLAG — indicates whether cost rates apply.
• BILL_RATE_FLAG — indicates whether bill rates are applied; the primary column of interest for billing rate configuration checks.
• REVENUE_QTY_FLAG — indicates whether revenue quantities are adjusted.
• ALL_QTY_FLAG — indicates whether all quantity types are adjusted.
• COST_QTY_FLAG — indicates whether cost quantities are adjusted.
• BUDGET_VERSION_ID — the budget version to which the flags pertain.
• TRACK_WORKPLAN_COSTS_FLAG — whether workplan costs are tracked.
• PROJECT_ID — the project identifier.

Common Use Cases and Queries

Typical uses include validating bill rate configuration for a project's budget version, auditing adjustment flags across financial plans, and feeding downstream integrations that must know whether quantities or rates are burdened. A common query filters by project and budget version:

• SELECT project_id, budget_version_id, bill_rate_flag, cost_rate_flag, burden_rate_flag FROM pa_adjust_type_v WHERE project_id = :p_project_id;
• SELECT budget_version_id, bill_rate_flag FROM pa_adjust_type_v WHERE bill_rate_flag = 'Y';
• Joining back to PA_PROJECTS or PA_BUDGET_VERSIONS to enrich reporting on financial plan setup.

Because the view is read-only and defined in APPS, it can be queried directly in reports, BI Publisher data models, and custom concurrent programs without invoking PL/SQL APIs.