Search Results pa_projects_v_o

Overview

PA_PROJECTS_V_O is a Projects (PA) module view in Oracle E-Business Suite that exposes project definition and billing attributes from the underlying project master data. The ETRM documentation classifies this object with the description "10Sc Only - Retrofitted," indicating that the view originated in an earlier release of the Oracle Projects application (the 10SC code line) and was carried forward as a compatibility or retrofit object rather than being introduced natively in the 12.1.1 or 12.2.2 schemas. The documentation further records the implementation status as "Not implemented in this database," meaning the object may be absent or inactive in a given environment, and consumers should verify its existence before relying on it.

Functionally, the view presents a wide, denormalized projection of project header information: descriptive columns (name, description, segment values), status and date columns, and—most significantly for the search term "distribution_rule_m"—the DISTRIBUTION_RULE column, which governs how project costs, revenue, and invoice amounts are distributed across general ledger accounts. Because it consolidates definitional, billing, and descriptive flexfield attributes into a single queryable surface, the view supports reporting and integration scenarios where a consumer needs project-level context without navigating the normalized PA_PROJECTS table directly.

Underlying Base Objects

The ETRM metadata documents no referenced base objects for this view, and no parent or child relationships are recorded. The embedded view text, however, shows that the projection is drawn from at least two sources: an aliased source "PROJ," which supplies the overwhelming majority of columns and corresponds to the PA_PROJECTS project master table, and an aliased source "BILL," which contributes the BILLING_CYCLE_NAME column and is joined through the BILLING_CYCLE_ID foreign key to the billing cycle entity. The presence of PROGRAM_ID, PROGRAM_APPLICATION_ID, REQUEST_ID, and PROGRAM_UPDATE_DATE columns indicates that the view is populated or maintained through concurrent program processing, a pattern common to Oracle Projects reporting objects. Because the documentation lists no referenced objects, DBAs should resolve the actual dependencies through ALL_DEPENDENCIES or ALL_VIEWS in the target instance.

Key Columns

• DISTRIBUTION_RULE — The distribution rule identifier applied to the project, determining how amounts are allocated to accounts; the column most directly associated with the searched term.
• PROJECT_ID, NAME, SEGMENT1 — Primary key, user-facing project name, and the project number segment.
• PROJECT_STATUS_CODE, START_DATE, COMPLETION_DATE, CLOSED_DATE — Lifecycle status and milestone dates.
• BILLING_CYCLE_ID, BILLING_CYCLE_NAME, BILLING_OFFSET — Billing frequency and offset information.
• LABOR_/NON_LABOR_/RETENTION_ INVOICE_FORMAT_ID, RETENTION_PERCENTAGE — Invoice formatting and retention configuration.
• UNBILLED_RECEIVABLE_DR, UNEARNED_REVENUE_CR — Default accounts for unbilled receivable and unearned revenue.
• COST_IND_RATE_SCH_ID, REV_IND_RATE_SCH_ID, INV_IND_RATE_SCH_ID — Indirect rate schedule assignments for cost, revenue, and invoicing.
• ATTRIBUTE1–ATTRIBUTE10, ATTRIBUTE_CATEGORY — Descriptive flexfield context and values.
• SUMMARY_FLAG, ENABLED_FLAG, TEMPLATE_FLAG — Structural and operational flags.

Common Use Cases and Queries

The view is typically used to resolve project distribution rules in reporting and in integration extracts. A representative query retrieves active projects with their distribution rule and billing cycle:

• SELECT project_id, name, segment1, distribution_rule, billing_cycle_name FROM pa_projects_v_o WHERE enabled_flag = 'Y';
• SELECT project_id, name, distribution_rule FROM pa_projects_v_o WHERE distribution_rule IS NOT NULL;
• SELECT p.project_id, p.name, p.project_status_code, p.start_date, p.completion_date FROM pa_projects_v_o p WHERE p.project_status_code = 'APPROVED';

Because the metadata records the view as not implemented in the database, any query should first confirm availability via ALL_VIEWS. Where the object is absent, equivalent project and distribution rule data can be obtained from PA_PROJECTS and its associated distribution rule tables.