Results for “okx_asst_catgrs_v”

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

Overview

OKX_ASST_CATGRS_V is an APPS-owned, valid database view that exposes Oracle E-Business Suite Fixed Assets category information to the Contracts Integration module (OKX). Within Release 12.1.1 and 12.2.2, its role is to present asset categories in a denormalized form suitable for contract-related reporting, service and lease integration, and inbound/outbound interfaces that must resolve a category identifier to its user-facing concatenated name. The view concatenates the seven descriptive flexfield segments of a Fixed Assets category into a single dotted NAME string and joins the translation table to deliver a language-appropriate DESCRIPTION. Because OKX is the Contracts Integration product, this view is typically consumed when contract lines, asset-related obligations, or leased and owned asset references must be enriched with asset category context.

Underlying Base Objects

The view is defined over two documented base objects, both accessed through synonyms in the APPS schema:

• FA_CATEGORIES_B — the base table holding the category definition, key flexfield segments, flags, and property-related attributes.
• FA_CATEGORIES_TL — the translation table supplying the DESCRIPTION in the session language.

The join predicate links B.CATEGORY_ID to TL.CATEGORY_ID and restricts TL.LANGUAGE to USERENV('LANG'), so the DESCRIPTION returned reflects the language of the connected user. The NAME column is derived at query time by concatenating SEGMENT1 through SEGMENT7 with '.' separators, applying LTRIM/RTRIM to each segment and using nested DECODE to suppress the separator when a segment is null. This means the concatenated name is not stored; it is computed on every access, so any comparison or filter on NAME should account for trailing-space trimming behavior.

Key Columns

• CATEGORY_ID — primary identifier of the asset category; exposed twice in the select list (as CATEGORY_ID and again as a duplicate alias) for integration convenience.
• NAME — concatenated segment string (SEGMENT1[.SEGMENT2...SEGMENT7]); the human-readable category name used in reports.
• DESCRIPTION — translated description from FA_CATEGORIES_TL.
• OWNED_LEASED — indicates whether the category represents owned assets or leased assets; this is the column most commonly searched for by users researching the term "owned_leased".
• CATEGORY_TYPE, CAPITALIZE_FLAG, INVENTORIAL, SUMMARY_FLAG, ENABLED_FLAG — classification and behavioral flags governing capitalization, physical inventory, summary categories, and whether the category is enabled for use.
• SEGMENT1 – SEGMENT7 — the individual key flexfield segments, retained separately so callers can filter on a specific segment rather than the concatenated string.
• START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date range of the category.
• STATUS — computed as 'A' (active) or 'I' (inactive) by comparing SYSDATE to the start and end dates, using NVL to treat a null date as SYSDATE.
• PROPERTY_TYPE_CODE, PROPERTY_1245_1250_CODE, DATE_INEFFECTIVE, PRODUCTION_CAPACITY — property and asset-specific attributes carried through for tax and property reporting.
• PRIMARY_UOM_CODE — exposed as a literal NULL placeholder, reserved for callers that expect the column to exist.

Common Use Cases and Queries

Typical uses include listing active categories for a picklist, resolving a category ID to its concatenated name during contract integration, and isolating owned versus leased categories for asset accounting or lease reporting.

• Filter by the owned/leased attribute: SELECT category_id, name, owned_leased, status FROM okx_asst_catgrs_v WHERE owned_leased = 'O' AND status = 'A';
• Resolve a known category: SELECT name, description, capitalize_flag FROM okx_asst_catgrs_v WHERE category_id = :p_category_id;
• Search by concatenated name and property type: SELECT category_id, name, property_type_code FROM okx_asst_catgrs_v WHERE name LIKE 'COMPUTER%' ORDER BY name;
• Find currently effective categories: SELECT category_id, name, start_date_active, end_date_active FROM okx_asst_catgrs_v WHERE status = 'A' AND enabled_flag = 'Y';

Because STATUS and NAME are computed rather than stored, queries that filter heavily on them are best issued directly against the view rather than expecting an index-backed predicate; performance-sensitive integrations should prefer filtering on CATEGORY_ID, ENABLED_FLAG, or the individual SEGMENT columns, which originate directly from FA_CATEGORIES_B.