Results for “pa_ci_types_w_finplan_v”

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

Overview

PA_CI_TYPES_W_FINPLAN_V is a read-only Oracle EBS view owned by the APPS schema within the Projects (PA) module. It is designed to expose the subset of capital interest (CI) type definitions that are relevant to financial planning and budgeting activities. In Oracle Projects, capital interest types represent configurable classifications that determine how a capitalized interest transaction affects cost and revenue. This particular view narrows the full set of CI types to those flagged for impact on budget planning, providing a focused, reporting-friendly data set for financial planning integrations, extensions, and custom reports.

The view is validated against both Oracle EBS 12.1.1 and 12.2.2 and is delivered as part of the standard APPS dictionary, making it available to any custom form, concurrent program, BI Publisher report, or OAF extension that needs to reconcile capital interest types with budget planning behavior.

Underlying Base Objects

The view is defined exclusively over a single referenced base object: PA_CI_TYPES_V (itself a view in the APPS schema). The view text performs the following operations against that source:

• Filters on the active date window: SYSDATE BETWEEN CT.START_DATE_ACTIVE AND NVL(CT.END_DATE_ACTIVE, SYSDATE), returning only currently effective CI types.
• Restricts to budget-relevant impact types via CT.IMPACT_BUDGET_TYPE_CODE IN ('EDIT_PLANNED_AMOUNTS', 'DIRECT_COST_ENTRY').
• Projects a derived set of columns, including two computed CASE expressions that collapse multiple flag columns into single COST_IMPACT_FLAG and REVENUE_IMPACT_FLAG indicators.

Because it sits on top of PA_CI_TYPES_V rather than a base table, all propagation of underlying CI type configuration changes flows through to this view automatically without additional maintenance.

Key Columns

• CI_TYPE_ID — Primary identifier for the capital interest type; used as the foreign key in related PA tables.
• CI_TYPE_CLASS_CODE — Classifies the CI type (for example, by functional grouping such as cost or revenue).
• NAME / SHORT_NAME — Descriptive and abbreviated labels presented in LOVs and reports.
• DESCRIPTION — Free-text description of the CI type purpose.
• COST_IMPACT_FLAG — Derived flag, set to 'Y' when any of COST_COL_FLAG, SUPP_COST_REG_FLAG, or DIR_COST_REG_FLAG equals 'Y'; otherwise 'N'. Indicates whether the CI type impacts project cost.
• REVENUE_IMPACT_FLAG — Derived flag, set to 'Y' when either REV_COL_FLAG or DIR_REG_REV_COL_FLAG equals 'Y'; otherwise 'N'. Indicates whether the CI type impacts revenue.

Common Use Cases and Queries

Typical usage centers on financial planning validation, LOV population, and reporting of CI types whose behavior affects planned amounts and direct cost entry.

• Populate a selection list: retrieve currently active, budget-impacting CI types for user selection.

SELECT ci_type_id, name, short_name
FROM   apps.pa_ci_types_w_finplan_v
ORDER  BY name;

• Identify cost-impacting CI types: drive exception reporting where capital interest must flow into cost plans.

SELECT ci_type_id, name
FROM   apps.pa_ci_types_w_finplan_v
WHERE  cost_impact_flag = 'Y';

• Reconcile revenue impact: confirm which CI types affect revenue recognition within financial plans.

SELECT ci_type_id, name, revenue_impact_flag
FROM   apps.pa_ci_types_w_finplan_v
WHERE  revenue_impact_flag = 'Y';

Because the view already enforces the active-date and budget-type filters, integrators avoid having to replicate that logic in custom SQL, reducing the risk of inconsistency with Oracle Projects' delivered planning rules.