Results for “pa_implementations_u1”

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

Overview

PA.PA_IMPLEMENTATIONS_ALL is the Oracle Projects implementation control table. It stores the operating-unit–level configuration that governs how Oracle Projects, Oracle Project Billing, and Oracle Project Costing behave for each organization. Every implementation row defines a single set of Project Accounting options — numbering schemes, GL interface flags, billing cycles, organization structures, currency rules, and cross-charging behavior — keyed by ORG_ID. In Oracle EBS 12.1.1 and 12.2.2 the table resides in the APPS_TS_SEED tablespace, is owned by the PA schema, and carries a status of VALID with a documented column count of 98. Oracle marks the object as Internal Use Only, so direct DML should be avoided; changes should be made through the standard Oracle Projects setup forms or supported APIs.

From a Data Vault modeling perspective, the mined FK structure suggests a satellite-leaning classification. The table extends an operating-unit hub with descriptive attributes rather than acting as a pure transaction or relationship table, so a modeler would typically treat it as a description satellite attached to the operating unit key.

Key Information Stored

The single documented unique index is PA_IMPLEMENTATIONS_U1 on ORG_ID, which also forms the primary key PA_IMPLEMENTATIONS_PK (ORG_ID). This makes ORG_ID both the surrogate/primary key and the business-key candidate for the operating unit.

• ORG_ID — Operating unit identifier; primary key and unique business key.
• SET_OF_BOOKS_ID — Ledger associated with the operating unit (FK to GL_SETS_OF_BOOKS_11I).
• BUSINESS_GROUP_ID — HR business group (FK to HR_ALL_ORGANIZATION_UNITS).
• ORGANIZATION_STRUCTURE_ID, ORG_STRUCTURE_VERSION_ID, START_ORGANIZATION_ID — Organization hierarchy used for project ownership.
• EXP_ORG_STRUCTURE_ID, PROJ_ORG_STRUCTURE_ID and their version/start columns — Expenditure and project organization structures.
• USER_DEFINED_PROJECT_NUM_CODE, MANUAL_PROJECT_NUM_TYPE — Project numbering rules.
• USER_DEFINED_INVOICE_NUM_CODE, MANUAL_INVOICE_NUM_TYPE, NEXT_AUTOMATIC_INVOICE_NUMBER — Invoice numbering configuration.
• INVOICE_BATCH_SOURCE_ID — Default AR batch source (FK to RA_BATCH_SOURCES_ALL).
• INTERFACE_LABOR_TO_GL_FLAG, INTERFACE_USAGE_TO_GL_FLAG, INTERFACE_REVENUE_TO_GL_FLAG — GL interface enablement flags.
• PA_PERIOD_TYPE — Period type used by Projects (FK to GL_PERIOD_TYPES).
• BILLING_CYCLE, BILLING_OFFSET, ACCUMULATION_PERIOD_TYPE — Billing cadence parameters.
• CENTRALIZED_INVOICING_FLAG, ALLOW_FOREIGN_CURR_TXN_FLAG, ACCT_RATE_TYPE — Invoicing and currency controls.

Common Use Cases and Queries

Typical uses include retrieving the configuration for an operating unit, joining Projects data to the correct ledger and organization structure, and validating billing and GL interface settings before running processes. A common query retrieves the implementation options for a given ORG_ID:

SELECT pim.org_id, pim.set_of_books_id, gsob.name,
       pim.invoice_batch_source_id, pim.pa_period_type,
       pim.billing_cycle, pim.interface_labor_to_gl_flag
FROM   pa.pa_implementations_all pim,
       gl.gl_sets_of_books gsob
WHERE  pim.set_of_books_id = gsob.set_of_books_id
AND    pim.org_id = :p_org_id;

Reporting scenarios frequently join this table to determine the ledger and organization structure for a project, or to audit GL interface and currency flags across operating units. Reconciliation reports compare INTERFACE_*_TO_GL_FLAG and ALLOW_FOREIGN_CURR_TXN_FLAG values to identify inconsistencies.

Related Objects

Foreign keys reference several core objects, and dependent tables reference this table by ORG_ID:

• GL.GL_SETS_OF_BOOKS_11I — joined on SET_OF_BOOKS_ID.
• HR.HR_ALL_ORGANIZATION_UNITS — joined on BUSINESS_GROUP_ID.
• PER.PER_ORGANIZATION_STRUCTURES and PER.PER_ORG_STRUCTURE_VERSIONS — joined on ORGANIZATION_STRUCTURE_ID and ORG_STRUCTURE_VERSION_ID.
• RA.RA_BATCH_SOURCES_ALL — joined on INVOICE_BATCH_SOURCE_ID.
• GL.GL_PERIOD_TYPES — joined on PA_PERIOD_TYPE.
• PA.PA_EVENT_TYPE_OUS_ALL, PA.PA_EXPENDITURE_TYPE_OUS_ALL, PA.PA_ORG_LABOR_SCH_RULE — reference ORG_ID as a parent key.