Search Results sr_attr_lkup_start_date

Overview

CUG_INCIDNT_ATTR_VALS_V is an APPS-owned database view within the CUG (Citizen Interaction Center) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It is consumed by the CIC runtime form to capture and display service request details that are specific to the Citizen Interaction Center application, including the incident address, the address validation override flag, and the configured SR attributes for a given incident type.

Functionally, the view joins the attribute definition metadata for a service request type with the per-incident attribute values, and enriches each attribute with its lookup description and lookup validity dates. It therefore acts as the runtime presentation layer for CIC service request attribute capture, and is equally useful as a reporting and integration source for querying how SR attributes are defined and populated. The view is documented as VALID and resolved against the APPS schema.

Underlying Base Objects

The view is defined over the following documented objects:

• CUG_SR_TYPE_ATTR_MAPS_VL — the SR type attribute mapping definition (aliased B), supplying attribute code, incident type, mandatory/displayed/duplicate-check flags, list name, default value, sequence number, and the active date range.
• CUG_INCIDNT_ATTR_VALS_VL — the incident attribute values (aliased C), supplying the incident-level value, override address validation flag, and the descriptive flexfield ATTRIBUTE1 through ATTRIBUTE15 columns.
• FND_LOOKUPS — the lookup view (aliased LKUP), restricted to LOOKUP_TYPE = 'CUG_SR_TYPE_ATTRIBUTES', supplying the lookup DESCRIPTION and the lookup's own active date range.
• FND_GLOBAL — referenced for session context (for example, the current application and user context) used by the runtime form.

The join is an outer join between the attribute mapping and the incident attribute values (C.SR_ATTRIBUTE_CODE(+) = B.SR_ATTRIBUTE_CODE) and between the attribute values and a fixed incident placeholder (C.INCIDENT_ID(+) = 0), so attribute definitions are returned even when no value has yet been captured. A mandatory predicate restricts the result to attributes with SR_ATTR_DISPLAYED_FLAG = 'Y' and to mappings whose active window currently includes TRUNC(SYSDATE).

Key Columns

• SR_TYPE_ATTR_MAP_ID, SR_ATTRIBUTE_CODE, INCIDENT_TYPE_ID — identify the mapped attribute and the service request type to which it belongs.
• SR_ATTR_MANDATORY_FLAG, SR_ATTR_DISPLAYED_FLAG, SR_ATTR_DUP_CHECK_FLAG — control runtime behavior: whether the attribute is required, rendered, and duplicate-checked.
• SR_ATTRIBUTE_LIST_NAME, SR_ATTR_DEFAULT_VALUE, SR_TYPE_ATTR_SEQ_NUM — the LOV list, default, and display ordering for the attribute.
• INCIDNT_ATTR_VAL_ID, INCIDENT_ID, SR_ATTRIBUTE_VALUE, OVERRIDE_ADDR_VALID_FLAG — the captured value, the owning incident, and the address validation override indicator.
• START_DATE_ACTIVE, END_DATE_ACTIVE — the mapping's active date range.
• SR_ATTR_LKUP_START_DATE, SR_ATTR_LKUP_END_DATE — aliases of the FND_LOOKUPS START_DATE_ACTIVE and END_DATE_ACTIVE columns; these are the columns most relevant to the search term "sr_attr_lkup_start_date".
• DESCRIPTION — the lookup description for the attribute code.
• ROW_ID, OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — standard WHO and concurrency columns.
• ATTRIBUTE1–ATTRIBUTE15, ATTRIBUTE_CATEGORY — the descriptive flexfield segments carried from the incident attribute values.

Common Use Cases and Queries

The view supports runtime rendering of CIC service request attributes, validation of configured attributes against the current date, and audit or reporting queries on captured SR attribute values. A representative query returning displayed attributes and their lookup validity dates is:

• SELECT sr_attribute_code, sr_attr_mandatory_flag, sr_attribute_value, sr_attr_lkup_start_date, sr_attr_lkup_end_date FROM apps.cug_incidnt_attr_vals_v WHERE incident_type_id = :p_incident_type_id ORDER BY sr_type_attr_seq_num;
• SELECT incident_id, sr_attribute_code, sr_attribute_value, override_addr_valid_flag FROM apps.cug_incidnt_attr_vals_v WHERE incident_id = :p_incident_id;
• SELECT sr_attribute_code, description, sr_attr_lkup_start_date FROM apps.cug_incidnt_attr_vals_v WHERE TRUNC(SYSDATE) BETWEEN TRUNC(sr_attr_lkup_start_date) AND TRUNC(sr_attr_lkup_end_date);

Because the view applies SYSDATE-based filtering to the attribute mapping, it presents only currently effective, displayed attributes, making it suitable for form runtime use and for operational reporting on active CIC service request attribute configuration.