Search Results oe_pc_rsets_vl




Overview
Explore in AI Chat

Overview

OE_PC_RSETS_VL is a seed data view in the Oracle E-Business Suite Order Management (ONT) module, owned by the APPS schema. It presents a language-translated ("_VL") representation of product catalog record sets, which are configuration containers used by Oracle Order Management and its product configurator infrastructure to group related records. The view is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2 and carries the object type VIEW within the ETRM repository.

The view joins a base entity table to a translation table so that consumers receive the correct display name and description in the session language, resolved through the USERENV('LANG') call. This translation-aware design makes the view appropriate for user-facing reporting, list-of-values queries, and integration extracts that must show record sets in the end user's own locale rather than the base language. Because the "_VL" object is a view rather than a table, it is read-only and cannot be used as a direct DML target; modifications must target the underlying base objects.

Underlying Base Objects

The view is defined over two APPS synonyms: OE_PC_RSETS and OE_PC_RSETS_TL. The base table OE_PC_RSETS stores language-independent record set attributes, while OE_PC_RSETS_TL stores the translated columns DISPLAY_NAME and DESCRIPTION keyed by RECORD_SET_ID and LANGUAGE. The view definition joins the two on RECORD_SET_ID and filters translation rows with TL.LANGUAGE = USERENV('LANG'), so only the current session language's translation is returned.

Although the view metadata reports the referenced objects as synonyms, in a standard EBS installation these resolve to the underlying ONT base tables. The join is a straightforward equijoin without an outer-join clause, which means a record set lacking a translation row for the session language will not appear in query results from this view. Report developers should account for this behavior when comparing counts against the base table.

Key Columns

Common Use Cases and Queries

The view is typically queried to retrieve translated record set names for inclusion in catalog configuration reports, integration extracts, or LOV-style lookups. A basic query returns the translated name and description for all record sets in the session language:

  • SELECT record_set_id, record_set_short_name, record_set_display_name, record_set_description FROM oe_pc_rsets_vl ORDER BY record_set_display_name;
  • Filtering on SYSTEM_FLAG is useful when distinguishing seeded record sets from customer-defined ones, for example: WHERE system_flag = 'Y'.
  • Joining to other product catalog or configurator tables on RECORD_SET_ID allows reports to resolve the human-readable name in place of the numeric identifier.
  • Because language filtering is applied internally, no additional language predicate is required in consuming SQL; the USERENV('LANG') call resolves automatically for the active session.

All access to this view requires appropriate APPS-level privileges, and because it is a view, it should be used strictly for read/query operations. Developers requiring the untranslated short name or needing to update record set data should reference the base OE_PC_RSETS table directly.