Results for “psa_efc_summary_budgets_u1”

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

Overview

PSA.PSA_EFC_SUMMARY_BUDGETS is a transaction data table in the Oracle E-Business Suite PSA (Public Sector Applications) schema. It stores budget information implemented with enhanced funds check (EFC) options, providing the persistent link between a funds-check template definition and the funding budget version against which enhanced funds checking is performed. The table resides in the APPS_TS_TX_DATA tablespace and is marked VALID in the ETRM 12.2.2 documentation, with the object also present in the 12.1.1 code line under the same owner and name.

From a Data Vault modeling heuristice, this object is classified as standalone. The documented FK structure does not surface outbound relationships, so no hub, link, or satellite role can be asserted from dependencies alone. The narrow two-column business key and the remaining five standard WHO audit columns are consistent with a configuration or mapping-style hub candidate, but this is a modeling suggestion rather than a documented fact.

Key Information Stored

The table documents seven columns. The most significant are:

• TEMPLATE_ID (NUMBER(30), mandatory) — Template identifier. First component of the composite primary key and of the unique index. Identifies the enhanced funds check template whose budget configuration is being recorded.
• FUNDING_BUDGET_VERSION_ID (NUMBER(30), mandatory) — Funding budget version identifier. Second key component; identifies the specific budget version associated with the template.
• CREATION_DATE — Standard WHO column capturing row creation date.
• CREATED_BY — Standard WHO column; foreign key to FND_USER.USER_ID.
• LAST_UPDATE_DATE — Standard WHO column recording the last update date.
• LAST_UPDATED_BY (NUMBER(15)) — Standard WHO column; foreign key to FND_USER.USER_ID.
• LAST_UPDATE_LOGIN (NUMBER(15)) — Standard WHO column; foreign key to FND_LOGINS.LOGIN_ID.

The surrogate-style primary key is PSA_EFC_SUMMARY_BUDGETS_PK, defined over (TEMPLATE_ID, FUNDING_BUDGET_VERSION_ID). The unique business-key candidate documented is PSA_EFC_SUMMARY_BUDGETS_U1, also over (TEMPLATE_ID, FUNDING_BUDGET_VERSION_ID), stored in APPS_TS_TX_IDX. Because the PK and the unique index cover the same column pair, the combination is the natural business key; the WHO columns carry no key significance.

Common Use Cases and Queries

The principal use case is resolving which funding budget version is bound to a given enhanced funds check template, typically during budget validation, funds reservation, or configuration review. A basic retrieval follows the documented query text:

SELECT TEMPLATE_ID
     , FUNDING_BUDGET_VERSION_ID
     , CREATION_DATE
     , CREATED_BY
     , LAST_UPDATE_LOGIN
     , LAST_UPDATE_DATE
     , LAST_UPDATED_BY
FROM   PSA.PSA_EFC_SUMMARY_BUDGETS
WHERE  TEMPLATE_ID = :p_template_id;

Because the unique index leads with TEMPLATE_ID, this predicate yields an index range scan and is the most efficient access path. Reporting patterns include inventorying all budget versions attached to each template, auditing configuration changes via LAST_UPDATE_DATE and LAST_UPDATED_BY, and reconciling the set of templates that participate in enhanced funds check. Joins to FND_USER on CREATED_BY or LAST_UPDATED_BY support audit trails, and joins to FND_LOGINS on LAST_UPDATE_LOGIN support session-level traceability.

Related Objects

The documented dependency metadata states that PSA_EFC_SUMMARY_BUDGETS does not reference any database object, and that it is referenced by the PSA schema object PSA_EFC_SUMMARY_BUDGETS#. Practically, the following objects are relevant when working with this table:

• FND_USER — joined on CREATED_BY and LAST_UPDATED_BY for user identification.
• FND_LOGINS — joined on LAST_UPDATE_LOGIN for login/session context.
• PSA_EFC_SUMMARY_BUDGETS# — the corresponding editioning or synonym-related object listed as referencing this table.
• PSA_EFC_SUMMARY_BUDGETS_PK — primary key constraint over (TEMPLATE_ID, FUNDING_BUDGET_VERSION_ID).
• PSA_EFC_SUMMARY_BUDGETS_U1 — unique index over the same column pair in APPS_TS_TX_IDX.
• Funding budget version and enhanced funds check template definitions in the PSA module — the conceptual parents of TEMPLATE_ID and FUNDING_BUDGET_VERSION_ID respectively.

Because the table is standalone with no documented foreign keys, referential integrity to template and budget version definitions is maintained by application logic rather than database constraints.