Results for “default_recovery_rate”

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

Overview

FINANCIALS_SYSTEM_PARAMS_ALL is the Oracle Payables (AP) configuration table that stores Financials system parameters and defaults for Oracle E-Business Suite. In release 12.1.1 and 12.2.2, the table resides in the AP schema and is exposed through the Financials System Options setup form, where it captures the operating defaults applied to invoice entry, payment processing, encumbrance accounting, tax calculation, and default accounting flexfield assignments. Because the table is keyed by both ledger and operating unit, it allows a distinct parameter set to be maintained for each combination of set of books and organization, which is the mechanism that makes multi-org payables behavior possible.

Under a heuristic Data Vault classification derived from the foreign key structure, this object is best modeled as a link. Its composite key of SET_OF_BOOKS_ID and ORG_ID naturally associates a ledger dimension with an operating unit dimension, while the numerous code combination identifiers and lookup columns act as reference pointers rather than descriptive history. A formal Data Vault design would typically place the ledger and operating unit attributes in hubs, the parameter values in a satellite, and the chart-of-accounts references in link structures.

Key Information Stored

The table contains 81 documented columns. The primary key, FINANCIALS_SYSTEM_PARAMS_PK, is a composite of SET_OF_BOOKS_ID and ORG_ID. A separate unique index, FINANCIALS_SYSTEM_PARAMS_U1, covers the same two columns, confirming this pair as the business-key candidate. The most operationally significant columns include:

• SET_OF_BOOKS_ID – identifies the ledger for which the parameters apply; joins to GL_SETS_OF_BOOKS_11I.
• ORG_ID – identifies the operating unit, enabling per-organization defaults.
• ACCTS_PAY_CODE_COMBINATION_ID – the default liability account for supplier invoices.
• PREPAY_CODE_COMBINATION_ID and DISC_TAKEN_CODE_COMBINATION_ID – default prepayment and discount-taken accounts.
• INVOICE_CURRENCY_CODE and PAYMENT_CURRENCY_CODE – default invoice and payment currencies, both referencing FND_CURRENCIES.
• TERMS_ID – default payment terms applied to new invoices.
• PAYMENT_METHOD_LOOKUP_CODE and PAY_DATE_BASIS_LOOKUP_CODE – default disbursement method and payment date derivation.
• REQ_ENCUMBRANCE_TYPE_ID, PURCH_ENCUMBRANCE_TYPE_ID, and INV_ENCUMBRANCE_TYPE_ID – encumbrance types for requisitions, purchase orders, and invoices.
• RES_ENCUMB_CODE_COMBINATION_ID and RESERVE_AT_COMPLETION_FLAG – reservation accounting controls.
• RATE_VAR_GAIN_CCID and RATE_VAR_LOSS_CCID – exchange rate variance gain and loss accounts.
• BILL_TO_LOCATION_ID and SHIP_TO_LOCATION_ID – default locations referencing HR_LOCATIONS_ALL.
• MATCH_OPTION and HOLD_UNMATCHED_INVOICES_FLAG – invoice matching and hold behavior.

Standard WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) are also present.

Common Use Cases and Queries

The primary use case is diagnosing why invoice or payment defaults appear incorrectly for a given operating unit. A typical query retrieves the complete parameter set for one ledger and organization:

• SELECT * FROM ap.financials_system_params_all WHERE set_of_books_id = :ledger AND org_id = :org;

Reporting queries commonly resolve the code combination identifiers to readable account strings by joining to GL_CODE_COMBINATIONS. A frequently used pattern joins the liability and discount accounts in a single pass:

• SELECT fsp.org_id, gcc1.concatenated_segments liability_account, gcc2.concatenated_segments discount_account FROM ap.financials_system_params_all fsp JOIN gl_code_combinations_kfv gcc1 ON fsp.accts_pay_code_combination_id = gcc1.code_combination_id JOIN gl_code_combinations_kfv gcc2 ON fsp.disc_taken_code_combination_id = gcc2.code_combination_id WHERE fsp.set_of_books_id = :ledger;

Other common scenarios include verifying encumbrance configuration before period close, confirming default currency and terms during an upgrade or new operating unit rollout, and validating that supplier number generation rules (USER_DEFINED_VENDOR_NUM_CODE, VENDOR_NUM_START_NUM, MANUAL_VENDOR_NUM_TYPE) align with the intended numbering scheme. Audit and migration projects frequently extract this table to compare configuration baselines across environments.

Related Objects

The following objects are the most significant dependencies, based on the documented foreign key relationships:

• GL_SETS_OF_BOOKS_11I – joined via SET_OF_BOOKS_ID.
• FND_CURRENCIES – referenced twice, via INVOICE_CURRENCY_CODE and PAYMENT_CURRENCY_CODE.
• GL_CODE_COMBINATIONS – referenced by numerous accounting columns, including ACCTS_PAY_CODE_COMBINATION_ID, PREPAY_CODE_COMBINATION_ID, DISC_TAKEN_CODE_COMBINATION_ID, RES_ENCUMB_CODE_COMBINATION_ID, RATE_VAR_CODE_COMBINATION_ID, RATE_VAR_GAIN_CCID, RATE_VAR_LOSS_CCID, EXPENSE_CLEARING_CCID, FUTURE_DATED_PAYMENT_CCID, MISC_CHARGE_CCID, and RETAINAGE_CODE_COMBINATION_ID.
• GL_ENCUMBRANCE_TYPES – referenced via REQ_ENCUMBRANCE_TYPE_ID, PURCH_ENCUMBRANCE_TYPE_ID, and INV_ENCUMBRANCE_TYPE_ID.
• HR_LOCATIONS_ALL – referenced via BILL_TO_LOCATION_ID and SHIP_TO_LOCATION_ID.

Application logic reads these parameters whenever an invoice, payment, or encumbrance entry is created, so any change to this table propagates directly into the Payables transaction defaults described above.