Results for “okl_gl_interface_uv”

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

Overview

OKL_GL_INTERFACE_UV is a reporting and integration view within the Oracle Lease and Finance Management (OKL) module. Its purpose is to expose the parameters required to drive the General Ledger (GL) interface process used by Lease and Finance Management when lease-related accounting entries must be transferred into Oracle General Ledger. In Oracle EBS 12.1.1 and 12.2.2, the OKL module maintains a set of system accounting options that govern how and when journal information is pushed to GL. The view surfaces a single logical control row containing the batch identifier, the accounting date range, account validation and GL transfer mode flags, a submit-journal-import flag, and the concurrent request identifier associated with that transfer run.

The view's distinctive characteristic, as documented in the ETRM metadata, is that it is defined with a WHERE 1=0 predicate over OKL_SYS_ACCT_OPTS. Consequently it is a structure-only (null-row) view: it always returns zero rows regardless of the underlying data. It exists to provide a stable, predefined column shape for the journal-import submission parameters rather than to return live accounting-option data. The metadata records that the view is "Not implemented in this database" in the environment captured, meaning the object is documented as part of the OKL schema definition but is not materialized as an active, invocable view in that particular instance. This is consistent with its purpose as a template or reference definition rather than an operational data source.

Underlying Base Objects

The only documented base object is OKL_SYS_ACCT_OPTS, the Lease and Finance Management table that stores system accounting options. The view declares no additional referenced base objects. Structurally, OKL_GL_INTERFACE_UV projects a fixed set of literals and pseudo-columns rather than selecting stored columns from OKL_SYS_ACCT_OPTS:

• BATCH_NAME — literal NULL
• FROM_DATE — TO_DATE(NULL)
• TO_DATE — TO_DATE(NULL)
• VALIDATE_ACCOUNT — literal 'N'
• GL_TRANSFER_MODE — literal 'N'
• SUBMIT_JOURNAL_IMPORT — literal 'N'
• REQUEST_ID — literal 0

Because these are constants and not references to columns of OKL_SYS_ACCT_OPTS, the FROM clause only supplies a source relation for the projection; no functional dependency on the table's rows exists. Combined with the 1=0 predicate, the definition guarantees an empty result set while preserving a typed, named column list.

Key Columns

The columns map directly to the parameters that the Lease and Finance Management journal-import submission process consumes:

• BATCH_NAME — the grouping identifier for the GL transfer batch; expected to be a character value naming the journal batch.
• FROM_DATE / TO_DATE — the accounting date range constraining which lease accounting entries are selected for transfer to GL.
• VALIDATE_ACCOUNT — a Y/N flag controlling whether GL account combinations are validated before the import is submitted.
• GL_TRANSFER_MODE — a mode indicator for how the transfer to the GL interface tables is performed.
• SUBMIT_JOURNAL_IMPORT — a Y/N flag indicating whether the Journal Import concurrent program should be launched automatically once the transfer completes. This column corresponds directly to the user query term "submit_journal_import," which is the parameter commonly set when driving the GL transfer programmatically.
• REQUEST_ID — the concurrent request identifier of the Journal Import program, used to track or reconcile the submitted request.

Common Use Cases and Queries

The view is typically referenced as a parameter container or structural contract rather than as a queryable data source. Because it returns no rows, standard reporting against it yields an empty result set by design; it is used to standardize the column interface for the GL interface submission. A representative query reflecting a submission/parameter pattern is:

• SELECT batch_name, from_date, to_date, validate_account, gl_transfer_mode, submit_journal_import, request_id FROM okl_gl_interface_uv; — returns no rows; used to confirm the parameter structure that callers expect.
• Application code or custom concurrent programs may select individual control values, for example SELECT submit_journal_import FROM okl_gl_interface_uv, treating the view as a defaulted control-row supplier.
• DBAs may query it diagnostically to verify that the object is defined and compiled, especially given that documentation records it as not implemented in at least one environment.

In summary, OKL_GL_INTERFACE_UV is a null-row, structure-only view over OKL_SYS_ACCT_OPTS that defines the batch, date-range, validation, transfer-mode, submit-journal-import, and request-id parameters governing the transfer of Lease and Finance Management accounting to Oracle General Ledger.