Search Results daily_maximum_rate

Overview

WIP_LINES_VAL_V is a reporting view owned by the APPS schema in Oracle E-Business Suite (documented for 12.1.1 and 12.2.2) under the Work in Process (WIP) product. Its purpose is to expose enabled production lines — that is, the manufacturing lines defined in the WIP module that are still active as of the current system date. Because it filters out disabled lines and derives an additional scheduling metric, the view is well suited for shop-floor reporting, capacity analysis, and integration scenarios that must reference only currently valid lines.

Underlying Base Objects

The view is defined over a single base object, WIP_LINES. In the documented metadata, WIP_LINES is referenced as a synonym. The enabling filter is applied in the WHERE clause:

• NVL(DISABLE_DATE, SYSDATE + 1) > SYSDATE — a row is returned only when the line has no disable date, or when its disable date is later than the current date. Lines disabled on or before SYSDATE are excluded.

All other columns are passed through from WIP_LINES, except DAILY_MAXIMUM_RATE, which is computed within the view and does not exist on the base table.

Key Columns

• LINE_ID — Primary identifier of the production line; used as a foreign key throughout WIP and related modules.
• LINE_CODE — User-assigned code that uniquely identifies the line within the organization.
• ORGANIZATION_ID — The inventory organization that owns the line.
• DESCRIPTION — Descriptive text for the line.
• MINIMUM_RATE — The minimum throughput rate defined for the line.
• MAXIMUM_RATE — The maximum throughput rate defined for the line.
• LINE_SCHEDULE_TYPE — Indicates the scheduling basis used for the line.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield columns available for customer-specific extensions.
• DAILY_MAXIMUM_RATE — A derived column calculated as:
  ROUND((MAXIMUM_RATE * DECODE(SIGN(STOP_TIME - START_TIME), -1, 86400 + STOP_TIME - START_TIME, 0, 86400, STOP_TIME - START_TIME) / 3600), 6)
  This formula accounts for shifts that cross midnight (when stop time is earlier than start time, a full day in seconds — 86400 — is added), a zero-length window is treated as a full 86400-second day, and the resulting seconds are divided by 3600 to express a daily maximum rate rounded to six decimals.

Common Use Cases and Queries

The view is typically used to populate LOVs, validation queries, and capacity reports that should never surface a disabled line. A basic listing of enabled lines for an organization looks like:

• SELECT line_id, line_code, description, minimum_rate, maximum_rate, daily_maximum_rate
• FROM  apps.wip_lines_val_v
• WHERE organization_id = :org_id
• ORDER BY line_code;

Because the search term minimum_rate maps directly to a column on this view, a targeted query such as the following is common when validating line throughput thresholds:

• SELECT line_code, minimum_rate, maximum_rate, daily_maximum_rate
• FROM  apps.wip_lines_val_v
• WHERE minimum_rate IS NOT NULL
•   AND organization_id = :org_id;

Integration consumers frequently join the view to WIP entities such as repetitive schedules or discrete jobs via LINE_ID to enforce that scheduling references only currently enabled lines. Reporting tools may also compare DAILY_MAXIMUM_RATE against planned load to identify lines operating near their capacity ceiling.

Because the enabled-status filter relies on SYSDATE, output is time-sensitive: a line disabled after the report is executed will drop out of subsequent runs without any change to the underlying table structure. This makes the view reliable for point-in-time operational reporting, though it is not intended for historical analysis of lines that are no longer active.