Search Results assembly_description




Overview
Explore in AI Chat

Overview

WSM_DISCRETE_JOBS_V is an APPS-owned database view in Oracle E-Business Suite (validated in 12.1.1 and 12.2.2) belonging to the WSM — Shop Floor Management product family. It presents a consolidated, denormalized read model of discrete manufacturing jobs. Rather than forcing a report or integration to join the three WIP tables (WIP_ENTITIES, WIP_DISCRETE_JOBS, and their lookups) manually, the view surfaces the job identifier, job name, status, item assembly, and scheduling dates in a single queryable object. It is a convenience layer for shop-floor reporting, dashboarding, and inbound/outbound interfaces that need job header information without navigating the full WIP schema. The view text explicitly exposes the assembly item description, which is a common search target for users reconciling job output to item master records.

Underlying Base Objects

The view is defined over the following documented base objects, all referenced through APPS synonyms or, in one case, a view:

  • WIP_DISCRETE_JOBS — the primary driver table holding the discrete job header (status type, primary item, dates, organization).
  • WIP_ENTITIES — supplies the human-readable WIP_ENTITY_NAME associated to the job.
  • MTL_SYSTEM_ITEMS — supplies the assembly description (MSI.DESCRIPTION) for the primary item.
  • MFG_LOOKUPS (documented as a VIEW) — outer-joined twice as LU1 (lookup type WIP_JOB_STATUS) and LU2 (lookup type WIP_SUPPLY), providing decoded status and supply-type meanings.
  • MTL_SECONDARY_INVENTORIES — outer-joined (MSUB) for the completion subinventory.
  • WIP_LINES — outer-joined (WL) for the production line.
  • WIP_SCHEDULE_GROUPS — outer-joined (WSG) for schedule group context.
  • MTL_KANBAN_CARDS — outer-joined (KC) for kanban sourcing information.

All joins use the (+) outer-join syntax, indicating the view is intentionally permissive—jobs without a matching line, schedule group, subinventory, or kanban card are still returned. The join between WDJ.PRIMARY_ITEM_ID / WDJ.ORGANIZATION_ID and MTL_SYSTEM_ITEMS is outer-joined to the item master.

Key Columns

  • ROW_ID — the WIP_DISCRETE_JOBS rowid, suitable for update/delete targeting.
  • WIP_ENTITY_ID — the primary key linking the job across the WIP schema.
  • WIP_ENTITY_NAME — the user-visible job or assembly name.
  • STATUS_TYPE — the lookup code for job status.
  • STATUS_TYPE_DISP — the decoded status meaning from MFG_LOOKUPS, ideal for display and filtering.
  • PRIMARY_ITEM_ID — the inventory item identifier of the assembly.
  • ASSEMBLY_DESCRIPTION — the description of the assembly item from MTL_SYSTEM_ITEMS; this is the column users search for when matching job output to item definitions.
  • SCHEDULED_START_DATE / SCHEDULED_COMPLETION_DATE — the job scheduling window.
  • ORGANIZATION_ID — the inventory organization owning the job, essential for multi-org security and filtering.

Common Use Cases and Queries

Typical applications include shop-floor status boards, job scheduling reports, and integration extracts that feed MES or planning systems. The view is frequently queried to list released or unreleased jobs with their decoded status and assembly description:

SELECT WIP_ENTITY_NAME,
       STATUS_TYPE_DISP,
       PRIMARY_ITEM_ID,
       ASSEMBLY_DESCRIPTION,
       SCHEDULED_START_DATE,
       SCHEDULED_COMPLETION_DATE
  FROM APPS.WSM_DISCRETE_JOBS_V
 WHERE ORGANIZATION_ID = :p_org_id
   AND STATUS_TYPE_DISP = 'Released'
 ORDER BY SCHEDULED_START_DATE;

To find jobs for a specific assembly by description, filter on ASSEMBLY_DESCRIPTION or join on PRIMARY_ITEM_ID. Practitioners should note that because the item master join is outer, jobs with an orphaned item reference will return a null ASSEMBLY_DESCRIPTION; such rows warrant data-cleansing review. Additionally, since MFG_LOOKUPS is a view, ensure the correct lookup types (WIP_JOB_STATUS, WIP_SUPPLY) are populated in the target environment to avoid null status displays. The view is read-only by nature; DML should be directed at WIP_DISCRETE_JOBS through the WIP APIs or forms.