Search Results weight_id

Overview

CS_SR_LOAD_BALANCE_WT is a Service (CS) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the weighting factors used by the load-balancing engine to assign and prioritize service requests among available agents. The table lets administrators bias assignment decisions by specifying how heavily individual attributes should influence the balancing calculation. Each row defines the relative weights applied to skill matches, incident-type and severity characteristics, login recency, and time-zone proximity, ensuring that routing rules reflect organizational support policy rather than a raw round-robin distribution.

From a Data Vault modeling perspective, the mined heuristic classifies this object as standalone. Because its foreign keys resolve outward to independent reference tables rather than capturing an association between two hubs, it is best treated as a descriptive configuration satellite keyed by its own surrogate identifier.

Key Information Stored

The primary key is a single-column surrogate, WEIGHT_ID, enforced by CS_SR_LOAD_BALANCE_WT_PK and also exposed through the unique index CS_SR_LOAD_BALANCE_WT_U1. The table has 37 documented columns. The most significant include:

• WEIGHT_ID — surrogate primary key identifying each weighting rule.
• INCIDENT_TYPE_ID — foreign key to CS_INCIDENT_TYPES_B, scoping the rule to an incident type.
• INCIDENT_SEVERITY_ID — foreign key to CS_INCIDENT_SEVERITIES_B, scoping the rule to a severity level.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective dating that governs when the rule is in force.
• PRODUCT_SKILL_WT, PLATFORM_SKILL_WT, PROB_CODE_SKILL_WT, CATEGORY_SKILL_WT — relative weights for skill-based matching.
• SEVERITY1_COUNT_WT through SEVERITY4_COUNT_WT — weights for open-request volume at each severity level.
• LAST_LOGIN_TIME_WT — weight applied to agent login recency.
• TIME_ZONE_DIFF_WT — weight applied to time-zone proximity between agent and request.
• ATTRIBUTE1–ATTRIBUTE15 and CONTEXT — descriptive flexfield segments for extensibility.
• OBJECT_VERSION_NUMBER — optimistic locking column.

Common Use Cases and Queries

Typical scenarios include tuning routing so product-skill matches dominate for technical issues, or making severity counts dominate for triage queues. Reporting queries commonly join weights to the incident reference tables and to the BIS weighted-measure tables that consume WEIGHT_ID.

• Active rule lookup: SELECT weight_id, incident_type_id, incident_severity_id, product_skill_wt, severity1_count_wt FROM cs_sr_load_balance_wt WHERE TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);
• Type/severity join: SELECT t.name, s.name, w.weight_id FROM cs_sr_load_balance_wt w JOIN cs_incident_types_b t ON w.incident_type_id = t.incident_type_id JOIN cs_incident_severities_b s ON w.incident_severity_id = s.incident_severity_id;
• Score consumption: SELECT m.measure_id, m.weight_id FROM bis_weighted_measure_weights m WHERE m.weight_id = :weight_id;

Because business keys such as incident type and severity are carried as foreign keys alongside effective dating, verification queries should also confirm that no overlapping active rows exist for the same type/severity combination.

Related Objects

• CS_INCIDENT_TYPES_B — referenced via INCIDENT_TYPE_ID; supplies incident type descriptions.
• CS_INCIDENT_SEVERITIES_B — referenced via INCIDENT_SEVERITY_ID; supplies severity descriptions.
• BIS_WEIGHTED_MEASURE_WEIGHTS — references WEIGHT_ID; stores measure-to-weight assignments.
• BIS_WEIGHTED_MEASURE_SCORES — references WEIGHT_ID; stores computed scores applying these weights.
• CS_SR_LOAD_BALANCE_WT_PK / CS_SR_LOAD_BALANCE_WT_U1 — primary key constraint and unique index on WEIGHT_ID.