Results for “okl_disb_rules_v”

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

Overview

OKL_DISB_RULES_V is a consolidated, language-aware reporting view owned by the APPS schema within the Oracle Lease and Finance Management (OKL) product family. It presents disbursement rule definitions used by ETRM to control how disbursement transactions are grouped, timed, and released. Disbursement rules allow finance users to automate the consolidation of payable items — typically fees, charges, and other disbursement elements — into a single payment or disbursement event based on criteria such as due date, streaming type, or a recurring schedule. The view joins the base transaction table with its translation table to expose both the functional rule setup and a language-specific description, filtered to the session language via USERENV('LANG'). Because it is a view rather than a table, it is read-only and is intended for inquiry, reporting, and integration extraction rather than maintenance. The presence of the DAY_OF_MONTH column — the term the user searched — reflects its role as a scheduling attribute that specifies which calendar day a recurring disbursement rule should be executed or consolidated. The view is documented as VALID in EBS 12.1.1 and 12.2.2, and its structure is consistent across both releases.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through APPS synonyms:

• OKL_DISB_RULES_ALL_B — the multi-org base table holding rule header attributes, including the DAY_OF_MONTH scheduling column, fee configuration, frequency, and descriptive flexfield (DFF) attribute columns 1 through 15.
• OKL_DISB_RULES_TL — the translation table holding RULE_NAME and DESCRIPTION in each installed language.

The join condition is DRAB.DISB_RULE_ID = DRAT.DISB_RULE_ID AND DRAT.LANGUAGE = USERENV('LANG'), ensuring that only the current-language translation row is returned for each rule. The DRAB.ROWID is aliased as ROW_ID to provide a stable row identifier for downstream processing. The _B and _TL suffix conventions confirm that rule definitions and their translations are maintained separately, a standard EBS pattern.

Key Columns

• DISB_RULE_ID — primary identifier linking the base and translation records.
• ROW_ID, OBJECT_VERSION_NUMBER — row locator and optimistic-locking token.
• RULE_NAME, DESCRIPTION — user-facing rule label and narrative, sourced from the translation table.
• ORG_ID — operating unit that owns the rule, indicating multi-org partitioning.
• START_DATE, END_DATE — effective period during which the rule is active.
• DAY_OF_MONTH — the calendar day on which a monthly or recurring disbursement is scheduled; the primary term of interest for scheduling queries.
• SCHEDULED_MONTH — the target month for annual or periodic rules.
• FREQUENCY — interval at which the rule executes.
• CONSOLIDATE_BY_DUE_DATE, CONSOLIDATE_STRM_TYPE — consolidation control flags and streaming type grouping.
• FEE_OPTION, FEE_BASIS, FEE_AMOUNT, FEE_PERCENT — fee calculation parameters applied to the rule.
• SFWT_FLAG — sourced from the translation table, indicating special handling characteristics.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield segments.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Reporting scenarios include listing all active disbursement rules by operating unit, identifying rules scheduled on a particular day of the month, and reconciling consolidation settings for disbursement processing.

Example — locate rules scheduled for a specific day of month:

• SELECT disb_rule_id, rule_name, org_id, frequency, day_of_month, start_date, end_date FROM okl_disb_rules_v WHERE day_of_month = :p_day AND NVL(end_date, SYSDATE) >= SYSDATE;

Example — active rules for a given operating unit with consolidation detail:

• SELECT rule_name, fee_option, fee_basis, fee_amount, fee_percent, consolidate_by_due_date, consolidate_strm_type FROM okl_disb_rules_v WHERE org_id = :p_org_id ORDER BY rule_name;

Because the view applies the language filter automatically, no additional language predicate is required. Direct DML against the view is not supported; maintenance is performed through the underlying base and translation tables or the corresponding OKL application forms.