Search Results pji_source_flag

Overview

PA_PROJECTS is a single-organization reporting view within the Oracle Projects (PA) module of Oracle E-Business Suite, documented for releases 12.1.1 and 12.2.2. It exposes project header information from the Projects repository, presenting one row per project definition along with the descriptive, financial, billing, scheduling, and descriptive flexfield attributes that drive project execution and accounting. In EBS reporting and integration contexts, the view serves as a flattened, read-oriented projection of the base project entity, allowing report developers, integrators, and business analysts to query project master data without navigating the full normalized table structure that underpins the Projects foundation.

The metadata identifies the object type as a View, product as PA - Projects, and describes it as Single-Org. This classification is significant: unlike multi-org secured views that apply operating unit or organization security predicates, a single-org view is typically intended for use in contexts where organization context is supplied externally or where the view itself does not enforce operating unit filtering. The documented metadata also records "Not implemented in this database" under Implementation/DBA Data, indicating that the view was not deployed in the particular environment from which the ETRM extract was generated, and no owner or referenced base objects were captured in the 12.2.2 documentation.

Underlying Base Objects

The ETRM metadata states that no base objects are documented for this view, and no owner is recorded. In practice, the column list makes clear that PA_PROJECTS is derived from the PA_PROJECTS_ALL base table, which holds the master project definitions in Oracle Projects. The view's presence in the single-org category, together with the inclusion of ORG_ID among the exposed columns, is consistent with a projection that filters or scopes by organization at query time rather than embedding the operating unit security of PA_PROJECTS_ALL. Because the documented metadata does not enumerate underlying tables, consumers should treat the relationship to PA_PROJECTS_ALL as inferred from column correspondence rather than as an explicitly documented fact. Related information such as project types, statuses, billing cycles, and rate schedules is referenced by identifier columns in this view and resolved through their respective lookup and setup tables.

Key Columns

The view exposes a broad set of columns spanning project identity, classification, lifecycle, billing, and integration control:

• PROJECT_ID, NAME, LONG_NAME, PROJECT_TYPE: Core identifiers and the project classification used throughout Projects.
• SEGMENT1 through SEGMENT10: The project number and other key flexfield segments.
• PROJECT_STATUS_CODE, START_DATE, COMPLETION_DATE, CLOSED_DATE, ACTUAL_START_DATE, ACTUAL_FINISH_DATE, SCHEDULED_START_DATE, SCHEDULED_FINISH_DATE: Status and the full set of scheduled and actual lifecycle dates.
• ORG_ID, CARRYING_OUT_ORGANIZATION_ID: Organization context, including the organization carrying out the project.
• Billing and revenue columns such as DISTRIBUTION_RULE, BILLING_CYCLE_ID, RETENTION_PERCENTAGE, UNBILLED_RECEIVABLE_DR, UNEARNED_REVENUE_CR, and the labor, non-labor, and retention invoice format identifiers.
• Rate schedule columns including COST_IND_RATE_SCH_ID, REV_IND_RATE_SCH_ID, INV_IND_RATE_SCH_ID and their override counterparts and fixed dates.
• PROJECT_CURRENCY_CODE, ALLOW_CROSS_CHARGE_FLAG, PROJECT_RATE_DATE: Currency and cross-charge behavior controls.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE10: Descriptive flexfield context and values.
• Audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and concurrent program columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID).

Common Use Cases and Queries

Typical applications include project master data extracts, status and milestone reporting, billing setup validation, and integration feeds into external reporting or data warehouse platforms. A representative query filters active projects for a given organization and status:

• SELECT project_id, name, long_name, project_status_code, start_date, completion_date FROM pa_projects WHERE org_id = :p_org_id AND project_status_code = 'APPROVED';
• Project currency and billing profile review: SELECT name, project_currency_code, billing_cycle_id, retention_percentage FROM pa_projects WHERE allow_cross_charge_flag = 'Y';
• Dated lifecycle reporting: SELECT name, actual_start_date, actual_finish_date, scheduled_start_date, scheduled_finish_date FROM pa_projects WHERE actual_finish_date IS NULL;

Because the view is documented as single-org and its base object mapping is not captured in the ETRM metadata, implementers should verify deployment and column availability in each target environment before relying on it in production queries or interfaces.