Search Results billing_offset




Overview
Explore in AI Chat

Overview

PA_PROJECT_TYPES is a Projects (PA) module view that exposes the definition of project types within Oracle EBS 12.1.1 and 12.2.2. A project type is a reusable template that drives defaulting, validation, and processing behavior for projects created against it — including billing, budgeting, capital asset processing, workflow enablement, and cost/revenue recognition. The view surfaces one row per project type and carries the full set of configuration flags and foreign key references that control how projects of that type behave.

The ETRM metadata classifies this object as "Single-Org," meaning the view is scoped to a single operating unit via the ORG_ID discriminator. In multi-org deployments, ORG_ID determines which operating unit owns a given project type row, and queries must respect the MOAC (Multi-Org Access Control) security context. The ETRM record notes the object is "Not implemented in this database," which indicates that in the documented environment the view was not deployed or was inaccessible at the time of extraction; the view text nonetheless reflects the canonical column projection used by Oracle.

Underlying Base Objects

The ETRM metadata documents no referenced base objects for this view. In standard Oracle implementation, PA_PROJECT_TYPES is a single-table view defined over PA_PROJECT_TYPES_ALL (the multi-org table holding project type definitions), typically filtered or joined to resolve ORG_ID scoping. Because the documented metadata lists no underlying objects, the authoritative column list supplied in the view text should be treated as the reference definition: it is a straight projection of the columns from the underlying project types table without aggregation or joins.

The absence of documented base objects means the view functions as a stability layer — applications and reports can query PA_PROJECT_TYPES rather than the _ALL table directly, insulating them from underlying storage changes.

Key Columns

Common Use Cases and Queries

This view is commonly queried to enumerate project types, audit their defaulting configuration, and drive validation logic in reports and integrations.

  • Locate the revenue budget resource list assigned to a project type:
SELECT project_type_id, project_type, description,
       rev_budget_entry_method_code, rev_budget_resource_list_id,
       allow_rev_budget_entry_flag
FROM   pa_project_types
WHERE  org_id = :p_org_id
AND    rev_budget_resource_list_id IS NOT NULL;
  • Compare cost and revenue budgeting configuration across types:
SELECT project_type, cost_budget_entry_method_code, cost_budget_resource_list_id,
       rev_budget_entry_method_code, rev_budget_resource_list_id,
       default_resource_list_id
FROM   pa_project_types
WHERE  org_id = :p_org_id;
  • Identify types with workflow enabled:
SELECT project_type, enable_project_wf_flag, enable_budget_wf_flag
FROM   pa_project_types
WHERE  org_id = :p_org_id
AND    enable_project_wf_flag = 'Y';

Because the view is Single-Org, every query must supply the appropriate ORG_ID filter to enforce MOAC security and return the correct operating unit's project types.