Search Results psa_implementation_pk

Overview

PSA_IMPLEMENTATION_ALL is a Public Sector Financials (PSA) configuration table in the Oracle E-Business Suite database. Its documented purpose is Public Sector Advanced Features Implementation: it records which optional PSA features have been enabled for a given operating unit and how those features behave. In practice, the table acts as a per-organization feature registry — a single row declares that a particular PSA feature is turned on, and the remaining columns describe the installation state and processing behavior for that feature.

The table resides in the PSA schema and is owner-qualified as PSA.PSA_IMPLEMENTATION_ALL. Its primary key is PSA_IMPLEMENTATION_PK, defined over the composite of ORG_ID and PSA_FEATURE, making the operating unit plus feature name the unique identifier of a configuration row. Because ORG_ID is part of the primary key, the table is organization-striped, and the trailing "_ALL" naming convention signals that it is a multi-org table whose rows are filtered by the MO (multi-org) security profile at runtime.

The ETRM metadata classifies this object, heuristically mined from its foreign-key structure, as standalone, with a Data Vault modeling suggestion of a hub-like reference table. No dependent or parent relationships to other PSA configuration tables were documented, which is consistent with a self-contained setup repository.

Key Information Stored

The documented physical schema contains eleven columns. The most significant are:

• PSA_FEATURE — the business identifier of the feature being configured; a component of the primary key and the column an administrator or report will most often filter on.
• ORG_ID — the operating unit for which the feature setting applies; the second component of the primary key and the driver of multi-org security.
• STATUS — the enabled/disabled or active/inactive state of the feature for that organization.
• ALLOCATION_METHOD — the allocation method to be applied for the feature, governing how amounts are distributed.
• MAPPING_REQUIRED — an indicator of whether account or value mapping must be maintained before the feature can be used.
• PROGRAM_INSTALLED — an indicator of whether the associated concurrent program or database object has been installed, used by setup diagnostics and upgrade validation.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS WHO audit columns recording row creation and modification, whose values should always be supplied from FND_GLOBAL when inserting programmatically.

The surrogate primary key is the composite PSA_IMPLEMENTATION_PK (ORG_ID, PSA_FEATURE). No separate single-column surrogate key is documented, and no alternate unique index is listed; the business key therefore coincides with the primary key.

Common Use Cases and Queries

The primary use case is verification of PSA setup prior to go-live or after a patch application. Administrators query the table to determine whether a feature is enabled for a specific operating unit and whether its prerequisite program is installed.

• Feature enablement by operating unit: SELECT psa_feature, status, allocation_method, mapping_required FROM psa.psa_implementation_all WHERE org_id = :org_id;
• Finding the organizations using a specific feature: SELECT org_id, status FROM psa.psa_implementation_all WHERE psa_feature = :feature;
• Setup diagnostics for missing installations: SELECT org_id, psa_feature FROM psa.psa_implementation_all WHERE program_installed = 'N';

Because ORG_ID is a key column, reports must always constrain or join it against the operating unit to avoid cross-organization leakage. Audit columns support change tracking, and joining ALL_OBJECTS or FND_CONCURRENT_PROGRAMS on the feature name can reconcile configuration with installed code during upgrades from 12.1.1 to 12.2.2.

Related Objects

Documented relationship data classifies this table as standalone, with no foreign keys to parent objects. The relevant associations are therefore by convention rather than enforced constraints:

• PSA_IMPLEMENTATION_PK — the primary key constraint enforcing uniqueness of ORG_ID and PSA_FEATURE.
• HR_OPERATING_UNITS and FND_OPERATING_UNITS — joined on ORG_ID to resolve the organization name for reporting.
• FND_CONCURRENT_PROGRAMS — used to verify the PROGRAM_INSTALLED claim against the actual executable.
• FND_GLOBAL — supplies the ORG_ID and WHO audit values at insert time.

Any PSA module logic reading advanced feature flags, including allocation and mapping routines, resolves configuration through this table, making it a foundational dependency of Public Sector feature processing.