Results for “okl_book_controller_trx_v”

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

Overview

OKL_BOOK_CONTROLLER_TRX_V is an Oracle EBS APPS-owned view within the OKL (Leasing and Finance Management) module. It presents book controller transaction data, exposing records from the underlying book controller transaction table joined to Oracle Application Object Library lookup data to resolve internal status codes into user-facing meanings. The view is a reporting and integration aid: rather than requiring downstream consumers to join the base transaction table to FND_LOOKUPS manually, it delivers a denormalized result set in which the progress status code is paired with its descriptive meaning.

Because users frequently search for the PROGRESS_STATUS attribute, this view is particularly relevant when monitoring the lifecycle of book controller processing jobs. Each row represents a book controller transaction tied to a batch, a concurrent request, and a program, with its current processing state surfaced via the joined lookup meaning. The view is defined in the APPS schema and is marked VALID in the ETRM 12.2.2 metadata.

Underlying Base Objects

The documented base objects referenced by this view are:

• OKL_BOOK_CONTROLLER_TRX (SYNONYM) — the primary driving table, aliased TRX, supplying transaction, batch, program, and status columns.
• FND_LOOKUPS (VIEW) — aliased FNDT, joined to translate the PROGRESS_STATUS code into a descriptive lookup meaning using lookup type OKL_BKG_CONTL_STATUS.
• FND_GLOBAL (PACKAGE) — the standard Oracle EBS context package referenced for session/environment values such as ORG_ID.

The join condition restricts rows to the book controller status lookup set: FNDT.LOOKUP_TYPE = 'OKL_BKG_CONTL_STATUS' AND FNDT.LOOKUP_CODE = TRX.PROGRESS_STATUS. This means only transactions whose PROGRESS_STATUS has a matching, defined lookup code are returned, and the descriptive meaning is always available alongside the code.

Key Columns

• USER_ID — the user associated with the transaction.
• ORG_ID — the operating unit/organization identifier, supporting multi-org filtering.
• BATCH_NUMBER — the book controller batch to which the transaction belongs.
• PROCESSING_SRL_NUMBER — a serial/sequence number for processing within the batch.
• KHR_ID — the key identifier linking to the relevant book controller or lease record.
• PROGRAM_NAME and PROG_SHORT_NAME — the concurrent program name and its short name.
• CONC_REQ_ID — the concurrent request identifier for tracing the originating job.
• PROGRESS_STATUS — the coded processing state (the column most commonly searched).
• STATUS_MEANING — the decoded, descriptive status derived from the OKL_BKG_CONTL_STATUS lookup.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.
• ACTIVE_FLAG — indicates whether the transaction is active.

Common Use Cases and Queries

Typical scenarios include monitoring book controller batch processing, troubleshooting jobs by concurrent request, and reporting transaction status counts by operating unit.

Status distribution by operating unit:

• SELECT ORG_ID, PROGRESS_STATUS, STATUS_MEANING, COUNT(*) FROM OKL_BOOK_CONTROLLER_TRX_V GROUP BY ORG_ID, PROGRESS_STATUS, STATUS_MEANING;

Tracing a specific batch or concurrent request:

• SELECT BATCH_NUMBER, PROCESSING_SRL_NUMBER, PROGRAM_NAME, CONC_REQ_ID, PROGRESS_STATUS, STATUS_MEANING FROM OKL_BOOK_CONTROLLER_TRX_V WHERE BATCH_NUMBER = :batch;
• SELECT CONC_REQ_ID, PROG_SHORT_NAME, PROGRESS_STATUS, STATUS_MEANING FROM OKL_BOOK_CONTROLLER_TRX_V WHERE CONC_REQ_ID = :req_id;

Finding active transactions only:

• SELECT USER_ID, BATCH_NUMBER, KHR_ID, STATUS_MEANING FROM OKL_BOOK_CONTROLLER_TRX_V WHERE ACTIVE_FLAG = 'Y';

Because the join is an inner join against FND_LOOKUPS, ensure the OKL_BKG_CONTL_STATUS lookup contains the relevant codes; otherwise such transactions will not appear in the view output.