Results for “pa_implementations_all”

50+ results




Overview
Explore in AI Chat

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

Overview

PA_IMPLEMENTATIONS_ALL is the principal setup table for the Oracle Projects (PA) application, residing in the PA schema. It stores information about the configuration of an Oracle Projects installation, with one implementation record per operating unit. Each row captures the business group, set of books, organization hierarchy, calendar, numbering, billing, costing, currency, and multi-organization options that govern how projects, expenditures, and invoices are processed for that unit.

The table is owned by the PA product and is classified as VALID in the ETRM metadata for Oracle EBS 12.1.1 and 12.2.2. It carries 98 documented columns and is described by the unique index PA_IMPLEMENTATIONS_U1 on the ORG_ID column, which is also the table's primary key (PA_IMPLEMENTATIONS_PK). Under the heuristic Data Vault classification mined from its foreign key structure, PA_IMPLEMENTATIONS_ALL is considered satellite-leaning; that is, it behaves as a configuration attribute repository keyed by operating unit rather than a transactional hub or a pure relationship link. This classification is a modeling suggestion, not a documented Oracle construct.

Key Information Stored

The surrogate primary key is ORG_ID, the operating unit identifier, and it is the sole documented business-key candidate through the unique index PA_IMPLEMENTATIONS_U1. The remaining columns hold the substantive setup data, and the most important among them include:

Common Use Cases and Queries

The table is most frequently queried during Projects setup validation, period and calendar troubleshooting, and multi-organization reporting. A typical lookup retrieves the core configuration for a given operating unit:

  • SELECT set_of_books_id, business_group_id, pa_period_type, period_set_name FROM pa_implementations_all WHERE org_id = :org_id;
  • Detecting operating units where the Projects period differs from the GL period by filtering on SAME_PA_GL_PERIOD.
  • Reviewing which operating units push labor, usage, or revenue to GL by inspecting the INTERFACE_*_TO_GL_FLAG columns.
  • Identifying installations with multi-currency billing or cross-charge processing enabled for audit and impact analysis.
  • Confirming the default invoice batch source and billing cycle before troubleshooting AR invoice generation.

Related Objects

PA_IMPLEMENTATIONS_ALL sits at the center of a set of reference and child objects. Its foreign keys reference HR_ALL_ORGANIZATION_UNITS through BUSINESS_GROUP_ID, GL_SETS_OF_BOOKS_11I through SET_OF_BOOKS_ID, FA_BOOK_CONTROLS through BOOK_TYPE_CODE, PER_ORGANIZATION_STRUCTURES and PER_ORG_STRUCTURE_VERSIONS through the organization hierarchy columns, RA_BATCH_SOURCES_ALL through INVOICE_BATCH_SOURCE_ID, GL_PERIOD_TYPES through PA_PERIOD_TYPE, and SO_SALES_CREDIT_TYPES_115 through SALES_CREDIT_TYPE_CODE.

Several dependent tables reference this table by ORG_ID, including PA_EVENT_TYPE_OUS_ALL, PA_EXPENDITURE_TYPE_OUS_ALL, PA_FP_OF_WEBADI_XFACE, PA_ORG_FCST_ELEMENTS (which also references it through OTHER_ORG_ID), and PA_ORG_LABOR_SCH_RULE. These objects inherit the operating unit's implementation configuration and depend on the presence of a valid PA_IMPLEMENTATIONS_ALL row for that organization.