Search Results csd_group_job_param_temp

Overview

The CS_INCIDENTS_ALL_B table is a core transactional entity within the Oracle E-Business Suite (EBS) Service (CS) module, specifically for versions 12.1.1 and 12.2.2. It serves as the primary repository for non-translated, master information related to service requests (also referred to as incidents). As a multi-organization enabled table, denoted by the "_ALL_" suffix, it stores data across operating units, making it the central table for all service request creation, tracking, and management. Its role is fundamental to the Service module's functionality, linking service requests to customers, inventory items, systems, and the broader trading community architecture.

Key Information Stored

The table's structure is defined by its primary and foreign keys, which reveal the critical data points it holds. The primary identifier is the system-generated INCIDENT_ID, while the user-facing, unique key is the INCIDENT_NUMBER. Essential stored information includes customer and site details via foreign keys to the HZ (Trading Community) schema, such as BILL_TO_PARTY_ID, SHIP_TO_SITE_ID, and INSTALL_SITE_ID. It links to the item categorization structure (CATEGORY_ID, CATEGORY_SET_ID) and tracks the service request's current state via INCIDENT_STATUS_ID. Other pivotal columns include OWNING_DEPARTMENT_ID for assignment, SYSTEM_ID for linked configurations, and contact point IDs (CUSTOMER_EMAIL_ID, PRIMARY_CONTACT_ID) for communication.

Common Use Cases and Queries

This table is central to operational reporting, data extracts, and custom integrations. Common use cases include generating open service request lists, analyzing incident volume by customer or product category, and building data feeds for external CRM systems. A typical query to retrieve basic incident details with customer information would join to Trading Community tables.

• Sample Query Pattern:
  SELECT inc.incident_number,
  inc.creation_date,
  sts.name status,
  party.party_name
  FROM cs_incidents_all_b inc,
  cs_incident_statuses_b sts,
  hz_parties party
  WHERE inc.incident_status_id = sts.incident_status_id
  AND inc.bill_to_party_id = party.party_id
  AND inc.owning_department_id = :dept_id
  AND TRUNC(inc.creation_date) >= :start_date;
• Data fixes or updates often target the INCIDENT_STATUS_ID or OWNING_DEPARTMENT_ID columns, but must be performed with caution and typically through official APIs.

Related Objects

CS_INCIDENTS_ALL_B is the hub of a complex data model. Its primary transactional counterpart is CS_INCIDENTS_ALL_TL, which stores the translated descriptions and summaries. Key foreign key dependencies, as documented, include:

• HZ_PARTIES, HZ_CUST_ACCOUNTS, HZ_PARTY_SITES: For customer and site information.
• CS_INCIDENT_STATUSES_B: For valid status values.
• CSI_SYSTEMS_B: For linked installed base items.
• MTL_CATEGORIES_B: For item categorization.
• BOM_DEPARTMENTS: For the owning service department.

For programmatic access and data integrity, the standard Oracle Service Request APIs (e.g., CS_ServiceRequest_PUB) should be used instead of direct DML on this table.