Results for “template_attribute_id”

2 results




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

Overview

CS_TP_TEMPLATE_ATTRIBUTE is a Service (CS) module table in the Oracle E-Business Suite schema CS. It stores the urgency, severity, and related threshold attributes that are attached to a service template. In practice, this table acts as the attribute-level detail layer behind a template header, allowing administrators to define how individual objects, categories, or identifiers behave within a template — for example, which urgency or severity bands apply, and the thresholds that govern the assignment.

The table is populated and maintained by the Service/TeleService template configuration components and is queried at runtime when the application evaluates template behavior, such as in Service Request or interaction workflows. Its presence in the CS schema and its foreign keys to template, object, and security group tables confirm its role as a configuration detail store rather than a transactional table.

Under a heuristic Data Vault classification mined from the foreign key structure, this object is best modeled as a link entity. It resolves relationships between a template (CS_TP_TEMPLATES_B) and an object (JTF_OBJECTS_B), carrying descriptive columns such as thresholds and attribute segments. This classification is a suggestion, not a documented fact.

Key Information Stored

The documented schema contains 28 columns. The most significant are:

The distinction is important: TEMPLATE_ATTRIBUTE_ID is a purely technical primary key, while the combination of TEMPLATE_ID, OTHER_ID, and OBJECT_CODE forms the meaningful business key that prevents duplicate attribute rows for the same template/object pair.

Common Use Cases and Queries

Typical scenarios include retrieving all attributes for a given template, joining to the template header to obtain the template name, and resolving object codes to their descriptions. A representative query joining the header follows:

  • SELECT ta.template_attribute_id, ta.template_id, ta.object_code, ta.start_threshold, ta.end_threshold
  • FROM cs.cs_tp_template_attribute ta
  • WHERE ta.template_id = :template_id;

To resolve the object referenced by each attribute:

  • SELECT ta.template_attribute_id, ob.title
  • FROM cs.cs_tp_template_attribute ta, jtf.jtf_objects_b ob
  • WHERE ta.object_code = ob.object_code
  • AND ta.security_group_id = :security_group_id;

Reporting use cases center on auditing which templates define urgency and severity thresholds, verifying that no overlapping threshold ranges exist within a template, and exporting template configuration for environment migration. Queries should always filter on SECURITY_GROUP_ID where the implementation is partitioned, to avoid cross-group data leakage.

Related Objects

  • CS_TP_TEMPLATES_B — the template header. Joined via CS_TP_TEMPLATE_ATTRIBUTE.TEMPLATE_ID = CS_TP_TEMPLATES_B.TEMPLATE_ID.
  • JTF_OBJECTS_B — the object definition table. Joined via CS_TP_TEMPLATE_ATTRIBUTE.OBJECT_CODE = JTF_OBJECTS_B.OBJECT_CODE.
  • FND_SECURITY_GROUPS — the security group definition. Joined via CS_TP_TEMPLATE_ATTRIBUTE.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID.
  • CS_TP_TEMPLATES_TL — the translatable template name table, joined through the template header to obtain language-specific names.
  • FND_FLEX_VALUES / FND_FLEX_VALUE_SETS — standard lookup sources for values held in the ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 DFF columns.

The unique indexes CS_TP_TEMPLATE_ATTR_U1 and CS_TP_TEMPLATE_ATTR_U2 are the principal constraints to account for when writing inserts, migrations, or de-duplication scripts against this table.