Search Results okl_acc_gen_rules




Overview
Explore in AI Chat

Overview

OKL_ACC_GEN_RULES is the account generator rule header table within the Oracle E-Business Suite (EBS) Leasing and Finance Management (OKL) module. It defines the top-level rule definitions used by the Account Generator to derive accounting flexfield combinations for lease, finance, and contract transactions. These rules determine how the individual segments of the Accounting Key Flexfield are constructed — for example, deriving Company, Cost Center, Account, and Product segments from source attributes — so that downstream subledger and General Ledger postings are valid and consistent.

The table functions as the header or parent record for account generation logic in leasing. While the Account Generator framework itself is shared across EBS products, OKL_ACC_GEN_RULES provides the leasing-specific rule header information that ties rule definitions to the OKL transaction flow. From a Data Vault modeling perspective, the metadata classifies this object heuristically as a standalone structure; that classification suggests treating it as an independent hub-style reference entity rather than a dependent link or satellite, though this is a modeling suggestion only and should be validated against actual foreign-key dependencies in the target environment.

The table is documented as not implemented in the reference database. This means the structure may exist in the data dictionary but hold no active rows, or that the Account Generator may use an alternate configuration mechanism (such as the standard EBS Account Generator workflow) in that installation. Consultants should verify population on a per-environment basis before relying on it for reporting or integration.

Key Information Stored

The documented metadata identifies a primary key constraint, OKL_ACC_GEN_RULES_PK, defined on the ID column. This ID is a surrogate primary key — a system-generated numeric identifier — and should be treated as the unique row identifier rather than as a business-meaningful key. Because the excerpted metadata does not enumerate additional named columns, only the following can be stated with confidence:

  • ID — the surrogate primary key value that uniquely identifies each account generator rule header record. It is the join column used to associate header rules with their dependent detail or line definitions.

In the broader Account Generator pattern, a rule header of this type typically carries a rule name or identifier, an application context, an enabled/disabled status, and effective dating. However, those columns are not confirmed in the supplied ETRM metadata and should be confirmed through a DESCRIBE of the live table before being referenced in SQL. No documented unique business-key index was provided, so business-key candidates cannot be asserted from the available information.

Common Use Cases and Queries

The primary use case is auditing and troubleshooting Account Generator configuration to determine which accounting flexfield combinations are produced for lease transactions. A typical validation query confirms whether the reference implementation contains rows:

  • SELECT COUNT(*) FROM okl_acc_gen_rules;
  • SELECT id FROM okl_acc_gen_rules ORDER BY id;

Where detail tables exist, analysts join on the ID column to reconstruct the complete rule structure, for example joining the header to its rule-line counterpart to trace how each flexfield segment is sourced. Reporting use cases include documenting account generation logic for audit, comparing rule configuration across environments, and diagnosing unbalanced or invalid accounting combinations in lease postings.

Related Objects

The metadata describes OKL_ACC_GEN_RULES as standalone under the Data Vault heuristic, so no foreign-key relationships to other tables are documented. In practice, this header is referenced by detail or line-level account generator rule tables that join on the shared ID primary key value (for example, an OKL_ACC_GEN_RULES line table keyed by a rule ID column). Related objects commonly consulted alongside it include the Oracle Account Generator workflow definitions and the OKL contract and transaction tables that consume the resulting accounting combinations. Because these linkages are not confirmed in the supplied excerpt, they should be verified against the actual data dictionary before being used in production queries or integrations.