Results for “processing_srl_number”

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

Overview

The OKL_BOOK_CONTROL_TRX_ALL table is a core transaction-staging object within the Oracle EBS Leasing and Finance Management (OKL) module. It is described in the ETRM documentation as the "OKL Booking Controller Transaction Table." Its functional purpose is to track the booking process as lease and finance contracts are passed through the Booking Controller. Each row represents a discrete unit of booking work — typically a contract, or a batch of contracts — and records the state of that work as it moves through the concurrent programs that perform the booking and accounting generation steps.

The table is owned by the OKL schema and contains 15 documented columns in the ETRM 12.2.2 physical model. It is present and valid in both Oracle EBS 12.1.1 and 12.2.2, making it a stable object across the two releases for reporting and diagnostics purposes.

The ETRM metadata provides a heuristic Data Vault classification of standalone for this object, mined from its foreign key structure. As a modeling suggestion, this implies the table has no strong hub or link characteristic within a Data Vault representation; it is best treated as an operational/transactional log rather than a master or relationship entity. Its single documented foreign key to OKL_PRTFL_CNTRCTS_B does, however, give it a soft association with the contract portfolio master.

Key Information Stored

The table's columns support both booking execution tracking and standard EBS audit requirements. The columns of greatest analytical importance are:

• KHR_ID — The contract identifier. This is the foreign key documented in the ETRM metadata, referencing OKL_PRTFL_CNTRCTS_B. It is the primary business-key candidate for linking a booking control transaction to its underlying contract.
• BATCH_NUMBER — The batch grouping used when booking is submitted as a set of contracts rather than individually.
• PROCESSING_SRL_NUMBER — A sequence number that orders processing steps within a batch or run, useful for reconstructing execution order.
• PROGRAM_NAME / PROG_SHORT_NAME — Identify the concurrent program that created or processed the record, enabling attribution of booking activity to a specific process.
• CONC_REQ_ID — The concurrent request ID, allowing the row to be tied back to the Concurrent Manager request that initiated processing; this is the standard anchor for troubleshooting failed or long-running booking jobs.
• PROGRESS_STATUS — The current state of the booking transaction (for example, pending, processing, complete, or error), and the primary filtering column for status reporting.
• ACTIVE_FLAG — Indicates whether the record is currently active, supporting soft-retention of historical booking attempts.
• USER_ID and ORG_ID — The requesting user and the operating unit / organization context in which the booking transaction was executed.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS "WHO" columns capturing creation and last-modification audit trail. LAST_UPDATE_DATE is frequently used for incremental extraction.

The table does not expose a documented surrogate single-column primary key in the ETRM metadata. In practice, rows are best identified by the combination of BATCH_NUMBER, PROCESSING_SRL_NUMBER, and CONC_REQ_ID, with KHR_ID providing the contract business key.

Common Use Cases and Queries

Typical scenarios include monitoring the progress of a booking run, diagnosing a contract that failed to book, and reconciling booking activity back to concurrent requests. The following query pattern lists pending or active booking transactions for a given batch:

• SELECT khr_id, batch_number, processing_srl_number, program_name, progress_status, conc_req_id, creation_date FROM okl_book_control_trx_all WHERE batch_number = :batch AND active_flag = 'Y' ORDER BY processing_srl_number;
• To trace a specific contract's booking history: SELECT ... WHERE khr_id = :khr_id ORDER BY creation_date DESC;
• To reconcile against Concurrent Manager output: join CONC_REQ_ID to FND_CONCURRENT_REQUESTS.REQUEST_ID and use LAST_UPDATE_DATE as the extraction watermark for incremental reporting.

Related Objects

The most significant objects associated with OKL_BOOK_CONTROL_TRX_ALL are:

• OKL_PRTFL_CNTRCTS_B — Referenced via KHR_ID; the contract portfolio master holding the lease/finance contract header.
• FND_CONCURRENT_REQUESTS — Joined on CONC_REQ_ID = REQUEST_ID to obtain program run status and timing.
• FND_USER — Joined on USER_ID for the requesting user identity.
• OKL_BOOK_CONTROL — Companion booking-control setup/definition object in the OKL schema.
• OKL_TRX_CONTRACTS / OKL_ACCOUNTING_GEN — Downstream objects populated by the booking process this table tracks.
• HR_OPERATING_UNITS — Joined on ORG_ID for operating-unit reporting context.