Results for “tas_type”

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

Overview

OKL_TRX_ASSETS is a top-level transaction table within the Oracle E-Business Suite Leasing and Finance Management (OKL) module. Its stated purpose is to group all transactions that contribute to the creation of asset lines for a Lease or Loan contract. In practical terms, the table acts as a transaction header or grouping construct: a single row in OKL_TRX_ASSETS represents a transaction event that may subsequently spawn one or more asset lines, item instances, or matching entries elsewhere in the OKL schema.

The object resides in the OKL schema and is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2. Its physical definition in 12.2.2 comprises 35 columns. Based on the foreign-key structure mined from the data dictionary, the heuristic Data Vault classification for this object is hub-leaning. Under that modeling suggestion, OKL_TRX_ASSETS would serve as a hub entity keyed on its surrogate identifier, with the surrounding asset-line and item-instance tables acting as satellites or link participants that reference it.

Key Information Stored

The primary key is defined by OKL_TRX_ASSETS_PK on the ID column, and a unique index OKL_TRX_ASSETS_U1 also exists on ID. The surrogate key ID is therefore the stable technical identifier, while TRANS_NUMBER and, where applicable, REQ_ASSET_ID serve as the closest business-key candidates because they carry meaning to end users and external references. The most significant columns include:

• ID — surrogate primary key uniquely identifying each top-level transaction record.
• TRY_ID — foreign key to OKL_TRX_TYPES_B, identifying the transaction type that governs processing rules for the record.
• TAS_TYPE — classifies the asset transaction being grouped.
• TRANS_NUMBER — user-facing transaction number used for identification and reporting.
• TRANSACTION_DATE and DATE_TRANS_OCCURRED — the effective and recorded dates of the transaction, used for period and ageing analysis.
• REQ_ASSET_ID — reference to a requested or source asset, linking the transaction to an equipment or asset request.
• TOTAL_MATCH_AMOUNT — aggregated matched amount associated with the transaction.
• LEGAL_ENTITY_ID — foreign key to FV_LEGAL_ENTITIES, determining the owning legal entity and driving accounting and reporting context.
• ORG_ID — operating unit identifier, supporting multi-org security and reporting.
• ICA_ID — reference to an associated contract or instrument context within the lease lifecycle.
• TSU_CODE — status or state code reflecting the transaction's current lifecycle position.
• COMMENTS — free-text notes entered by users.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the application to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit ("WHO") columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the standard DFF (descriptive flexfield) columns for client-specific extensions.

Common Use Cases and Queries

Typical reporting and reconciliation scenarios include listing all asset-related transactions for a contract, tracking transaction volumes by type, and joining to legal entity and operating unit for financial reporting. A representative query groups transactions by type and legal entity:

• SELECT ta.TRANS_NUMBER, tt.NAME, ta.TRANSACTION_DATE, ta.TOTAL_MATCH_AMOUNT FROM OKL_TRX_ASSETS ta, OKL_TRX_TYPES_B tt WHERE ta.TRY_ID = tt.ID AND ta.LEGAL_ENTITY_ID = :legal_entity;
• Retrieving associated asset lines: SELECT b.* FROM OKL_TXL_ASSETS_B b WHERE b.TAS_ID = :tas_id;
• Auditing by operating unit: filter on ORG_ID combined with TSU_CODE for status-based exception reporting.

These patterns are commonly used in lease portfolio extracts, asset roll-forward reports, and reconciliation of asset creation activity ahead of accounting generation.

Related Objects

The foreign-key relationships documented in the data dictionary establish the principal dependencies:

• OKL_TRX_TYPES_B — referenced by OKL_TRX_ASSETS.TRY_ID; defines the transaction type and its processing behavior.
• OKL_TXL_ASSETS_B — references OKL_TRX_ASSETS.TAS_ID; holds the asset lines generated from the transaction.
• OKL_TXL_ITM_INSTS — also references OKL_TRX_ASSETS.TAS_ID; stores item instance detail for asset lines.
• FV_LEGAL_ENTITIES — referenced by OKL_TRX_ASSETS.LEGAL_ENTITY_ID; supplies legal entity context for accounting and reporting.

Collectively, these relationships position OKL_TRX_ASSETS as the central grouping point through which OKL transaction activity is organized and downstream asset lines are created for lease and loan contracts.