Search Results okx_assets_v




Overview
Explore in AI Chat

Overview

The OKX_ASSETS_V view is a source view within the Oracle E-Business Suite (EBS) Contracts Integration module (OKX), owned by the APPS schema. It serves as the data source for Fixed Asset Lines in Oracle Contracts when a lease contract is created or processed. In EBS 12.1.1 and 12.2.2, this view bridges the Oracle Assets (FA) schema and the Contracts integration layer, exposing asset attributes in a denormalized, contracts-oriented format that the OKX integration APIs consume.

The view presents a consolidated picture of a fixed asset as it relates to a corporate depreciation book, including asset identification, financial book values, depreciation parameters, and physical attributes. Its status is VALID in the documented environment, indicating it is compiled and free of errors. Because the view filters to corporate book controls and active book assignments, it returns only the asset records eligible for lease contract association.

Underlying Base Objects

OKX_ASSETS_V is defined over four base objects in the FA schema (accessed via APPS synonyms):

The join is driven by BOOK_TYPE_CODE between FA_BOOK_CONTROLS and FA_BOOKS, and by ASSET_ID between FA_BOOKS, FA_ADDITIONS_B, and FA_ADDITIONS_TL. The view restricts results to CORPORATE book class records still in effect and excludes assets with a pending outbound transaction (TRANSACTION_HEADER_ID_OUT IS NULL).

Key Columns

The view exposes numerous columns; the most significant include:

Common Use Cases and Queries

This view is typically queried when investigating how asset lines flow into lease contracts, when validating asset quantities, or when reconciling contract lines back to Oracle Assets.

To retrieve assets with their current units and book values:

  • SELECT asset_number, tag_number, current_units, adjusted_cost, book_type_code FROM okx_assets_v ORDER BY asset_number;
  • SELECT asset_id, asset_number, current_units FROM okx_assets_v WHERE current_units > 1;
  • SELECT a.asset_number, a.description, b.set_of_books_id, b.org_id FROM okx_assets_v b, okx_assets_v a WHERE a.asset_id = b.asset_id AND b.org_id = :p_org_id;

Because the view already filters to active corporate books and excludes outbound transactions, queries against it require no additional book-scope predicates, making it convenient for Contracts integration diagnostics and operational reporting.