Results for “update_allowed_flag”

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

Overview

The CUG.CUG_SR_TYPE_ATTR_MAPS_B table is a base (non-translated) entity table within the CUG – Citizen Interaction Center product of Oracle E-Business Suite. It stores the mapping between Service Request Types and Service Request Attributes, effectively defining which attributes are associated with a given Service Request (incident) type and how those attributes behave at runtime. In practice, it governs the attribute layout presented to agents when they create, update, or close a service request of a particular type.

The table follows the standard EBS "_B" base-table convention, pairing with a "_TL" translation table to hold language-specific descriptive information. Based on its foreign key topology — a single principal parent reference to incident types, a leaf referencing translation table, and an enumerated set of descriptive and behavioral columns — the metadata's heuristic Data Vault classification is satellite-leaning. This suggests the table is best modeled as a satellite attached to a parent hub (the Service Request Type), where each row captures descriptive and behavioral attributes about that parent rather than representing an independent business entity or a many-to-many association link. It carries full WHO/audit and descriptive-flex column sets typical of a satellite.

Key Information Stored

The primary key is a surrogate, SR_TYPE_ATTR_MAP_ID, enforced by constraint CUG_SR_TYPE_ATTR_MAPS_B_PK and indexed uniquely by CUG_SR_TYPE_ATTR_MAPS_B_U1. Two business-key candidates are documented: the surrogate itself, and the composite unique index CUG_SR_TYPE_ATTR_MAPS_B_U2 over SR_ATTRIBUTE_CODE, INCIDENT_TYPE_ID, and TEMPLATE_ID. This composite uniquely identifies an attribute mapping for a given type and template combination.

The most significant columns include:

• SR_TYPE_ATTR_MAP_ID — surrogate primary key and the join key to the translation table.
• INCIDENT_TYPE_ID — foreign key to CS_INCIDENT_TYPES_B, identifying the Service Request Type.
• SR_ATTRIBUTE_CODE — the attribute being mapped to the type.
• TEMPLATE_ID — the template scope for the mapping.
• SR_ATTR_MANDATORY_FLAG — whether the attribute is required.
• SR_ATTR_DISPLAYED_FLAG — whether the attribute surfaces on the UI.
• SR_ATTR_DUP_CHECK_FLAG — duplicate-value validation behavior.
• SR_ATTRIBUTE_LIST_NAME — lookup/list of values source for the attribute.
• START_DATE_ACTIVE / END_DATE_ACTIVE — date-effective activation window.
• REQD_FOR_CLOSE_FLAG, SHOW_ON_UPDATE_FLAG, UPDATE_ALLOWED_FLAG — lifecycle behavior controls.
• SR_TYPE_ATTR_SEQ_NUM — display ordering of the attribute.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS supporting multi-org/security partitioning.
• OBJECT_VERSION_NUMBER and the standard WHO columns — concurrency and audit tracking.

Common Use Cases and Queries

Typical uses include reporting which attributes are mandatory for a type, troubleshooting missing or incorrectly displayed attributes, and validating template-driven configurations. A representative query retrieves active, mandatory attributes for a type:

• SELECT map.SR_TYPE_ATTR_MAP_ID, map.SR_ATTRIBUTE_CODE, map.SR_TYPE_ATTR_SEQ_NUM FROM CUG.CUG_SR_TYPE_ATTR_MAPS_B map WHERE map.INCIDENT_TYPE_ID = :p_type_id AND map.SR_ATTR_MANDATORY_FLAG = 'Y' AND TRUNC(SYSDATE) BETWEEN map.START_DATE_ACTIVE AND NVL(map.END_DATE_ACTIVE, TRUNC(SYSDATE)+1) ORDER BY map.SR_TYPE_ATTR_SEQ_NUM;
• Joining to the translation table for ATTRIBUTE: SELECT b.SR_ATTRIBUTE_CODE, t.ATTRIBUTE FROM CUG.CUG_SR_TYPE_ATTR_MAPS_B b, CUG.CUG_SR_TYPE_ATTR_MAPS_TL t WHERE b.SR_TYPE_ATTR_MAP_ID = t.SR_TYPE_ATTR_MAP_ID;
• Joining to CS_INCIDENT_TYPES_B to resolve type names for reporting.

Related Objects

• CUG.CUG_SR_TYPE_ATTR_MAPS_TL — translation table joined on SR_TYPE_ATTR_MAP_ID; holds language-specific text.
• CS.CS_INCIDENT_TYPES_B — parent Service Request Type; joined on INCIDENT_TYPE_ID.
• FND.FND_SECURITY_GROUPS — security partitioning; joined on SECURITY_GROUP_ID.
• Service Request / incident type configuration and template components that consume these mappings to drive attribute presentation and validation.

Because the table is date-effective and security-partitioned, consumers should always filter on active dates and security group to obtain a correct point-in-time view of attribute mappings.