Results for “pa_implementations”

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

Overview

PA_IMPLEMENTATIONS is a Projects (PA) module view in Oracle E-Business Suite that exposes the implementation-level configuration for Oracle Projects. It is documented in ETRM as a single-org view, meaning its definition returns the implementation setup row scoped to a single operating unit / organization context rather than across the whole business group. The underlying column set mirrors the multi-org base table PA_IMPLEMENTATIONS_ALL, with the "_ALL" columns that do not belong to the current organization filtered out at runtime by the Multi-Org mechanism.

Functionally, the view acts as the central configuration registry for Oracle Projects. Each row carries the setup that governs how the application behaves across key processes: expenditure cycles, overtime calculation, general ledger interfacing, project and invoice numbering, organization structures, billing cycles, cross-charging, and taxation. Because the view is bound to a SET_OF_BOOKS_ID and BUSINESS_GROUP_ID in addition to ORG_ID, it links Projects processing to the correct ledger and business group.

Underlying Base Objects

The ETRM metadata records no referenced base objects for this view. In practice, PA_IMPLEMENTATIONS is the single-org synonym-style view over the Projects implementation table, which is partitioned by operating unit through the ORG_ID column. The view text returns the implementation columns without the multi-org filter columns that exist only on the _ALL variant. Because the metadata lists "Not implemented in this database" for the DBA section, no physical base object mapping is documented here; consultants should confirm the actual base table name in their instance by querying USER_VIEWS or DBA_VIEWS.

Key Columns

• SET_OF_BOOKS_ID, BUSINESS_GROUP_ID, ORG_ID — Ledger, business group, and operating unit context for the implementation row.
• ORGANIZATION_STRUCTURE_ID / ORG_STRUCTURE_VERSION_ID / START_ORGANIZATION_ID — The organization hierarchy used by Projects.
• USER_DEFINED_PROJECT_NUM_CODE, MANUAL_PROJECT_NUM_TYPE, PROJECT_ORGANIZATION_TYPE — Project numbering and organization defaults.
• INTERFACE_LABOR_TO_GL_FLAG, INTERFACE_USAGE_TO_GL_FLAG, INTERFACE_REVENUE_TO_GL_FLAG — Control whether labor, usage, and revenue are interfaced to the General Ledger.
• ACCUMULATION_PERIOD_TYPE, PA_PERIOD_TYPE, EXP_CYCLE_START_DAY_CODE — Period and expenditure cycle definitions.
• OVERTIME_CALC_ENABLED_FLAG — Enables overtime calculation for expenditures.
• INVOICE_BATCH_SOURCE_ID, BILLING_CYCLE, BILLING_OFFSET, NEXT_AUTOMATIC_INVOICE_NUMBER — Billing generation defaults.
• CENTRALIZED_INVOICING_FLAG, MULTI_CURRENCY_BILLING_FLAG, ALLOW_FUNDING_ACROSS_OU_FLAG, SHARE_ACROSS_OU_BR_SCH_FLAG — Cross-organizational billing and funding behavior.
• DEFAULT_RATE_TYPE, DEFAULT_RATE_DATE_CODE, CC_DEFAULT_RATE_TYPE, CC_DEFAULT_RATE_DATE_CODE — Default rate selection for billing and cross-charging.
• OUTPUT_TAX_USE_* and OUTPUT_TAX_HIER_* — Tax driver and hierarchy sources for output tax determination.
• PERIOD_SET_NAME, SAME_PA_GL_PERIOD, FTE_DAY, FTE_WEEK, INCLUDE_GAINS — Accounting calendar linkage and resource/utilization configuration.

Common Use Cases and Queries

The view is typically queried to audit implementation setup, to drive configuration checks during upgrades or implementations, and to feed downstream reporting that depends on Projects configuration flags.

Sample query to retrieve the implementation configuration for an operating unit:

• SELECT org_id, set_of_books_id, business_group_id, interface_labor_to_gl_flag, interface_revenue_to_gl_flag, overtime_calc_enabled_flag FROM pa_implementations;

To review billing and cross-charging behavior:

• SELECT org_id, billing_cycle, billing_offset, centralized_invoicing_flag, cc_ic_billing_prvdr_flag, cc_ic_billing_recvr_flag FROM pa_implementations;

To verify tax determination sources and numbering rules:

• SELECT org_id, output_tax_use_cust_flag, output_tax_use_site_flag, output_tax_use_project_flag, user_defined_invoice_num_code, manual_invoice_num_type FROM pa_implementations;

Because the view is single-org, results are already restricted to the session's operating unit; multi-org reporting that must span operating units should query the corresponding _ALL base table instead.