Search Results okl_service_fees_all_b

Overview

The OKL_SERVICE_FEES_ALL_B table is a core transactional entity within the Oracle E-Business Suite (EBS) Leasing and Finance Management (OKL) module. It serves as the primary repository for recording fees charged for services rendered. As a multi-organization enabled table, indicated by the "_ALL_B" suffix, it stores data across multiple operating units, a critical feature for enterprise-level leasing operations. This table is fundamental to the fee management lifecycle, capturing the financial details of service charges that are subsequently integrated into the Accounts Receivable (AR) invoicing process. Its existence is central to ensuring accurate billing and revenue recognition for ancillary services provided alongside or within leasing contracts.

Key Information Stored

While the provided metadata does not list specific columns, the table's primary key is documented as the ID column. Based on its role and standard Oracle EBS table conventions, this table typically stores essential attributes for a service fee transaction. These would logically include the fee amount, currency, the associated service type or product, a link to the originating contract or agreement (KHR_ID), and the date the fee was assessed. The table also contains standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) for auditing and the ORG_ID column to support multi-org architecture. The primary key, ID, uniquely identifies each service fee record in the system.

Common Use Cases and Queries

This table is primarily accessed for financial reporting, billing reconciliation, and audit inquiries related to service fees. Common operational scenarios include generating reports of all service fees charged within a specific period, reconciling fees billed to invoices created, and investigating fee-related entries for a particular contract. A typical query would join this table to the contract header (OKL_K_HEADERS_B) to analyze fees by customer or asset, or to the AR invoices table to verify billing status. For example, to list all service fees for a specific contract that have been invoiced, one might use a SQL pattern joining OKL_SERVICE_FEES_ALL_B (SF) to OKL_TRX_AR_INVOICES_B (INV) on SF.ID = INV.SVF_ID with a filter on the contract identifier.

Related Objects

The documented foreign key relationship explicitly defines this table's critical integration point. The primary key column (ID) of OKL_SERVICE_FEES_ALL_B is referenced by the SVF_ID column in the OKL_TRX_AR_INVOICES_B table. This relationship signifies that a service fee record stored in OKL_SERVICE_FEES_ALL_B can be linked to one or more Accounts Receivable invoice lines, facilitating the direct billing of these fees to customers. Beyond this documented relationship, this table is also conceptually related to the leasing contract headers (OKL_K_HEADERS_B) and likely interfaces with product and pricing setup tables within the OKL module to determine the fee calculation basis and rules.