Results for “direct_cost_entry”

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

Overview

APPS.PA_CI_TYPES_W_FINPLAN_V is a reporting view in the Oracle EBS Projects (PA) module that exposes control item (CI) type definitions that are eligible for use within financial plan structures. In Oracle Projects terminology, "control items" represent user-defined line classifications — such as labor, travel, or material categories — that determine how costs and revenue are budgeted, collected, and summarized against a project. This view represents the intersection of control item type configuration with financial plan usage, restricting the returned rows to those CI types flagged as applicable to financial plan layouts.

The view is classified as Internal with the prominent Oracle warning that it is for Oracle Internal Use Only and is not supported for direct customer access except through standard Oracle Applications programs. Its FINPLAN-oriented naming and dependency on PA_CI_IMPACT_TYPE_USAGE confirm that it serves the financial plan configuration screens and the control item validation logic rather than ad hoc reporting. For users searching on cost_impact_flag, this view is directly relevant: it is one of the few published structures that surfaces the COST_IMPACT_FLAG attribute together with the financial-plan scoped set of control item types.

Underlying Base Objects

The view is defined over two documented objects:

• PA_CI_TYPES_V — the base control item types view supplying the identity and descriptive attributes (CI_TYPE_ID, class code, name, short name, description, and the cost and revenue impact flags).
• PA_CI_IMPACT_TYPE_USAGE — the impact type usage table that governs where a given control item type may be applied. The join to this table is what gives the view its financial-plan orientation, filtering CI types to those valid for financial plan use.

Downstream, the view is referenced by PA_FP_CI_AMOUNTS_V and PA_FP_CONTROL_ITEMS_UTILS, both financial plan components. PA_FP_CI_AMOUNTS_V exposes control item amounts within plans, while PA_FP_CONTROL_ITEMS_UTILS is the utility package/object that resolves control item behavior during plan processing. This dependency chain confirms the view's role as a configuration lookup consumed during financial plan construction and maintenance.

Key Columns

• CI_TYPE_ID (NUMBER, 15) — primary identifier of the control item type; the key joined throughout Projects financial plan objects.
• CI_TYPE_CLASS_CODE (VARCHAR2, 30) — classification code grouping the control item type.
• NAME (VARCHAR2, 150) — user-facing name of the control item type.
• SHORT_NAME (VARCHAR2, 30) — abbreviated label used in dense plan layouts and lists.
• DESCRIPTION (VARCHAR2, 2000) — free-text explanation of the control item type.
• COST_IMPACT_FLAG (VARCHAR2) — indicates whether the control item type affects cost. This is the column most commonly targeted when validating whether a CI type contributes to the cost side of a financial plan.
• REVENUE_IMPACT_FLAG (VARCHAR2) — parallel indicator for revenue impact.

Common Use Cases and Queries

Typical uses include validating control item configuration before building plan entry pages, resolving display labels for plan lines, and determining impact behavior during plan processing. The simplest query retrieves all financial-plan-capable CI types:

• SELECT ci_type_id, name, short_name, cost_impact_flag, revenue_impact_flag FROM apps.pa_ci_types_w_finplan_v;
• SELECT ci_type_id, name FROM apps.pa_ci_types_w_finplan_v WHERE cost_impact_flag = 'Y';
• SELECT c.ci_type_id, c.name, c.cost_impact_flag FROM apps.pa_ci_types_w_finplan_v c WHERE c.ci_type_class_code = :class_code;

Because the view is unsupported for direct access, any production usage should mirror its logic through supported APIs or Oracle-provided concurrent programs rather than relying on the view itself.