Search Results cug_sr_type_attributes




Overview
Explore in AI Chat

Overview

APPS.CUG_INCIDNT_ATTR_VALS_V is a reporting and integration view in the Oracle E-Business Suite (12.1.1 and 12.2.2) that exposes service request (SR) type attribute configurations together with the lookup definitions that govern them. It is part of the Oracle TeleService / Customer Support foundation, specifically the Common Understanding Group (CUG) incident attribute framework. The view resolves the relationship between SR type attribute map definitions and the FND_LOOKUPS values of lookup type CUG_SR_TYPE_ATTRIBUTES, providing a denormalized projection that is convenient for querying without needing knowledge of the underlying mapping and value tables.

The view is defined as a DISTINCT join across three source objects, filtered so that only currently active and displayed attributes are returned. It is commonly referenced when the user searches for cug_sr_type_attributes, since that is the lookup type driving the visibility of the attribute codes returned by the view.

Underlying Base Objects

The view is defined over the following documented base objects:

  • CUG_SR_TYPE_ATTR_MAPS_VL (VIEW) — the SR type attribute mapping definition, supplying the attribute code, incident type, mandatory/displayed/duplicate-check flags, default value, active dates, and sequence number.
  • CUG_INCIDNT_ATTR_VALS_VL (VIEW) — the incident attribute value records, supplying the incident-linked attribute values and the descriptive flexfield (DFF) columns ATTRIBUTE1 through ATTRIBUTE15 plus ATTRIBUTE_CATEGORY.
  • FND_LOOKUPS (VIEW) — the lookup definitions restricted to LKUP.LOOKUP_TYPE = 'CUG_SR_TYPE_ATTRIBUTES', supplying the description and lookup effective dates.
  • FND_GLOBAL (PACKAGE) — referenced for session context (user, login, responsibility) used by the underlying VL views.

The join condition between the mapping and value views is an outer join on SR_ATTRIBUTE_CODE and INCIDENT_ID = 0, producing a per-SR-type attribute blueprint that is not yet tied to a specific incident. The lookup join is on LOOKUP_CODE = SR_ATTRIBUTE_CODE.

Key Columns

Common Use Cases and Queries

The view is most often used to enumerate the active, displayed attributes available for a given incident type, and to resolve attribute descriptions from the lookup. Typical reporting includes attribute configuration audits and integration extracts feeding service request interfaces.

Sample query returning the active attribute blueprint for an incident type:

  • SELECT sr_attribute_code, description, sr_attr_mandatory_flag, sr_attr_default_value, sr_attribute_list_name FROM apps.cug_incidnt_attr_vals_v WHERE incident_type_id = :p_type_id ORDER BY sr_type_attr_seq_num;

Query joining to incidents for captured values:

  • SELECT v.incident_id, v.sr_attribute_code, v.sr_attribute_value, v.attribute_category FROM apps.cug_incidnt_attr_vals_v v WHERE v.incident_id = :p_incident_id;

Because the view pre-filters on TRUNC(SYSDATE) against START_DATE_ACTIVE and END_DATE_ACTIVE of the mapping, and requires SR_ATTR_DISPLAYED_FLAG = 'Y', no additional date or flag filtering is necessary for active-attribute reporting. Reports seeking historical or disabled attributes must query the base CUG_SR_TYPE_ATTR_MAPS_VL view directly instead.