Results for “interfaced_to_depot_flag”

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

Overview

CS_INCIDENTS_ALL_VL is the multi-lingual (ML) view owned by the APPS schema in the Oracle E-Business Suite Service (CS) product family. It presents service incident and service request data by joining the base incident table with its translation table, exposing a single denormalized row per incident per installed language. The "_VL" suffix denotes a "view, language" object, which is the standard EBS pattern for presenting translated (TL) entities alongside their base (B) attributes.

The view is VALID in both release 12.1.1 and 12.2.2 and is a core read interface for Service Request reporting, OBIEE/BI Publisher extracts, custom forms, and integration interfaces. Rather than querying the base tables directly, developers and analysts use this view to obtain incident summary text already resolved to the session or desired language, avoiding manual joins to the translation table.

Underlying Base Objects

The view is defined over two documented base objects, both accessed as APPS synonyms:

• CS_INCIDENTS_ALL_B — the base (non-translated) incident table holding all language-independent attributes such as incident number, dates, status, owner, resource, and customer references.
• CS_INCIDENTS_ALL_TL — the translation table holding language-dependent columns: LANGUAGE, SOURCE_LANG, and SUMMARY.

The view text selects all columns from the "_B" table (aliased B) and joins the LANGUAGE, SOURCE_LANG, and SUMMARY columns from the "_TL" table (aliased TL), keyed on INCIDENT_ID and LANGUAGE. It also exposes B.ROWID as ROW_ID. This relationship means a single incident can produce multiple view rows — one per translated language — so queries must filter on LANGUAGE (or rely on EBS' language-secured synonyms) to avoid duplicate rows.

Key Columns

• INCIDENT_ID / INCIDENT_NUMBER — primary key and user-facing service request number.
• INCIDENT_DATE, CLOSE_DATE, EXPECTED_RESOLUTION_DATE, ACTUAL_RESOLUTION_DATE, OBLIGATION_DATE — lifecycle and SLA-relevant timestamps.
• INCIDENT_STATUS_ID, INCIDENT_TYPE_ID, INCIDENT_URGENCY_ID, INCIDENT_SEVERITY_ID, INCIDENT_OWNER_ID — classification and ownership foreign keys.
• SUMMARY — the translated incident description from CS_INCIDENTS_ALL_TL, the principal ML column.
• LANGUAGE / SOURCE_LANG — installed language and the language of the source record.
• CUSTOMER_ID, ACCOUNT_ID, CUSTOMER_NUMBER, CUSTOMER_PRODUCT_ID, INVENTORY_ITEM_ID, CURRENT_SERIAL_NUMBER — customer and installed-base context.
• ORG_ID — operating unit, enforcing multi-org security.
• RESOLUTION_CODE, PROBLEM_CODE — resolution and problem categorization.
• INCIDENT_ATTRIBUTE_1 through INCIDENT_ATTRIBUTE_15, INCIDENT_CONTEXT — extensible descriptive flexfield (DFF) segments.
• RESOURCE_TYPE, RESOURCE_SUBTYPE_ID, SYSTEM_ID, PLATFORM_VERSION_ID — resource/asset modeling.
• OBJECT_VERSION_NUMBER — optimistic locking support for the underlying row.

Common Use Cases and Queries

Typical scenarios include aging/backlog reports, SLA compliance analysis, customer incident history, and interfaces feeding external CRM or analytics platforms. A representative query returns open incidents with translated summaries for a given operating unit:

• SELECT incident_number, incident_date, incident_status_id, summary FROM cs_incidents_all_vl WHERE org_id = :p_org_id AND close_date IS NULL ORDER BY incident_date;
• SELECT customer_number, COUNT(*) FROM cs_incidents_all_vl WHERE TRUNC(incident_date) >= TRUNC(SYSDATE)-30 GROUP BY customer_number;
• SELECT incident_number, expected_resolution_date, actual_resolution_date FROM cs_incidents_all_vl WHERE actual_resolution_date > expected_resolution_date;

Because the view is a synonym-based join across "_B" and "_TL", queries should always constrain ORG_ID for multi-org security and filter or join on LANGUAGE when a specific translation is required. When only base attributes are needed, querying CS_INCIDENTS_ALL_B avoids the translation join and duplication entirely; use the "_VL" view when the SUMMARY text is part of the result.