Search Results default_rule




Overview
Explore in AI Chat

Overview

The APPS.OKL_BPD_ACTIVE_CSH_RLS_V view is a reporting and integration construct within the Oracle E-Business Suite (EBS) Lease and Finance Management (OKL) module, part of the Enterprise Tax and Revenue Management (ETRM) family of applications. It exposes the set of currently active cash allocation rules that are available for application against lease and finance contracts. The view is designed to return only those allocation rules whose effective date window includes the current system date (TRUNC(SYSDATE)), thereby providing a runtime-valid list of allocation rules without requiring callers to perform their own date filtering.

A distinguishing characteristic of this view is its use of a UNION to append a synthetic "On Account" allocation rule sourced directly from the FND_LOOKUPS lookup type OKL_CASH_APPL_RULE. This rule, identified by the lookup code ON_ACCOUNT, is not stored in the transactional allocation rule tables but is treated as a system-defined allocation rule equivalent in status to user-defined active rules. This design reflects the fact that the "on account" cash application behavior is a functional constant in Oracle Lease Management rather than a configurable record, yet it must appear alongside active rules in user-facing selection lists.

Underlying Base Objects

The view is defined over the following documented base objects:

  • OKL_CSH_ALLCTN_RL_HDR (synonym) — the cash allocation rule header entity, supplying the rule ID, name, description, and ORG_ID (operating unit) attributes via aliases A.ID, A.NAME, A.DESCRIPTION, and A.ORG_ID.
  • OKL_CASH_ALLCTN_RLS_ALL (synonym) — the cash allocation rules "all" entity, joined on A.ID = B.CAU_ID, providing the effective date range (START_DATE, END_DATE) and the DEFAULT_RULE indicator.
  • FND_LOOKUPS (view) — the Oracle Applications lookup values view, from which the hard-coded ON_ACCOUNT row is drawn under LOOKUP_TYPE = 'OKL_CASH_APPL_RULE'.
  • FND_GLOBAL (package) — referenced for session context such as org_id resolution and responsibility-based security, though it does not appear as an explicit join in the SQL text.

Because the header and associated rows are exposed through synonymized base objects, the view respects the standard OKL data model where a rule header is paired with one or more dated rule lines. Only rules whose date window is currently open are returned from the base tables.

Key Columns

  • ID1 — The allocation rule identifier. For real rules this is A.ID; for the synthetic ON_ACCOUNT row it is the sentinel value -1, which callers can use to detect the special "on account" selection.
  • ID2 — A constant '#' placeholder column, typically used by LOV and list-of-values frameworks for concatenation or display purposes.
  • NAME — The rule name. For the ON_ACCOUNT row this is populated from the lookup MEANING.
  • DESCRIPTION — Descriptive text for the rule; for the lookup-derived row it is drawn from the lookup DESCRIPTION.
  • START_DATE / END_DATE — The effective date window of the rule. These are NULL for the synthetic ON_ACCOUNT row since it has no configurable date range.
  • DEFAULT_RULE — Indicator marking whether the rule is the default allocation rule for its operating unit. NULL for the ON_ACCOUNT row.
  • ORG_ID — The operating unit (legal entity/business unit) to which the rule belongs. NULL for the synthetic row, which is applicable across all orgs.

Common Use Cases and Queries

This view is most commonly consumed by cash application screens, allocations setups, and integrations that need to present a valid list of allocation rules to a user or process. A typical query retrieves active rules for the current operating unit, with the ON_ACCOUNT entry always appearing:

SELECT id1, name, description, start_date, end_date, default_rule
FROM   apps.okl_bpd_active_csh_rls_v
WHERE  org_id = :org_id OR org_id IS NULL
ORDER  BY name, start_date DESC;

Because the ON_ACCOUNT row carries ID1 = -1, it is frequently excluded when only real allocation rules are required, or explicitly included when representing "apply cash on account" as a valid allocation outcome:

SELECT * FROM apps.okl_bpd_active_csh_rls_v
WHERE  id1 = -1;

The view is also useful for auditing which allocation rules were active on a given date, although callers must remember that date filtering is by SYSDATE and the ON_ACCOUNT row is always present regardless of date.