Results for “purge_status”

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

Overview

CS_INCIDENTS_PURGE_STAGING is a Service (CS) module staging table in the Oracle E-Business Suite CS schema. It is used to hold the set of Service Requests (SRs) that are candidates for purge, based on a supplied set of purge parameters. Rather than deleting or archiving incident records directly from the transactional tables, the purge process first materializes the qualifying SR set into this staging table, providing a stable working set for validation, error capture, and controlled downstream processing.

Under the heuristic Data Vault classification supplied in the ETRM metadata, this object is modeled as satellite-leaning. Its structure — a single primary key column (INCIDENT_ID) with descriptive status and audit attributes — is consistent with a satellite surrounding the incident business key rather than a hub or link. This is a modeling suggestion only; the table is a physical staging construct, not a Data Vault artifact.

Key Information Stored

The documented physical schema (ETRM 12.2.2) contains five columns, with INCIDENT_ID serving as the primary key via constraint CS_INCIDENTS_PURGE_STAGING_PK. A unique index, CS_INCIDENTS_PURGE_STAGING_U1, also exists on INCIDENT_ID, making that column both the surrogate primary key and the effective business-key candidate for this staging set. The most significant columns are:

• INCIDENT_ID — Identifier of the Service Request selected for purge. Primary key of the table and the sole unique-indexed column.
• WORKER_ID — Identifies the concurrent worker or process instance responsible for staging the SR, supporting parallel purge processing.
• CONCURRENT_REQUEST_ID — The concurrent request that populated the staging row, enabling traceability back to a specific purge run.
• PURGE_STATUS — Processing state of the staged SR (for example, pending, processed, or failed), used to drive and monitor the purge workflow.
• PURGE_ERROR_MESSAGE — Captures the error text when a staged SR cannot be purged, providing the diagnostic record for exception handling and reprocessing.

The remaining documented column set is narrow by design, since the staging table identifies SRs and tracks their purge lifecycle rather than duplicating full incident data.

Common Use Cases and Queries

Typical use cases center on running and auditing the SR purge process. Administrators may review what was staged for a given concurrent request, identify failed purges, or clear stale staging rows before a rerun.

• Report SRs staged by a specific purge run: SELECT INCIDENT_ID, PURGE_STATUS FROM CS.CS_INCIDENTS_PURGE_STAGING WHERE CONCURRENT_REQUEST_ID = :req_id;
• List purge failures with messages: SELECT INCIDENT_ID, PURGE_ERROR_MESSAGE FROM CS.CS_INCIDENTS_PURGE_STAGING WHERE PURGE_STATUS = 'ERROR';
• Count staged versus processed SRs by worker to measure parallel throughput using WORKER_ID.
• Join to CS_INCIDENTS_ALL_B to confirm the SR number and subject for staged records.

Related Objects

The documented foreign key establishes the primary dependency:

• CS_INCIDENTS_ALL_B — Referenced by CS_INCIDENTS_PURGE_STAGING.INCIDENT_ID; the base Service Request table holding incident header data. This is the principal join target to enrich staged rows with SR details.
• CS_INCIDENTS_ALL_TL — Translation table for incident descriptive fields, commonly joined for SR subject text in reports.
• FND_CONCURRENT_REQUESTS — Relates to CONCURRENT_REQUEST_ID to identify the purge run and its status.
• FND_CONCURRENT_PROGRAMS — Provides the concurrent program definition backing the SR purge process.
• CS_INCIDENTS_ALL_B (indexes/constraints) — The PK constraint CS_INCIDENTS_PURGE_STAGING_PK and unique index CS_INCIDENTS_PURGE_STAGING_U1 govern row uniqueness and support the join to the incident base table.

Because the schema exposes only these relationships, integrations should treat INCIDENT_ID as the authoritative link between the staging set and the Service Request base tables.