Results for “concat_segments”

50+ results




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

Overview

OKL_RA_TERRITORIES_UV is an APPS-owned database view in Oracle E-Business Suite Release 12.1.1 and 12.2.2, delivered as part of the OKL — Lease and Finance Management product family. Its documented purpose is to serve as the user interface view for the sales territories list of values (LOV). In practice, the view presents a flattened, concatenated representation of the multi-segment territory definition stored in the RA_TERRITORIES table, exposing a single derived column, CONCAT_SEGMENTS, that joins the territory's individual segments with a period delimiter for display and selection in Oracle Forms-based LOV windows.

The user search term "concat_segments" corresponds exactly to this view's derived column, which is the primary reason applications and users query OKL_RA_TERRITORIES_UV rather than the underlying base table directly. The view abstracts away the segment-by-segment storage model and provides a presentation-ready territory string suitable for lookup, validation, and reporting against lease and finance management transactions.

Underlying Base Objects

The view is defined exclusively over the RA_TERRITORIES table, which is available in the APPS schema via a synonym (RA_TERRITORIES SYNONYM). No other base tables are referenced in the documented view text. RA_TERRITORIES stores sales territory definitions using a flexible multi-segment structure spanning SEGMENT1 through SEGMENT20, alongside identifying and status attributes such as TERRITORY_ID, NAME, DESCRIPTION, ENABLED_FLAG, STATUS, and effective dating columns (START_DATE, END_DATE).

The view filters rows so that only active, enabled territories are returned: ENABLED_FLAG = 'Y', STATUS = 'A', and a TRUNC(SYSDATE) BETWEEN NVL(TRUNC(RAT.START_DATE... condition on the effective date range. This filtering ensures the LOV surfaces only territories that are currently valid for selection at the time of query.

Key Columns

  • TERRITORY_ID — The unique numeric identifier of the territory (RAT.TERRITORY_ID), used as the returned value in LOV selections and as the join key to downstream lease and finance transactions.
  • CONCAT_SEGMENTS — The derived concatenated territory string. Each non-null SEGMENT1 through SEGMENT20 is trimmed with LTRIM/RTRIM and appended in sequence, separated by a period ('.'). The DECODE construct returns NULL for null segments, so only populated segments appear. This column is the display value in the territory LOV and the focal point of user searches involving "concat_segments".
  • NAME — The short descriptive name of the territory (RAT.NAME), typically the human-readable label shown alongside the concatenated segments.
  • DESCRIPTION — The full textual description of the territory (RAT.DESCRIPTION), providing additional context.

Common Use Cases and Queries

Typical usage centers on populating territory LOVs and mapping displayed territory names back to TERRITORY_ID for transaction processing. A sample query mirroring the LOV behavior is:

  • SELECT territory_id, concat_segments, name, description FROM okl_ra_territories_uv WHERE UPPER(name) LIKE UPPER(:p_search||'%') ORDER BY concat_segments;
  • SELECT concat_segments FROM okl_ra_territories_uv WHERE territory_id = :p_territory_id; — to resolve a stored ID into its display string.
  • Joining the view to lease transaction tables on territory_id to render territory labels in custom reports, while relying on the view's built-in ENABLED_FLAG, STATUS, and effective-date filters to exclude inactive definitions.

Because the view applies its own filtering and derives CONCAT_SEGMENTS dynamically, developers should prefer querying OKL_RA_TERRITORIES_UV for LOV and reporting purposes rather than recreating the concatenation logic against RA_TERRITORIES.