Search Results wip_dj_close_temp




Overview
Explore in AI Chat

Overview

WIP_DJ_CLOSE_TEMP is a transient staging table in the Work in Process (WIP) module of Oracle E-Business Suite, owned by the WIP schema. Its documented purpose is to hold "temporary information on jobs being closed." In practice, the table functions as a working set for the discrete job close process: when a user or concurrent program initiates closure of one or more discrete jobs, qualifying jobs are collected into this table, processed, and cleared. It is not a permanent transactional ledger; rows generally exist only for the duration of a close request.

From a dimensional modeling perspective, the mined relationship data classifies WIP_DJ_CLOSE_TEMP as satellite-leaning. This is a modeling suggestion rather than a physical property: the table carries descriptive and status attributes about a discrete job close event, keyed by the job entity, which is the characteristic shape of a satellite hanging off a hub (here, the discrete job hub represented by WIP_DISCRETE_JOBS).

Key Information Stored

The table has seven documented columns. The most significant are:

  • WIP_ENTITY_ID — The job identifier. This is both the primary key column of WIP_DJ_CLOSE_TEMP_PK and a unique business-key candidate via index WIP_DJ_CLOSE_TEMP_U1. It is also the foreign key to WIP_DISCRETE_JOBS, tying each staging row to its source job.
  • ORGANIZATION_ID — The inventory organization that owns the job, essential for multi-org filtering and reporting.
  • WIP_ENTITY_NAME — The user-facing job or work order name, carried into the staging table for identification and reporting without a join.
  • STATUS_TYPE — The status classification of the job being closed, used by the close program to select and segregate eligible records.
  • PRIMARY_ITEM_ID — The primary assembly item of the job, resident in the staging row to support item-level reporting and validation.
  • ACTUAL_CLOSE_DATE — The date the job was actually closed, populated as part of the close processing.
  • GROUP_ID — A grouping identifier, typically assigned per concurrent request or processing run, allowing a single batch of jobs to be processed and purged together.

Where a pure surrogate key would exist in a Data Vault hub, the satellite-leaning WIP_ENTITY_ID serves as the effective entity key; no separate surrogate is documented.

Common Use Cases and Queries

Primary use is diagnostic and monitoring of the discrete job close cycle. Typical patterns include checking for rows left behind by a failed or interrupted close request, confirming which jobs a given request touched, and validating the close date recorded. Sample queries:

  • List currently staged jobs: SELECT wip_entity_id, wip_entity_name, organization_id, status_type FROM wip.wip_dj_close_temp;
  • Rows for a specific concurrent request batch: SELECT * FROM wip.wip_dj_close_temp WHERE group_id = :group_id;
  • Join to the source job to reconcile close dates: SELECT t.wip_entity_name, t.actual_close_date, d.date_closed FROM wip.wip_dj_close_temp t JOIN wip.wip_discrete_jobs d ON d.wip_entity_id = t.wip_entity_id;
  • Organization-level activity: SELECT organization_id, COUNT(*) FROM wip.wip_dj_close_temp GROUP BY organization_id;

Because data is temporary, reporting should treat this table as a transient work area, never as a retained close history. Persistent close history belongs in WIP_DISCRETE_JOBS.

Related Objects

  • WIP_DISCRETE_JOBS — The parent table; joined on WIP_DJ_CLOSE_TEMP.WIP_ENTITY_ID = WIP_DISCRETE_JOBS.WIP_ENTITY_ID, the documented foreign key.
  • WIP_ENTITIES — The master WIP entity table keyed by WIP_ENTITY_ID, used for broader job context.
  • WIP_DISCRETE_JOBS_TEMP / close concurrent programs — The processing programs that populate and consume this staging table.
  • MTL_SYSTEM_ITEMS_B — Joined on PRIMARY_ITEM_ID for item descriptions.
  • ORG_ORGANIZATION_DEFINITIONS — Joined on ORGANIZATION_ID to resolve organization names.