Search Results cs_sr_load_balance_wt_v




Overview
Explore in AI Chat

Overview

CS_SR_LOAD_BALANCE_WT_V is an APPS-owned database view in the Oracle E-Business Suite Service (CS) module. Its documented status is VALID and it is available in both EBS 12.1.1 and 12.2.2. As stated in the ETRM metadata, the view "contains data of all the load balance weights." In the Oracle Service request (SR) routing and assignment model, load balance weights are the configurable coefficients used by the assignment engine to score and rank service request candidates — for example, field service technicians or support agents — before an incident is dispatched. The view exposes these weighting factors in a denormalized, human-readable form by resolving the raw numeric foreign keys into the descriptive names held by the incident type and incident severity lookup views.

Because it joins the transactional weight configuration to the lookup views, CS_SR_LOAD_BALANCE_WT_V is well suited to reporting and integration layers. Rather than requiring a consumer to resolve INCIDENT_TYPE_ID and INCIDENT_SEVERITY_ID separately, the view already presents the joined lookup names, making it convenient for BI Publisher reports, Oracle Discoverer worksheets, OBIEE extracts, and custom concurrent programs that need to display or validate routing configuration.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over three referenced objects:

  • CS_SR_LOAD_BALANCE_WT (SYNONYM) — the primary base object holding the load balance weight configuration, aliased as A in the view text. This is the driving table supplying WEIGHT_ID, the scoring weight columns, DML audit columns, effective dating columns, and the DFF attribute columns.
  • CS_INCIDENT_TYPES_VL (VIEW) — the incident type lookup view, aliased as B, joined on A.INCIDENT_TYPE_ID = B.INCIDENT_TYPE_ID. It supplies the NAME column projected as INCIDENT_TYPE.
  • CS_INCIDENT_SEVERITIES_VL (VIEW) — the incident severity lookup view, aliased as C, joined on A.INCIDENT_SEVERITY_ID = C.INCIDENT_SEVERITY_ID. It supplies the NAME column projected as INCIDENT_SEVERITY.

The naming convention of the lookup views (the _VL suffix) indicates they are translation-enabled views exposing the current-language descriptive name, which is why the join results are already display-ready. The view performs inner joins, so weight records whose incident type or severity is not resolvable in the lookup views are excluded from the result set.

Key Columns

The view exposes identity, descriptive, audit, effective-dating, and weighting columns. The most significant are:

Common Use Cases and Queries

Typical usage includes verifying that weights are configured per incident type and severity, auditing effective-dated changes, and feeding assignment scoring reports. A query listing all active weights for a given severity might read:

SELECT incident_type,
       incident_severity,
       product_skill_wt,
       platform_skill_wt,
       severity1_count_wt,
       start_date_active,
       end_date_active
FROM   apps.cs_sr_load_balance_wt_v
WHERE  incident_severity = 'High'
AND    TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE)
                         AND NVL(end_date_active, SYSDATE);

To compare configurations across severities, aggregate on the resolved names:

SELECT incident_severity,
       COUNT(*) weight_count,
       AVG(severity1_count_wt) avg_sev1_wt
FROM   apps.cs_sr_load_balance_wt_v
GROUP  BY incident_severity;

For integration or extraction, the view can be queried directly by concurrent programs or external interfaces, filtering on LAST_UPDATE_DATE to capture incremental changes. Note that because the view resolves lookup names via inner joins, it is most reliable for reporting on actively maintained configuration data.