Results for “okl_tbc_definitions”

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

Overview

OKL_TBC_DEFINITIONS is a configuration table within the Oracle E-Business Suite Leasing and Finance Management (OKL) module. The name reflects the "TBC" construct — typically understood as "Third-Party Billing" or a related billing/charge definition context — and the table stores definitional records that bind an OKL product to a stream type, transaction type, and an external vendor site. In practical terms, it acts as a cross-reference or linkage table that governs how certain leasing and finance transactions are attributed to third-party service providers identified through Oracle Payables' supplier site master.

The ETRM metadata classifies this object — by heuristic data-mining of its foreign-key structure — as a link table in Data Vault terms. That is a modeling suggestion rather than a physical design statement: the table's purpose is to associate multiple independent business entities (product, stream type, transaction type, and vendor site) rather than to hold a single natural key or descriptive history. It is not implemented in the standard shipped database and is created or populated only where the corresponding OKL functionality is configured.

Key Information Stored

The documented metadata identifies the following structural elements. The surrogate primary key is OKL_TBC_PK, with TBC_CODE serving as the business-key candidate (unique identifier) for each definition record.

• TBC_CODE — the user-meaningful code uniquely identifying each TBC definition; the primary business-key candidate.
• PDT_ID — foreign key to OKL_PRODUCTS, identifying the leasing/finance product to which the definition applies.
• STY_ID — foreign key to OKL_STRM_TYPE_B, identifying the stream type associated with the definition.
• TRY_ID — foreign key to OKL_TRX_TYPES_B, identifying the transaction type governing the definition's use.
• VENDOR_SITE_ID — foreign key to PO_VENDOR_SITES_ALL, identifying the supplier site (third-party vendor) tied to the definition.
• OKL_TBC_PK — the surrogate primary key column for the table.

Because the metadata is intentionally limited, additional descriptive columns (such as effective dates, enabled flags, and audit columns) are not enumerated here. Analysts should always query ALL_TAB_COLUMNS for OKL_TBC_DEFINITIONS in a live environment to confirm the full column list before writing scripts.

Common Use Cases and Queries

Typical reporting and reconciliation scenarios involve tracing which products, stream types, and transaction types are bound to a given vendor site, or conversely which vendor sites are in use for a product. A representative query joins the definition table to its parents to resolve codes:

• Vendor attribution report: join OKL_TBC_DEFINITIONS to PO_VENDOR_SITES_ALL on VENDOR_SITE_ID to list definitions by supplier site.
• Product-to-stream mapping: join to OKL_PRODUCTS on PDT_ID and OKL_STRM_TYPE_B on STY_ID to validate configuration completeness.
• Transaction type analysis: join to OKL_TRX_TYPES_B on TRY_ID to group definitions by transaction type.
• Configuration audit: select TBC_CODE with all FK columns to detect orphaned or duplicate definition codes.

A sample pattern: SELECT d.tbc_code, p.name, s.stream_type, t.trx_type, v.vendor_site_code FROM okl_tbc_definitions d, okl_products p, okl_strm_type_b s, okl_trx_types_b t, po_vendor_sites_all v WHERE d.pdt_id = p.pdt_id(+) AND d.sty_id = s.sty_id(+) AND d.try_id = t.try_id(+) AND d.vendor_site_id = v.vendor_site_id(+). Outer joins are advisable because not all FK columns are mandatory in every configuration.

Related Objects

The following tables are the most significant related objects, each joined via the documented foreign keys:

• OKL_PRODUCTS — parent of PDT_ID; defines the leasing/finance product.
• OKL_STRM_TYPE_B — parent of STY_ID; defines stream types.
• OKL_TRX_TYPES_B — parent of TRY_ID; defines transaction types.
• PO_VENDOR_SITES_ALL — parent of VENDOR_SITE_ID; the Oracle Payables supplier site master.

Because OKL_TBC_DEFINITIONS is a link-style table, dependent child objects are unlikely; its principal value lies in the joins it enables across the OKL product/stream/transaction model and the Payables vendor master.