Search Results show_on_update_flag

Overview

CS_TEMPLATE_DETAILS_V is a Service (CS) module view that consolidates every configurable attribute associated with incident and service request templates. In Oracle EBS 12.1.1 and 12.2.2, template behavior is not stored in a single table; rather, attribute-level configuration is distributed across mapping and lookup entities. This view joins those sources to present one denormalized row per template attribute, exposing both the technical flag columns and the user-facing lookup meaning and description.

The view is primarily a reporting and integration object. It allows functional and technical users to audit how each template is configured — which attributes are mandatory, displayed, defaulted, or editable — without navigating multiple setup forms. The presence of the column SR_ATTR_MANDATORY_FLAG (the term originally searched) reflects its common use for identifying attributes that must be captured during service request creation.

Underlying Base Objects

The view is defined over two referenced objects:

• CUG_SR_TYPE_ATTR_MAPS_VL — a VL (translated) view over the service request type attribute map table. It supplies the mapping between service request types and layout attributes, together with the configuration flags and template identifier.
• FND_LOOKUPS — the standard Oracle lookup table, joined on LOOKUP_CODE = SR_ATTRIBUTE_CODE and restricted to LOOKUP_TYPE = 'CS_LAYOUT_ATTRIBUTES'. This provides the MEANING and DESCRIPTION of each attribute.

The join is an inner equijoin, so rows appear only where a valid layout attribute lookup exists for the mapped attribute code. The view therefore acts as an enriched projection of the attribute map, not a physical table.

Key Columns

• SR_TYPE_ATTR_MAP_ID — primary identifier of the attribute-map record; unique per mapping.
• SR_ATTRIBUTE_CODE — the lookup code of the attribute (from FND_LOOKUPS).
• INCIDENT_TYPE_ID / TEMPLATE_ID — the incident type and template to which the attribute belongs.
• SR_ATTR_MANDATORY_FLAG — indicates whether the attribute must be entered.
• SR_ATTR_DISPLAYED_FLAG — controls whether the attribute is shown on the layout.
• SR_ATTR_DUP_CHECK_FLAG — enables duplicate checking for the attribute value.
• SR_ATTR_DEFAULT_VALUE — the default value applied when the attribute is not supplied.
• SR_ATTRIBUTE_LIST_NAME — the value-set or list used for the attribute.
• REQD_FOR_CLOSE_FLAG — requires the attribute before a service request can be closed.
• SHOW_ON_UPDATE_FLAG / UPDATE_ALLOWED_FLAG — govern visibility and editability after creation.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective-dating of the mapping.
• CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN / OBJECT_VERSION_NUMBER — standard audit and concurrency columns.
• DESCRIPTION / MEANING — the lookup description and display meaning of the attribute.

Common Use Cases and Queries

Typical scenarios include listing all mandatory attributes for a template, auditing defaulted attributes, or extracting template configuration for migration and integration.

Retrieve all mandatory attributes for a given template:

SELECT sr_attribute_code, meaning, sr_attr_mandatory_flag
FROM   cs_template_details_v
WHERE  template_id = :p_template_id
AND    sr_attr_mandatory_flag = 'Y';

Report the full configuration of attributes required for close:

SELECT template_id, sr_attribute_code, meaning, reqd_for_close_flag
FROM   cs_template_details_v
WHERE  reqd_for_close_flag = 'Y'
ORDER BY template_id, sr_attribute_code;

Because the view depends on FND_LOOKUPS and the attribute-map VL view, report queries should account for effective-date filtering via START_DATE_ACTIVE and END_DATE_ACTIVE where historical accuracy is required.