Results for “okl_service_fees_b”

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

Overview

OKL_SERVICE_FEES_B is a base table within the Oracle E-Business Suite (EBS) Leasing and Finance Management (OKL) module. It stores the fee charged for service rendered, functioning as the transaction-level repository for service-based fee records associated with leasing and finance contracts. In the OKL data model, service fees represent ancillary charges applied to contracts for services such as maintenance, inspection, documentation, or other value-added activities performed by the lessor or a third party. The table forms part of the broader fee and pricing architecture that supports contract generation, billing, and accounting.

The heuristic Data Vault classification for this object is standalone, derived from its foreign key structure. This suggests, as a modeling exercise, that OKL_SERVICE_FEES_B behaves as an independent entity rather than a dependent child in the mined FK graph. Modelling it as a standalone hub-style structure may be appropriate where no inbound or outbound foreign key relationships were detected at the time the metadata was mined. Practitioners should note that this classification is heuristic and should be validated against the live schema before relying on it for integration or data-warehouse design.

Key Information Stored

Because the object is documented as "Not implemented in this database" within the source metadata, the column list is limited. The primary key and its documented column are the authoritative data points:

• ID — Surrogate primary key, defined by the constraint OKL_SERVICE_FEES_B_PK. This is the system-generated unique identifier for each service fee row and is the recommended join key in all downstream queries.

Note that no business-key unique index (such as a contract ID plus service type combination) is documented in the ETRM metadata. Where such natural keys exist in a populated environment, they typically combine the owning contract identifier with a service or fee type code; however, these cannot be confirmed from the provided source and should be verified against the actual database dictionary. The absence of documented business keys, coupled with the standalone classification, reinforces that ID is the primary referential anchor.

Common Use Cases and Queries

Service fee data supports reporting on ancillary revenue, contract-based fee analysis, and reconciliation between the leasing sub-ledger and billing. Typical scenarios include listing all service fees for a contract, aggregating fee revenue by service category or period, and auditing fee records for completeness before billing runs.

A representative query pattern, using the documented primary key for lookup, is:

• SELECT ID FROM OKL_SERVICE_FEES_B WHERE ID = :p_id; — direct surrogate-key retrieval.
• SELECT b.ID FROM OKL_SERVICE_FEES_B b WHERE EXISTS (SELECT 1 FROM ... ); — correlated patterns where the base table is joined to contract headers or fee lines via IDs confirmed in the live schema.

Because only the primary key column is documented, precise join predicates cannot be asserted from the ETRM metadata alone. When implementing reports, teams should confirm the actual column names and relationships against ALL_TAB_COLUMNS and the constraint definitions before writing production SQL. Standard EBS multi-org and security predicates may also apply.

Related Objects

The mined relationship data classifies OKL_SERVICE_FEES_B as standalone, meaning no foreign key relationships were detected. Consequently, the set of confirmed related objects is minimal. In practice, the most significant objects that reference or depend on this table are identified through application logic and the wider OKL fee structure rather than through the mined FK graph. These include the contract and fee processing entities and views within the OKL module, such as contract header/version tables and fee line or pricing interfaces, together with any concurrent programs and APIs that create or consume service fee records.

• OKL_SERVICE_FEES_B — the base (transaction) table itself, keyed by ID.
• Contract header/version objects in OKL — logical parent candidates in application terms, though not FK-confirmed here.
• Fee line and pricing objects in OKL — sibling components of the fee architecture.
• OKL reporting views and concurrent programs — consumers of service fee data.

Given the standalone classification and the absence of documented foreign keys, implementers should treat any join to contract or fee entities as needing explicit validation. Confirming the true parent-child relationships through the actual constraint data is essential before building dependent interfaces, extracts, or Data Vault links.