Search Results status_type_disp




Overview

APPS.WSM_DISCRETE_JOBS_V is a supplementary Oracle E-Business Suite view owned by the APPS schema. It is classified in the ETRM metadata as a "View Type A" object — a supplementary view used to simplify Forms coding. Oracle explicitly warns that this view is not recommended for direct querying or data alteration, since its definition may change dramatically in subsequent minor or major releases. The view is registered in FND Design Data as WSM.WSM_DISCRETE_JOBS_V and carries a VALID status in ETRM 12.2.2.

The view presents a denormalized, form-friendly projection of discrete work orders from Work in Process (WIP) alongside related assembly, organization, and status information. Its purpose is to expose the fields required by the WSM (Work Order / Shop Floor Management) Forms UI and similar internal components, including a pre-resolved display value for the work order status. Because the view is not referenced by any other database object, it functions as a terminal presentation layer rather than a shared integration source.

Underlying Base Objects

The view is defined over, or references, the following documented objects:

At the database level, several of these are referenced via APPS synonyms (MTL_KANBAN_CARDS, MTL_SECONDARY_INVENTORIES, MTL_SYSTEM_ITEMS, WIP_DISCRETE_JOBS, WIP_ENTITIES, WIP_LINES, WIP_SCHEDULE_GROUPS) rather than the physical tables directly.

Key Columns

  • ROW_ID (ROWID) — a row identifier for the underlying row.
  • WIP_ENTITY_ID (NUMBER) — the unique identifier for the work order entity.
  • WIP_ENTITY_NAME (VARCHAR2, 240) — the stored work order name/number used for identification in the UI.
  • STATUS_TYPE (NUMBER) — the numeric status code for the discrete job, sourced from MFG_LOOKUPS.
  • STATUS_TYPE_DISP (VARCHAR2, 80) — the resolved, display-ready status description corresponding to STATUS_TYPE. This is the column most directly associated with the user's search term and serves to present a human-readable status rather than the underlying lookup code.
  • PRIMARY_ITEM_ID (NUMBER) — the assembly item identifier.
  • SCHEDULED_START_DATE (DATE) — the planned start date for the work order.
  • SCHEDULED_COMPLETION_DATE (DATE) — the planned completion date.
  • ASSEMBLY_DESCRIPTION (VARCHAR2, 240) — the description of the assembly item.
  • ORGANIZATION_ID (NUMBER) — the inventory organization context for the job.

Common Use Cases and Queries

The view is typically consumed by WSM Forms to display discrete jobs alongside their status labels, effective assembly information, and scheduling dates. Because Oracle discourages direct queries, any custom use should be treated as read-only and periodically re-validated against the view definition.

A representative query retrieving work orders with their display status is:

SELECT WIP_ENTITY_ID
, WIP_ENTITY_NAME
, STATUS_TYPE
, STATUS_TYPE_DISP
, PRIMARY_ITEM_ID
, ASSEMBLY_DESCRIPTION
, SCHEDULED_START_DATE
, SCHEDULED_COMPLETION_DATE
, ORGANIZATION_ID
FROM APPS.WSM_DISCRETE_JOBS_V
WHERE ORGANIZATION_ID = :org_id
AND STATUS_TYPE_DISP IS NOT NULL;

Typical scenarios include shop-floor status dashboards, organization-scoped job listings, and reconciliation of discrete job headers with item descriptions. All operations should be limited to SELECT statements; the supplementary nature of the view means its column set and joins are not contractually guaranteed across releases.