Search Results okl_sys_acct_opts_all




Overview
Explore in AI Chat

Overview

OKL_SYS_ACCT_OPTS_ALL is the system accounting options table within the Oracle E-Business Suite Leasing and Finance Management (OKL) module. It stores the accounting configuration that governs how the leasing application derives, posts, and reconciles financial entries across contracts, receivables, payables, and the general ledger. Because leasing activity generates a continuous stream of cash flows, accruals, tax implications, and multi-currency settlements, the OKL module requires a centralized repository defining which accounts, currencies, rounding rules, and precision thresholds apply. This table fulfills that role, functioning as the accounting engine's control record set at the operating unit and ledger level.

The object resides in the OKL schema and is documented as VALID under ETRM 12.2.2, with 59 physical columns. Its primary key is OKL_SYS_ACCT_OPTS_ALL_PK, defined on the ID column, and a unique index OKL_SYS_ACCT_OPTS_ALL_U1 also covers ID. The heuristic Data Vault classification mined from the foreign key structure is standalone. From a modeling perspective, this suggests the table behaves as a self-contained reference or configuration satellite rather than participating in a hub-and-link network; it should be treated as a satellite-style configuration entity keyed by its own surrogate identifier, with ORG_ID and SET_OF_BOOKS_ID acting as natural business qualifiers rather than foreign-key dependencies to other hubs.

Key Information Stored

The table blends surrogate identity, ledger context, and account derivation settings. The most consequential columns include:

The remaining columns are primarily DFF attributes (ATTRIBUTE_CATEGORY, ATTRIBUTE1–15), audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN), and OBJECT_VERSION_NUMBER for optimistic locking.

Common Use Cases and Queries

Typical usage revolves around auditing accounting setup, troubleshooting posting failures, and confirming account derivation for a given operating unit.

SELECT org_id,
       set_of_books_id,
       code_combination_id,
       rec_ccid,
       liablity_ccid,
       tax_ccid,
       cc_rep_currency_code,
       ael_rep_currency_code
FROM   okl.okl_sys_acct_opts_all
WHERE  org_id = :p_org_id;

Reconciliation reports frequently join CODE_COMBINATION_ID values to GL_CODE_COMBINATIONS to display the human-readable account string. Another common pattern inspects rounding and precision configuration to explain small residual differences during multi-currency lease settlements:

SELECT cc_rounding_rule, cc_precision, cc_min_acct_unit,
       ael_rounding_rule, ael_precision, ael_min_acct_unit
FROM   okl.okl_sys_acct_opts_all
WHERE  set_of_books_id = :p_ledger;

Because the table is standalone and small, it is well suited to being cached in concurrent programs and form personalizations that need default account values during contract booking.

Related Objects

Given the ETRM metadata classifies this table as standalone, no formal foreign keys originating within it are documented. The relationships below are therefore functional rather than enforced by constraint definitions:

  • GL_CODE_COMBINATIONS — Resolves CODE_COMBINATION_ID, REC_CCID, LIABLITY_CCID, TAX_CCID, ROUNDING_CCID, AR_CLEARING_CCID, and AP_CLEARING_CCID into account segment strings.
  • GL_SETS_OF_BOOKS — Joined on SET_OF_BOOKS_ID to validate the target ledger.
  • HR_OPERATING_UNITS — Joined on ORG_ID to resolve the owning operating unit.
  • FND_CURRENCIES — Joined on CC_REP_CURRENCY_CODE and AEL_REP_CURRENCY_CODE to obtain currency names and precision defaults.
  • OKL_CONTRACTS — Lease contracts that inherit the accounting options configured here during booking and accounting generation.
  • OKL_ACCOUNTING_GEN_PVT — The accounting generation package that reads these options to derive and post lease journal entries.
  • OKL_SYS_ACCT_OPTS_TL — Translation table that may accompany the base table for descriptive option text.

Because the object is configuration-driven rather than transactional, most dependencies are mediated through the OKL accounting subsystems and GL integration points rather than direct relational constraints.