Search Results attribute_context




Overview

CS_SR_LINK_TYPES_VL is a seeded, valid database view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the Service (CS) product family and exposes the set of relationship types that may be established between service requests, together with their translated display names and descriptions. The view is a translation ("_VL") view, meaning it presents both the language-independent definition rows and the language-specific descriptive text side by side, filtered to the session's current language.

The object is documented as new for release 11.5.9 (referenced as "1159"), which places it among the earlier Service Request relationship constructs that were subsequently carried forward unchanged into the 12.x code line. Because it resolves the session language automatically through USERENV('LANG'), it is a natural source for reports, concurrent programs, forms, and integration interfaces that must present relationship-type labels in the user's own language without performing their own translation joins.

Underlying Base Objects

The view is defined over two documented base objects, both exposed to APPS as synonyms:

  • CS_SR_LINK_TYPES_B — the base (_B) table holding the language-independent relationship-type definition, including identifiers, activation dates, audit columns, the descriptive flexfield attribute columns, SEEDED_FLAG, and OBJECT_VERSION_NUMBER.
  • CS_SR_LINK_TYPES_TL — the translation (_TL) table holding NAME, DESCRIPTION, LANGUAGE, and SOURCE_LANG for each link type in each installed language.

The join is an equi-join on LINK_TYPE_ID between the two tables, with the additional restriction B.LANGUAGE = USERENV('LANG'). The view therefore returns one row per relationship type per session language, with no duplicate language rows. All columns from the base table are projected verbatim, while only the four descriptive columns are drawn from the translation table.

Key Columns

  • LINK_TYPE_ID — primary key of the relationship type; the value stored on service request relationship records.
  • RECIPROCAL_LINK_TYPE_ID — the inverse relationship type, allowing the system to infer the reverse link (for example, a "parent/child" pairing).
  • START_DATE_ACTIVE, END_DATE_ACTIVE — the effective date range during which the relationship type may be used; END_DATE_ACTIVE null indicates an open-ended type.
  • SEEDED_FLAG — indicates whether the row was delivered by Oracle (Y) or defined by the customer (N).
  • NAME, DESCRIPTION — the translated label and long description presented to the user.
  • LANGUAGE, SOURCE_LANG — the language of the returned translation row and the language from which it was derived.
  • ATTRIBUTE1 through ATTRIBUTE15, ATTRIBUTE_CONTEXT — descriptive flexfield columns for customer-defined attributes.
  • OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle Application Framework (OAF) and forms.
  • SECURITY_GROUP_ID, APPLICATION_ID, and the standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN).

Common Use Cases and Queries

Typical consumers include service request relationship LOVs, Service Request report layouts, and inbound integration that must map an external relationship code to an internal LINK_TYPE_ID. Listing the currently active relationship types in the session language is the most frequent query:

  • SELECT link_type_id, reciprocal_link_type_id, name, description
      FROM cs_sr_link_types_vl
     WHERE TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE)
        AND NVL(end_date_active, SYSDATE)
     ORDER BY name;
  • SELECT name FROM cs_sr_link_types_vl WHERE link_type_id = :p_link_type_id; — resolve a label during reporting.
  • SELECT link_type_id FROM cs_sr_link_types_vl WHERE seeded_flag = 'Y'; — isolate Oracle-delivered types.

Because the view is a translation view, ad hoc queries against the base tables should be avoided when display text is required; querying CS_SR_LINK_TYPES_VL guarantees language correctness and keeps custom SQL consistent with Oracle's own retrieval semantics.

  • View: CS_SR_LINK_TYPES_VL 12.1.1

    owner:APPS,  object_type:VIEW,  fnd_design_data:CS.CS_SR_LINK_TYPES_VL,  object_name:CS_SR_LINK_TYPES_VL,  status:VALID,  product: CS - Servicedescription: View has information of service request relationship types. This view is based on CS_SR_LINK_TYPES_B and _TL and is used to select the translated name and description. New for 1159. ,  implementation_dba_data: APPS.CS_SR_LINK_TYPES_VL

  • View: CS_SR_LINK_TYPES_VL 12.2.2

    owner:APPS,  object_type:VIEW,  fnd_design_data:CS.CS_SR_LINK_TYPES_VL,  object_name:CS_SR_LINK_TYPES_VL,  status:VALID,  product: CS - Servicedescription: View has information of service request relationship types. This view is based on CS_SR_LINK_TYPES_B and _TL and is used to select the translated name and description. New for 1159. ,  implementation_dba_data: APPS.CS_SR_LINK_TYPES_VL