Search Results book_classification_code




Overview
Explore in AI Chat

Overview

OKL_REPORTS_B is a foundational table within the Oracle E-Business Suite Lease and Finance Management (OKL) module. It stores the basic descriptive definition of a report — the master catalog entry that identifies each reporting construct configured in the leasing application. In Oracle EBS 12.1.1 and 12.2.2, this table acts as the header or definition record for reports consumed by the leasing subsystem, providing the metadata (name, category, type, effective dating, and status) that downstream processes, concurrent programs, and inquiry screens use to resolve a report identifier into meaningful descriptive context.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign-key structure is standalone. This suggests that OKL_REPORTS_B behaves as an independent reference entity rather than a link joining two hubs or a satellite tracking descriptive history. Practically, it functions much like a hub or reference table: it holds a stable, uniquely identified business entity (a report) whose attributes may be referenced by other leasing objects but which does not itself aggregate multiple parents.

Key Information Stored

The table is documented with 16 columns. The most significant are:

Because OKL_REPORTS_B_U1 also covers REPORT_ID, no distinct natural business key is documented beyond the primary key itself; the name and code columns serve as the de facto business identifiers in application logic.

Common Use Cases and Queries

Typical usage centers on resolving a report identifier into its descriptive attributes for concurrent program parameters, responsibility-based inquiries, and reporting joins. A representative query retrieving active report definitions for a ledger is:

  • SELECT report_id, name, report_category_code, report_type_code FROM okl_reports_b WHERE ledger_id = :ledger AND status_code = 'ACTIVE' AND TRUNC(SYSDATE) BETWEEN effective_from_date AND NVL(effective_to_date, SYSDATE);
  • Reporting on report counts by category: SELECT report_category_code, COUNT(*) FROM okl_reports_b GROUP BY report_category_code;
  • Joining to accounting context: SELECT r.name, r.report_type_code, l.name ledger_name FROM okl_reports_b r, gl_ledgers l WHERE r.ledger_id = l.ledger_id;

These patterns support reconciliation, audit, and configuration-review reporting, and are frequently embedded in custom BLANKET or inquiry reports within the OKL module.

Related Objects

The documented foreign-key relationship links OKL_REPORTS_B.CHART_OF_ACCOUNTS_ID to GL_MGT_SEG_UPGRADE_H, tying report definitions to the accounting segment upgrade structure used during ledger migration. Beyond this explicit relationship, the table's LEDGER_ID and CHART_OF_ACCOUNTS_ID columns logically join to GL_LEDGERS and GL chart-of-accounts entities. Child or dependent objects referencing REPORT_ID would include leasing report detail and layout tables, concurrent program parameter definitions, and OKL inquiry views that resolve report metadata. In 12.2.2 the table's 16 documented columns and single primary key remain consistent with the ETRM reference, positioning OKL_REPORTS_B as a stable configuration cornerstone for Lease and Finance Management reporting.