Results for “tax_upfront_sty_id”

20 results




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

Overview

OKL_SYSTEM_PARAMS_ALL is the central configuration table within the Oracle E-Business Suite (EBS) Leasing and Finance Management (OKL) module. It stores the parameters that govern how the leasing and finance application behaves across an operating unit, covering lease origination, tax handling, invoice generation, asset depreciation, remittance processing, and quoting workflows. Because the table is suffixed _ALL, it is designed to hold one or more rows per operating unit, keyed by ORG_ID, allowing different business units to operate under distinct parameter sets. The object is owned by the OKL schema and is marked VALID in ETRM 12.2.2 documentation, with 63 documented columns.

From a Data Vault modeling perspective, the heuristic classification of OKL_SYSTEM_PARAMS_ALL is satellite-leaning. It carries descriptive attributes and foreign-key references to other entities, and its two unique indexes (OKL_SYSTEM_PARAMS_ALL_U1 on ORG_ID and OKL_SYSTEM_PARAMS_ALL_U2 on ID) suggest a business-key candidate on ORG_ID supported by a surrogate primary key. Analysts modeling this object in a Data Vault context should therefore treat it as a satellite attached to an operating-unit hub rather than as a hub or link.

Key Information Stored

The most significant attributes relate to operational and financial defaults. The primary key is ID, enforced by OKL_SYS_PARAMS_PK. Two unique indexes exist: OKL_SYSTEM_PARAMS_ALL_U1 on ORG_ID acts as the primary business-key candidate, and OKL_SYSTEM_PARAMS_ALL_U2 on ID is effectively the surrogate key uniqueness constraint.

Standard EBS audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER) and the DFF attribute columns (ATTRIBUTE_CATEGORY, ATTRIBUTE1–15) are also present.

Common Use Cases and Queries

The most frequent use is retrieving a single operating unit's configuration to drive downstream logic or reporting. A typical query is:

  • SELECT * FROM OKL.OKL_SYSTEM_PARAMS_ALL WHERE org_id = :p_org_id;
  • Reporting on tax behavior: SELECT org_id, tax_upfront_yn, tax_invoice_yn, tax_schedule_yn FROM okl_system_params_all;
  • Joining to the stream type master to resolve the upfront tax stream: SELECT p.org_id, s.stream_type_code FROM okl_system_params_all p, okl_strm_type_b s WHERE p.tax_upfront_sty_id = s.id;
  • Resolving task templates: SELECT p.org_id, t.group_name FROM okl_system_params_all p, jtf_task_temp_groups_b t WHERE p.task_template_group_id = t.group_id;
  • Auditing changes: SELECT org_id, last_updated_by, last_update_date FROM okl_system_params_all ORDER BY last_update_date DESC;

Related Objects

The following objects are the most significant dependencies based on the documented FK relationships and the broader OKL model.

Together these relationships confirm OKL_SYSTEM_PARAMS_ALL as the configuration backbone for leasing and finance transactions, providing the defaults, tax rules, and sequence-prefix definitions consumed by virtually every OKL business process.