Search Results psa_efc_options




Overview
Explore in AI Chat

Overview

PSA_EFC_OPTIONS is a configuration table within the PSA (Public Sector Financials) product of Oracle E-Business Suite, holding Enhanced Funds Check Options keyed by set of books. Its purpose is to control how budgetary funds checking behaves for a given ledger, most notably whether multiple funding budgets are permitted during funds reservation and validation. The table exists in both EBS 12.1.1 and 12.2.2, with the documented sample reflecting the 12.2.2 physical schema, and its status is VALID in the PSA schema.

The object carries a single-row-per-ledger configuration semantic: the primary key PSA_EFC_OPTIONS_PK is defined on SET_OF_BOOKS_ID, which is also the sole business-key candidate captured by the unique index PSA_EFC_OPTIONS_U1. In Data Vault modeling terms, the heuristic classification mined from the foreign-key structure is standalone. This means the table has no documented FK dependencies to parent hubs or links; it can be modeled as a small reference/satellite-style configuration set whose natural business key is the ledger identifier, with no parent hub required.

Functionally, PSA_EFC_OPTIONS sits in the funds-check configuration layer of Public Sector Financials. When Oracle performs enhanced budgetary control, the funds-check engine consults this table to determine which processing options apply to the ledger, rather than relying solely on global profile options. Administrators populate it once per set of books, and runtime funds-check logic reads the option flags to decide allowable funding sources.

Key Information Stored

The documented columns (7 total) divide into a ledger business key, a functional option flag, and the standard EBS audit/WHO columns.

  • SET_OF_BOOKS_ID — the ledger identifier. It is the primary key (PSA_EFC_OPTIONS_PK), the business-key candidate (PSA_EFC_OPTIONS_U1), and the join column to the accounting setup. This is the column that makes each row unique.
  • MULT_FUNDING_BUDGETS_FLAG — the substantive configuration value, indicating whether multiple funding budgets are allowed for enhanced funds checking in the specified ledger.
  • CREATION_DATE and CREATED_BY — the standard audit columns recording when and by whom the option row was first created.
  • LAST_UPDATE_DATE and LAST_UPDATED_BY — the audit columns capturing the most recent modification and its author.
  • LAST_UPDATE_LOGIN — the session/login identifier associated with the last change, used for audit traceability in concurrent or web sessions.

The surrogate-versus-business-key distinction is minimal here: there is no generated surrogate key column, so the ledger identifier serves as both the physical primary key and the business key. Because the table is standalone, no foreign-key columns to other PSA hubs are documented.

Common Use Cases and Queries

The most frequent use is verifying the enhanced funds-check configuration for a ledger before troubleshooting budget validation errors. A typical lookup joins the option row to the ledger definition:

  • Retrieve the flag for a specific ledger: SELECT mult_funding_budgets_flag FROM psa_efc_options WHERE set_of_books_id = :p_sob_id;
  • List all configured ledgers: SELECT set_of_books_id, mult_funding_budgets_flag, last_update_date FROM psa_efc_options ORDER BY set_of_books_id;
  • Audit recent changes: filter on LAST_UPDATE_DATE and LAST_UPDATED_BY to identify who altered funds-check behavior and when.
  • Reconcile against GL_LEDGERS (or FND_ID_FLEX_STRUCTURES via the ledger) to detect ledgers lacking an option row, which may default to standard funds-check behavior.

Reporting use cases include configuration inventories for public-sector implementations, migration validation when moving a ledger between instances, and pre-upgrade checks confirming option rows exist before 12.2.2 patch application. Because each ledger has at most one row, queries are inexpensive and suitable for embedding in concurrent program validation logic.

Related Objects

The documented relationship data classifies PSA_EFC_OPTIONS as standalone, so it has no mined foreign keys. The significant associated objects are the ledger definitions referenced by SET_OF_BOOKS_ID and the PSA funds-check components that consume the option flag.

  • GL_LEDGERS — join on LEDGER_ID = PSA_EFC_OPTIONS.SET_OF_BOOKS_ID to resolve the ledger name and currency.
  • GL_LEDGER_CONFIG_DETAILS / GL_SETS_OF_BOOKS — legacy and 12.2 ledger setup views used to validate the ledger identifier.
  • PSA_EFC_... companion Enhanced Funds Check tables in the PSA schema that share the set-of-books context and are read together during funds validation.
  • PO/AP funds-check and budgetary-control APIs — the public-sector reservation interfaces that indirectly honor MULT_FUNDING_BUDGETS_FLAG at runtime.
  • FND standard WHO audit references — CREATED_BY and LAST_UPDATED_BY join to FND_USER for audit reporting.

Because the table is standalone, integration points are logical (shared ledger key and concurrent funds-check logic) rather than referential constraints.