Results for “okl_assets_v”

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

Overview

OKL_ASSETS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, defined within the OKL (Lease and Finance Management) product family. It is a VALID database view that presents a consolidated, translation-aware projection of lease asset master data. In the ETRM 12.1.1 and 12.2.2 data models, lease assets are physically stored in two distinct tables: OKL_ASSETS_B, which holds the operational and business columns, and OKL_ASSETS_TL, which holds the language-dependent descriptive columns. OKL_ASSETS_V joins these two sources so that consumers receive a single horizontally integrated row per asset without needing to understand the underlying _B/_TL (_BASE / _TRANSLATION) split.

The view is principally consumed by concurrent programs, Oracle Reports, Oracle Forms, OAF-based pages, and custom integrations that need asset attributes together with their descriptions. Because the join restricts the translation table to the session language using USERENV('LANG'), each query returns descriptions appropriate to the connected user's language environment, which is the standard Oracle EBS multilingual design pattern.

Underlying Base Objects

The documented base objects for this view are OKL_ASSETS_B and OKL_ASSETS_TL, both referenced through public synonyms resolved to the APPS schema. The defining query joins them on the ID column (ASS.ID = ASST.ID) and filters the translation side by ASST.LANGUAGE = USERENV('LANG').

• OKL_ASSETS_B — the base table supplying all operational columns, including identifiers, descriptive flexfield attribute columns, audit columns, asset number, install site, pricing, and financial defaults.
• OKL_ASSETS_TL — the translation table supplying SHORT_DESCRIPTION, DESCRIPTION, and COMMENTS for the active language.

The view exposes ROW_ID from the base table ROWID, which permits positional identification of the underlying row for certain update or diagnostics scenarios involving the base table. Because the view is defined over the translated and base pair, the cardinality is normally one row per asset per language; a missing translation row for the session language would exclude the asset from the result set, which is important to remember when troubleshooting apparently absent records.

Key Columns

The view returns ID (the primary asset identifier), ASSET_NUMBER, and OBJECT_VERSION_NUMBER, which is used for optimistic locking in OAF/ADF pages. The PARENT_OBJECT_CODE and PARENT_OBJECT_ID columns identify the owning business object the asset belongs to, enabling polymorphic association across OKL entities. FINANCIAL and PRICING related columns include STRUCTURED_PRICING, RATE_TEMPLATE_ID, RATE_CARD_ID, LEASE_RATE_FACTOR, TARGET_ARREARS, OEC, OEC_PERCENTAGE, TARGET_AMOUNT, TARGET_FREQUENCY, END_OF_TERM_VALUE, and END_OF_TERM_VALUE_DEFAULT. ORIG_ASSET_ID supports asset derivation/rollover lineage.

INSTALL_SITE_ID is the column most directly relevant to the searched term: it holds the operating location (site) where the leased asset is installed. In ETRM, this value typically relates to an operating unit or location used for tax, accounting, and billing purposes, and it is often combined with asset number to reconcile physical assets against lease contracts. The ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 columns are the descriptive flexfield segments, and the standard audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN are carried through unchanged. Descriptive columns SHORT_DESCRIPTION, DESCRIPTION, and COMMENTS are sourced from the translation table.

Common Use Cases and Queries

Typical use cases include reporting assets by installation site, validating flexfield attributes, and joining asset data to contract or pricing structures for integration extracts. A representative query selecting assets for a given install site is shown below; replace the bind value with the actual operating location identifier.

• Assets by install site: SELECT id, asset_number, install_site_id, asset_number FROM okl_assets_v WHERE install_site_id = :p_install_site_id AND language IS NOT NULL — note that language is implicitly filtered by the view.
• Pricing and rate lookup: SELECT id, asset_number, rate_template_id, rate_card_id, lease_rate_factor FROM okl_assets_v WHERE rate_card_id IS NOT NULL.
• Asset lineage: SELECT id, orig_asset_id, asset_number, parent_object_code FROM okl_assets_v WHERE orig_asset_id IS NOT NULL.
• Descriptive extraction: SELECT id, short_description, description FROM okl_assets_v WHERE short_description LIKE :pattern.

When tuning queries against OKL_ASSETS_V, be aware of the underlying join and language predicate; filtering on ASSET_NUMBER, ID, or INSTALL_SITE_ID generally performs well, whereas heavy string matching on DESCRIPTION is more expensive because it originates from the translation table. Bulk integrations should prefer the base tables directly where translation is not required.