Search Results accrual_date

Overview

OKL_GEN_ACCRUALS_UV is a view within the Oracle Leasing and Finance Management (OKL) module, delivered as part of Oracle E-Business Suite releases 12.1.1 and 12.2.2. The view is identified as a "User View" (denoted by the _UV suffix), a naming convention Oracle commonly applies to simplified, user-facing query definitions that abstract underlying complexity from the base transactional tables. In the context of OKL, this view is associated with accrual processing, which drives the recognition of accrued interest, income, and expense across lease and finance contracts.

The view exposes three columns: BATCH_NAME, ACCRUAL_DATE, and REQUEST_ID. Its definition is intentionally constrained, selecting only from OKL_SYS_ACCT_OPTS filtered by the predicate WHERE 1 = 0. This predicate causes the view to return no rows in a standard runtime environment; the construction is characteristic of a metadata or placeholder definition rather than an operational data source. Per the documented ETRM metadata, the view is "Not implemented in this database," confirming it is a template object that may be materialized or extended under specific configurations.

Because the searched term was "accrual_date," this view is directly relevant to users investigating how the ACCRUAL_DATE attribute is surfaced and consumed in OKL reporting and integration logic. It serves as a structural reference for accrual-related columns rather than a populated reporting source.

Underlying Base Objects

The documented view text references a single base object: OKL_SYS_ACCT_OPTS, which is the OKL system accounting options table. This table stores configuration and system-level accounting parameters used throughout the leasing module. No other base tables, synonyms, or referenced objects are documented in the ETRM metadata for this view; the referenced base object listing confirms that no additional dependencies are recorded beyond OKL_SYS_ACCT_OPTS.

The join relationship is effectively a single-table projection. The view does not join to contract, stream, or accrual detail tables such as OKL_TRX_ACCRUALS or OKL_ACCRUAL_HEADERS, which are the tables typically expected to carry transactional accrual data. Instead, it derives its three columns using literals and expressions: NULL for BATCH_NAME, SYSDATE for ACCRUAL_DATE, and 0 for REQUEST_ID. This design indicates the view acts as a stub or reference structure rather than a traversal of accrual records.

Key Columns

• BATCH_NAME — Exposed as a NULL literal. In an operational accrual context, a batch name would identify the concurrent or batch process that generated accrual entries, enabling traceability back to a specific run. Here it functions as a placeholder for schema compatibility.
• ACCRUAL_DATE — Exposed via the SYSDATE function, returning the current database system date. This is the column most relevant to the "accrual_date" search. In a live implementation, it would represent the effective date on which accruals are recognized; in this view definition it dynamically reflects the query execution date.
• REQUEST_ID — Exposed as a zero literal. In standard Oracle EBS architecture, REQUEST_ID links rows to a concurrent program invocation recorded in FND_CONCURRENT_REQUESTS. The zero placeholder indicates no genuine concurrent request association is maintained by this definition.

Common Use Cases and Queries

The view's principal utility is diagnostic and structural. Developers and functional analysts investigating how ACCRUAL_DATE is exposed across OKL objects can query this view to confirm column names and data types, particularly when building extensions, custom reports, or integrations that must conform to OKL accrual schemas.

A typical query to inspect the view's structure and returned values is:

• SELECT BATCH_NAME, ACCRUAL_DATE, REQUEST_ID FROM OKL_GEN_ACCRUALS_UV; — retrieves the placeholder columns, returning the current system date for ACCRUAL_DATE.
• SELECT ACCRUAL_DATE FROM OKL_GEN_ACCRUALS_UV WHERE ACCRUAL_DATE = TRUNC(SYSDATE); — demonstrates the date predicate, though no rows persist because of the internal restriction.

Because the view is documented as not implemented and returns no data by design, it should not be relied upon as a production reporting source. For actual accrual reporting, users should reference the populated OKL transactional accrual tables. This view remains valuable as a canonical reference for the ACCRUAL_DATE column definition within the OKL module.