Results for “sr_attribute_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CUG_INCIDNT_ATTR_VALS_B is the base (non-translatable) table in the Citizen Interaction Center (CUG) module of Oracle E-Business Suite that stores the runtime values of Service Request attributes configured for a given Service Request Type. Where the configuration of Service Request attributes is defined at the setup level, this table captures the actual values that a user entered or that the system populated for a specific Service Request (incident) instance. It is therefore an operational data table rather than a setup table, and it sits at the intersection of the Service Request framework in the Oracle Service (CS) module and the Citizen Interaction Center extensions.

From a Data Vault modeling perspective, the metadata indicates a satellite-leaning classification. The table carries a single-column surrogate primary key (INCIDNT_ATTR_VAL_ID) but also a composite unique business key on (INCIDENT_ID, SR_ATTRIBUTE_CODE), plus a foreign key to the Service Request header. This pattern — one row per attribute per parent entity, with descriptive and audit columns attached — is characteristic of a satellite hanging off the incident hub rather than a true independent hub or a many-to-many link. This classification is a heuristic suggestion derived from the FK structure, not a prescribed physical design.

Key Information Stored

The 27-column physical schema is dominated by EBS standard audit columns and a flexible descriptive flexfield (DFF) block, with a small number of functional columns carrying the business meaning:

• INCIDNT_ATTR_VAL_ID — Surrogate primary key (CUG_INCIDNT_ATTR_VALS_B_PK, also unique index _U1). System-generated identifier for each attribute-value row.
• INCIDENT_ID — Foreign key to CS_INCIDENTS_ALL_B; identifies the Service Request to which this attribute value belongs.
• SR_ATTRIBUTE_CODE — The attribute identifier. Together with INCIDENT_ID it forms the unique business key (CUG_INCIDNT_ATTR_VALS_B_U2). This is the column referenced by the ETRM user search term "sr_attribute_code" and is the primary lookup predicate for retrieving a specific attribute value.
• OVERRIDE_ADDR_VALID_FLAG — Functional flag controlling whether standard address validation is overridden for the attribute value held on the row.
• ATTRIBUTE_CATEGORY — DFF context (structure/context) that determines which of the ATTRIBUTEn segments are meaningful for the row.
• ATTRIBUTE1 … ATTRIBUTE15 — Descriptive flexfield segments holding additional attribute payload not accommodated by dedicated columns.
• OBJECT_VERSION_NUMBER — Optimistic locking / concurrency control column used by the ORM framework.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — Standard who-column audit trail.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS supporting multi-org/security partitioning of the row.

The translatable/description counterpart resides in CUG_INCIDNT_ATTR_VALS_TL, keyed by the same INCIDNT_ATTR_VAL_ID.

Common Use Cases and Queries

The most frequent access pattern is retrieving all attribute values for a specific Service Request, or retrieving a single attribute value by incident and code. Typical reporting includes Service Request detail reports, attribute-driven analytics, and data migration or reconciliation between configuration and runtime values.

• All attributes for an incident: SELECT sr_attribute_code, attribute_category, attribute1, attribute15 FROM cug_incidnt_attr_vals_b WHERE incident_id = :p_incident_id;
• Single attribute lookup by business key: SELECT * FROM cug_incidnt_attr_vals_b WHERE incident_id = :p_incident_id AND sr_attribute_code = :p_code;
• Join to header and translated description: SELECT i.incident_number, b.sr_attribute_code, t.description FROM cug_incidnt_attr_vals_b b JOIN cs_incidents_all_b i ON b.incident_id = i.incident_id JOIN cug_incidnt_attr_vals_tl t ON b.incidnt_attr_val_id = t.incidnt_attr_val_id WHERE t.language = USERENV('LANG');
• Audit / change tracking: filter on LAST_UPDATE_DATE and LAST_UPDATED_BY to detect recent attribute modifications.

Because SECURITY_GROUP_ID is present, queries executed within a multi-org secured context should respect the standard security profile predicate where applicable.

Related Objects

• CS_INCIDENTS_ALL_B — Parent Service Request header. Join on CUG_INCIDNT_ATTR_VALS_B.INCIDENT_ID = CS_INCIDENTS_ALL_B.INCIDENT_ID. This is the most significant dependency.
• CUG_INCIDNT_ATTR_VALS_TL — Translation table referencing this table via INCIDNT_ATTR_VAL_ID. Join on CUG_INCIDNT_ATTR_VALS_B.INCIDNT_ATTR_VAL_ID = CUG_INCIDNT_ATTR_VALS_TL.INCIDNT_ATTR_VAL_ID.
• FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID for security/multi-org partitioning.
• CUG Service Request attribute configuration objects — The setup definitions that determine which SR_ATTRIBUTE_CODE values are valid for a given Service Request Type; these govern the rows that can exist here.
• CS_INCIDENTS_ALL_TL — Translated header information commonly joined alongside the header base table for reporting.
• CUG_INCIDNT_ATTR_VALS_B_PK / _U1 / _U2 — The primary and unique indexes that enforce one row per incident and attribute code and support the principal query paths.