Search Results okl_trx_types_b

Overview

The OKL_TRX_TYPES_B table is a core master data table within the Oracle E-Business Suite (EBS) Leasing and Finance Management (OKL) module. It serves as the central repository for defining and maintaining transaction types that govern the financial and operational activities throughout the leasing lifecycle. These transaction types are fundamental control points, dictating the accounting, tax, and processing rules for various transactions such as invoices, payments, asset additions, and contract modifications. The table's role is pivotal, as its primary key (ID) is extensively referenced across the OKL schema to classify and control transaction processing.

Key Information Stored

While the provided ETRM excerpt does not list individual columns, the documented primary and foreign key relationships reveal its critical structure. The table's primary key is the ID column, uniquely identifying each transaction type record. A significant design aspect is the table's self-referential relationship, managed through the TRY_ID and TRY_ID_FOR columns. This hierarchical structure allows for the creation of parent-child relationships between transaction types, enabling complex categorization. The existence of a unique key (TRY_AEX_UK) on the combination of TRY_ID and TRY_ID_FOR further enforces data integrity within this hierarchy. The data stored for each transaction type record typically includes a code, name, description, active status, and other attributes that define the transaction's behavior within the system.

Common Use Cases and Queries

This table is primarily referenced in configuration and transactional reporting. A common use case is querying active transaction types for setup or audit purposes. For instance, to list all transaction types and their potential parent relationships, one might execute: SELECT id, name, code, try_id, try_id_for FROM okl_trx_types_b WHERE NVL(active_flag,'Y') = 'Y';. Another critical scenario involves troubleshooting accounting or tax issues by identifying all transactions of a specific type. A join to a transactional table like OKL_TRX_CONTRACTS would be essential: SELECT trx.* FROM okl_trx_contracts trx, okl_trx_types_b typ WHERE trx.try_id = typ.id AND typ.code = 'LEASE_INCEPTION';. Implementation teams use this table extensively when defining accounting rules, tax sources, and external system mapping for payables, receivables, and fixed assets.

Related Objects

The OKL_TRX_TYPES_B table has a vast number of foreign key relationships, underscoring its central role. Key related objects include:

• Self-Reference: OKL_TRX_TYPES_B references itself via TRY_ID and TRY_ID_FOR for hierarchical data.
• Accounting Setup: OKL_AE_TEMPLATES_ALL, OKL_TRX_ACCT_OPTS (and _ALL), which link transaction types to accounting templates and options.
• Transactional Headers: OKL_TRX_CONTRACTS (and _ALL), OKL_TRX_AR_INVOICES_B, OKL_TRX_AP_INVOICES_B (and _ALL), which classify transactions.
• External System Integration: OKL_EXT_AP_HEADER_SOURCES_B, OKL_EXT_AR_HEADER_SOURCES_B, OKL_EXT_FA_HEADER_SOURCES_B, for mapping to Payables, Receivables, and Assets.
• Tax Configuration: OKL_TAX_SOURCES (and _T), OKL_TAXBASISOVERRIDE_ALL, OKL_TAX_BASIS_OVERRIDE, which define tax treatment by transaction type.
• Other Configuration: OKL_TXL_QUOTE_LINES_B (and _ALL), OKL_LS_RT_FCTR_SETS_B, OKL_TBC_DEFINITIONS, linking to quoting, rate factors, and tax basis calculations.

The consistent join column across almost all these relationships is the TRY_ID column referencing the primary key (ID) of OKL_TRX_TYPES_B.