Search Results psa_efc_options_u1

Overview

PSA.PSA_EFC_OPTIONS is a reference (setup) table in the Oracle E-Business Suite PSA (Public Sector Applications) schema that stores Enhanced Funds Check configuration options. In Oracle EBS 12.1.1 and 12.2.2, the PSA schema underlies the Grants Accounting and Public Sector Financials functionality, where funds checking is performed against appropriated budgets rather than simple account balances. This table provides the per-ledger controls that govern how Enhanced Funds Check behaves, most notably whether multiple funding budgets may be combined when validating a transaction.

The table is owned by PSA, is registered as FND Design Data (PSA.PSA_EFC_OPTIONS), has a documented status of VALID, and resides in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10. Its unique index PSA_EFC_OPTIONS_U1 is built in the APPS_TS_TX_IDX tablespace on SET_OF_BOOKS_ID, and the same column forms the documented primary key PSA_EFC_OPTIONS_PK. Because the table is a standalone configuration entity with no foreign-key dependencies on referential columns beyond the standard WHO audit columns, a Data Vault modeling heuristic would suggest classifying it as a hub-like reference entity: the ledger identifier acts as the natural business key, with the flag and audit columns carried as descriptive context on that key.

Key Information Stored

The documented schema contains seven columns, reflecting a narrow, single-row-per-ledger configuration table:

• SET_OF_BOOKS_ID (NUMBER 15, mandatory) — the accounting books defining column. This is both the surrogate primary key (PSA_EFC_OPTIONS_PK) and the business-key candidate exposed by the unique index PSA_EFC_OPTIONS_U1. In 12.2.2 terminology this corresponds to the ledger identifier, though the legacy EBS 12.1.1 column naming is retained.
• MULT_FUNDING_BUDGETS_FLAG (VARCHAR2) — indicates whether Multiple Funds Budgets is enabled for the ledger, i.e., whether funds checking may draw on more than one funding budget when evaluating a transaction.
• CREATION_DATE (DATE) — the date the row was created.
• CREATED_BY (NUMBER) — the user who created the row (foreign key to FND_USER.USER_ID).
• LAST_UPDATE_DATE (DATE) — the date a user last updated the row.
• LAST_UPDATED_BY (NUMBER 15) — the user who last updated the row (foreign key to FND_USER.USER_ID).
• LAST_UPDATE_LOGIN (NUMBER 15) — the operating system login of the last updater (foreign key to FND_LOGINS.LOGIN_ID).

The core business content is therefore the pairing of the ledger with its Multiple Funds Budgets flag; the remaining five columns are the standard WHO audit columns maintained automatically by Oracle Application Object Library.

Common Use Cases and Queries

The principal use case is administrative inquiry: determining whether a given ledger has Multiple Funds Budgets enabled before running or troubleshooting a funds check. The canonical query is a point lookup on the unique key, which is fully satisfied by the PSA_EFC_OPTIONS_U1 index:

SELECT set_of_books_id, mult_funding_budgets_flag
FROM psa.psa_efc_options
WHERE set_of_books_id = :ledger_id;

Reporting scenarios include auditing which ledgers have the option enabled across the instance, and reconciling setup changes against audit history:

SELECT set_of_books_id, mult_funding_budgets_flag, last_updated_by, last_update_date
FROM psa.psa_efc_options
ORDER BY set_of_books_id;

A common join pattern is to combine the flag with the ledger definition in GL_LEDGERS to produce a human-readable configuration report keyed by ledger name. Because the table holds one row per ledger, it is also useful in migration or cloning validation: verifying that the expected rows exist after a financials setup copy. The absence of a row for a ledger implies the Enhanced Funds Check option has not been explicitly configured for that books definition.

Related Objects

The documented dependency data shows this table does not reference any database object directly and is referenced by the object PSA_EFC_OPTIONS# (the underlying object referenced in the PSA dependency chain). The most significant related objects are:

• PSA.PSA_EFC_OPTIONS# — the dependent object listed in the ETRM dependency section for this table.
• FND_USER — join on CREATED_BY = USER_ID and LAST_UPDATED_BY = USER_ID for WHO audit resolution.
• FND_LOGINS — join on LAST_UPDATE_LOGIN = LOGIN_ID.
• GL_LEDGERS / GL_SETS_OF_BOOKS — join SET_OF_BOOKS_ID to the ledger or books definition for descriptive reporting.
• PSA_EFC_OPTIONS_PK and PSA_EFC_OPTIONS_U1 — the primary-key constraint and unique index that enforce one configuration row per ledger.
• PSA funds-check and budget validation logic — the Enhanced Funds Check processing that consumes MULT_FUNDING_BUDGETS_FLAG at transaction validation time.

Consultation of these related dictionary views and constraints, alongside the table itself, provides the full picture of how Enhanced Funds Check options are configured and consumed in Oracle EBS 12.1.1 and 12.2.2.