Results for “okl_bpd_active_csh_rls_v”

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

Overview

OKL_BPD_ACTIVE_CSH_RLS_V is a read-only database view owned by the APPS schema and delivered as part of the OKL – Lease and Finance Management module in Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is to present the set of currently active cash allocation rules. Only rules whose effective date range brackets the current system date (TRUNC(SYSDATE)) are surfaced, together with a synthetic "On Account" entry derived from the lookups table.

Cash allocation rules define how receipts or disbursements are applied within leasing and finance agreements — for example, whether an incoming payment is applied to open receivables, held, or posted to an on-account bucket. Because the view pre-filters by date validity and injects the on-account option, it is commonly used as an LOV source in forms, in concurrent program report queries, and as the driver of BPD (Business Process Definition) workflow logic. The view is registered in ETRM with status VALID and encapsulates the notion that at any point in time only a subset of configured allocation rules is eligible for use.

Underlying Base Objects

The view is defined over two principal OKL synonyms plus an FND lookups view:

• OKL_CSH_ALLCTN_RL_HDR (synonym for the cash allocation rule header table) — supplies the rule ID, name and description.
• OKL_CASH_ALLCTN_RLS_ALL (synonym for the cash allocation rules / effective-dates child table) — supplies the START_DATE, END_DATE and DEFAULT_RULE attributes matched by CAU_ID.
• FND_LOOKUPS — provides the "On Account" row via a UNION, filtered on LOOKUP_TYPE = 'OKL_CASH_APPL_RULE' and LOOKUP_CODE = 'ON_ACCOUNT'.
• FND_GLOBAL — referenced in the metadata (typically supplying ORG_ID context, though the view text joins ORG_ID from the header table directly).

The join is on A.ID = B.CAU_ID, enforced by an effective-date predicate. The second branch of the UNION fabricates a pseudo rule with ID1 = -1 and the lookup's MEANING/DESCRIPTION, guaranteeing that "On Account" is always offered regardless of the header table's contents.

Key Columns

• ID1 — Allocation rule identifier. Values greater than zero are real rule IDs; -1 marks the synthetic On Account option.
• ID2 — A constant '#' placeholder, used to distinguish or align the two UNION branches in downstream logic.
• NAME — Rule name from the header, or the lookup MEANING ("On Account") in the second branch.
• DESCRIPTION — Descriptive text for the rule or the lookup description.
• START_DATE / END_DATE — Effective period of the rule. END_DATE may be NULL, indicating an open-ended rule.
• DEFAULT_RULE — Flag indicating whether this is the default allocation rule for the context.
• ORG_ID — Operating unit / organisation identifier for multi-org filtering; NULL for the synthetic On Account row.

Common Use Cases and Queries

Typical usage includes populating a cash application rule LOV in a form, validating whether a rule was active on a given processing date, and reporting on the currently effective allocation set. Because the view already enforces the SYSDATE validity predicate, callers do not need to re-implement it.

• List all active cash allocation rules for an operating unit:

  SELECT id1, name, description, default_rule
  FROM   okl_bpd_active_csh_rls_v
  WHERE  org_id = :p_org_id
  ORDER BY name;

• Locate the synthetic On Account entry:

  SELECT id1, name
  FROM   okl_bpd_active_csh_rls_v
  WHERE  id1 = -1;

• Identify the default rule:

  SELECT name, start_date, end_date
  FROM   okl_bpd_active_csh_rls_v
  WHERE  default_rule = 'Y'
  AND    org_id = :p_org_id;

Because this is a UNION of two sources with no DML capability, it should be treated strictly as a query source. Applications requiring a binding write-back should target the base tables OKL_CSH_ALLCTN_RL_HDR and OKL_CASH_ALLCTN_RLS_ALL directly, applying their own effective-date and org-security rules.