Results for “wip_shop_floor_status_codes”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
WIP_SHOP_FLOOR_STATUS_CODES is a Work in Process (WIP) reference table that defines the discrete statuses a job or schedule may assume on the shop floor within a given organization. A shop floor status in Oracle EBS represents the operational state of a discrete job or repetitive schedule — for example, released to the floor, on hold pending material, awaiting inspection, or awaiting a rework disposition. The table is organization-scoped, meaning the same status code can be defined independently per manufacturing organization, which permits each plant to model its own operational workflow while retaining a consistent business identifier.
The table stores both the code definition and control attributes that determine whether moving a job into or out of that status is permitted to trigger a transaction. From a Data Vault modeling perspective, the documented foreign key structure is satellite-leaning: the table primarily carries descriptive attributes qualifying the combination of a status code and an organization, rather than serving as a pure hub or acting as a many-to-many resolution link.
Key Information Stored
The primary key of the table is WIP_SHOP_FLOOR_STATUS_CODES_PK, composed of SHOP_FLOOR_STATUS_CODE and ORGANIZATION_ID. A unique index, WIP_SHOP_FLOOR_STATUS_CODES_U1, covers the same two columns and therefore serves as the business-key candidate; there is no separate surrogate identifier in the documented schema. The most significant columns are:
- SHOP_FLOOR_STATUS_CODE — the business identifier of the status, combined with organization to form the primary key.
- ORGANIZATION_ID — the manufacturing organization that owns the definition; confirmed by foreign key to WIP_PARAMETERS.
- DESCRIPTION — the user-facing name displayed in shop floor and job status windows.
- DISABLE_DATE — the date from which the status is no longer available for selection on new job status changes.
- STATUS_MOVE_FLAG — controls whether a job may be moved into or out of this status, governing the allowable transitions on the floor.
- LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns.
- ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield (DFF) columns, available for customer-defined extensions.
Common Use Cases and Queries
Typical reporting resolves the status code stored on a job or schedule against this table to obtain a readable description and to determine whether transitions are permitted. A representative query for active statuses in an organization is:
SELECT shop_floor_status_code, description, status_move_flag FROM wip_shop_floor_status_codes WHERE organization_id = :org_id AND (disable_date IS NULL OR disable_date > SYSDATE) ORDER BY shop_floor_status_code;
Common scenarios include building a shop floor status list of values for custom job-management screens, validating allowed status transitions before invoking WIP job status update APIs, and auditing which statuses have been disabled over time. Because the table is organization-scoped, reporting solutions must always include ORGANIZATION_ID in the predicate to avoid cross-organization ambiguity.
Related Objects
The following objects are most significant in relation to this table:
- WIP_SHOP_FLOOR_STATUSES — references this table on SHOP_FLOOR_STATUS_CODE and ORGANIZATION_ID; it is the primary dependent entity holding status assignment data.
- WIP_PARAMETERS — referenced by this table on ORGANIZATION_ID; supplies the manufacturing organization definition.
- WIP_DISCRETE_JOBS — stores the current shop floor status of a discrete job.
- WIP_REPETITIVE_SCHEDULES — stores the current shop floor status of a repetitive schedule.
- WIP_JOB_STATUS_INSTANCES and the WIP job status update APIs — used to apply and record status transitions validated against these definitions.
Together these objects form the control layer through which shop floor statuses are defined, assigned, and transitioned across an organization's manufacturing execution.
-
Statuses that a job or schedule may assume
-
Statuses that a job or schedule may assume
-
APPS.WIPBV_INTRAOP_STEP_STATUSES·↳ HR_ALL_ORGANIZATION_UNITS·↳ MFG_LOOKUPS·↳ MTL_PARAMETERS·Explore WIP module →
-
View: WIPBV_WIP_STATUS_CODES 12.1.1
APPS.WIPBV_WIP_STATUS_CODES·↳ HR_ALL_ORGANIZATION_UNITS·↳ MFG_LOOKUPS·↳ MTL_PARAMETERS·Explore WIP module →
-
View: WIPFV_WIP_STATUS_CODES 12.2.2
APPS.WIPFV_WIP_STATUS_CODES·↳ HR_ALL_ORGANIZATION_UNITS·↳ MFG_LOOKUPS·↳ MTL_PARAMETERS·Explore WIP module →
-
View: WIPFV_WIP_STATUS_CODES 12.1.1
APPS.WIPFV_WIP_STATUS_CODES·↳ HR_ALL_ORGANIZATION_UNITS·↳ MFG_LOOKUPS·↳ MTL_PARAMETERS·Explore WIP module →
-
Enabled shop floor statuses
APPS.WIP_SHOP_FLOOR_STATUSES_VAL_V·↳ WIP_SHOP_FLOOR_STATUS_CODES·Explore WIP module →
-
View: WIPBV_WIP_STATUS_CODES 12.2.2
APPS.WIPBV_WIP_STATUS_CODES·↳ HR_ALL_ORGANIZATION_UNITS·↳ MFG_LOOKUPS·↳ MTL_PARAMETERS·Explore WIP module →
-
Enabled shop floor statuses
APPS.WIP_SHOP_FLOOR_STATUSES_VAL_V·↳ WIP_SHOP_FLOOR_STATUS_CODES·Explore WIP module →
-
APPS.WIPFV_INTRAOP_STEP_STATUSES·↳ HR_ALL_ORGANIZATION_UNITS·↳ MFG_LOOKUPS·↳ MTL_PARAMETERS·Explore WIP module →
-
APPS.WIPBV_INTRAOP_STEP_STATUSES·↳ HR_ALL_ORGANIZATION_UNITS·↳ MFG_LOOKUPS·↳ MTL_PARAMETERS·Explore WIP module →
-
APPS.WIPFV_INTRAOP_STEP_STATUSES·↳ HR_ALL_ORGANIZATION_UNITS·↳ MFG_LOOKUPS·↳ MTL_PARAMETERS·Explore WIP module →
-
Foreign-key data for WIP_SHOP_FLOOR_STATUSES
APPS.WIP_SHOP_FLOOR_STATUSES_V·↳ BOM_DEPARTMENTS·↳ MFG_LOOKUPS·↳ WIP_OPERATIONS·Explore WIP module →
-
Foreign-key data for WIP_SHOP_FLOOR_STATUSES
APPS.WIP_SHOP_FLOOR_STATUSES_V·↳ BOM_DEPARTMENTS·↳ MFG_LOOKUPS·↳ WIP_OPERATIONS·Explore WIP module →
-
Statuses assigned to particular jobs and schedules