Search Results as_tap_purge_working




Overview
Explore in AI Chat

Overview

AS_TAP_PURGE_WORKING is a transient working table owned by the OSM schema within the AS – Sales Foundation product family of Oracle E-Business Suite. Its documented purpose is to serve as the staging and processing workspace for the TAP purge program, a concurrent utility responsible for the controlled removal of obsolete territory assignment and related transaction data. The table is not an end-user or reporting object; it exists to support a batch purge process by holding the set of records selected for evaluation, thereby decoupling the selection phase from the deletion phase and reducing contention on the parent business tables.

The documented relationship metadata classifies AS_TAP_PURGE_WORKING as standalone under the heuristic Data Vault model. From a modeling perspective this is reasonable: the table behaves as a satellite-like staging artifact with no true parent-child dependencies of its own, and its lifecycle is bounded by the duration of the purge run rather than by long-term reference to a business entity. It should therefore be treated as a technical work area rather than a durable dimension or fact source.

Key Information Stored

The documented physical schema exposes eight columns. The most significant are:

  • ROW_ID – the principal identifier column, which carries a foreign key reference to CS_SYSTEMS_ALL_B_TEMP. This links each working row back to the system record being processed.
  • WORKER_ID – identifies the purge worker or processing unit assigned to the row, enabling parallel execution and partitioning of the purge workload.
  • ACCESS_ID – the access identifier used to scope the record within the purge criteria.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY – standard EBS audit trail columns recording the most recent modification and its author.
  • CREATION_DATE, CREATED_BY – standard EBS audit columns recording initial insertion.
  • LAST_UPDATE_LOGIN – the login context associated with the last update, used for diagnostic tracing of concurrent sessions.

The surrogate key is ROW_ID, which also functions as the join key to the referenced CS_SYSTEMS table. No alternative unique business key is documented, so queries should not assume uniqueness on WORKER_ID or ACCESS_ID independently. The audit columns are the standard WHO columns applied across EBS transactional and technical tables.

Common Use Cases and Queries

The primary use case is operational monitoring of an in-flight or completed TAP purge. Because the table is a work area, typical queries are diagnostic rather than analytical. A simple workload distribution check helps confirm that the purge is balanced across workers:

  • SELECT WORKER_ID, COUNT(*) FROM AS_TAP_PURGE_WORKING GROUP BY WORKER_ID;
  • SELECT ROW_ID, ACCESS_ID, LAST_UPDATE_DATE FROM AS_TAP_PURGE_WORKING WHERE WORKER_ID = :worker;

Administrators also use the table to verify which system rows remain pending purge by joining to the referenced parent:

  • SELECT w.ROW_ID FROM AS_TAP_PURGE_WORKING w, CS_SYSTEMS_ALL_B_TEMP s WHERE w.ROW_ID = s.ROW_ID;

Audit queries correlating CREATED_BY and LAST_UPDATED_BY with concurrent program execution help confirm that the correct program instance populated the workspace before deletion proceeds.

Related Objects

The documented foreign key points from ROW_ID to CS_SYSTEMS_ALL_B_TEMP, making that table the most significant related object. Beyond the documented relationship, the following are the objects most commonly associated with this purge pattern in Oracle EBS implementations:

  • CS_SYSTEMS_ALL_B_TEMP – referenced parent supplying the system records under purge (join on ROW_ID).
  • CS_SYSTEMS_ALL_B and CS_SYSTEMS_ALL_TL – the base and translated system tables the temporary carries forward.
  • AS_TAP_PURGE_* sibling working and log tables belonging to the same purge program.
  • The TAP purge concurrent program definition in the concurrent manager, which populates and consumes this table.

Because the object is schema-qualified and proprietary, direct modification outside the purge program is not supported and should be avoided.