Results for “fixed_lead_time”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BOMFV_MANUFACTURING_LINES is an APPS-owned, read-only view that exposes the manufacturing production line definitions stored in the WIP_LINES base table, enriched with organization and ATP routing context. It belongs to the Bills of Material (BOM) product family and carries a classification of "Retrofitted," indicating that it was re-engineered for later EBS releases (12.1.1 and 12.2.2) to preserve backward compatibility for downstream reports, forms, and integrations that previously depended on the legacy naming conventions.

The view presents one row per production line (WIP_LINES record) as defined within a manufacturing organization. Its principal purpose is to present line-level scheduling and costing attributes using user-friendly column aliases (for example, LINE_CODE is exposed as LINE_NAME, and DISABLE_DATE as INACTIVE_DATE). This aliasing allows reports, Discoverer workbooks, and interfaces to reference a consistently named, organization-scoped set of line attributes without joining the underlying tables directly. Because the view is defined WITH READ ONLY, it is intended strictly for query and reporting purposes; data manipulation must be performed against the underlying WIP_LINES table through the appropriate Oracle EBS forms or APIs.

Underlying Base Objects

The view is defined over four synonyms that resolve to base application tables. The primary driver is WIP_LINES (aliased LI), which supplies the manufacturing line records and virtually every column projected by the view. WIP_LINES is joined to MTL_PARAMETERS (aliased PA) on ORGANIZATION_ID and to HR_ALL_ORGANIZATION_UNITS (aliased AL) on ORGANIZATION_ID, providing the organization code and organization name respectively. An outer join is applied to MTL_ATP_RULES (aliased AT) using LI.ATP_RULE_ID = AT.RULE_ID(+) and LI.ATP_RULE_ID is a nullable foreign key, ensuring that lines without an assigned ATP rule are still returned.

The WHERE clause includes the predicate '_SEC:LI.ORGANIZATION_ID' IS NOT NULL, which is Oracle's internal mechanism for enforcing multi-organization security (MOAC) filtering at the organization level. As a result, only lines belonging to organizations accessible within the user's current security profile are visible through the view.

Key Columns

• LINE_NAME — Derived from WIP_LINES.LINE_CODE; the user-visible identifier of the production line and the object of the "line_name" search.
• ORGANIZATION_CODE / ORGANIZATION_NAME — From MTL_PARAMETERS and HR_ALL_ORGANIZATION_UNITS; identify the owning manufacturing organization.
• DESCRIPTION — Line description from WIP_LINES.
• INACTIVE_DATE — Maps to DISABLE_DATE; indicates when the line becomes unavailable for scheduling.
• MINIMUM_HOURLY_RATE / MAXIMUM_HOURLY_RATE — Bound the line's rate-based capacity costing.
• FIXED_LEAD_TIME — From FIXED_THROUGHPUT; a fixed duration added to scheduling calculations.
• LINE_START_TIME / LINE_STOP_TIME — Daily operating window for the line.
• "_LA:LINE_SCHEDULE_TYPE" — A descriptive flexfield token resolving the schedule type via the MFG_LOOKUPS lookup (WIP_LINE_SCHED_TYPE).
• RULE_NAME — From MTL_ATP_RULES; the ATP rule assigned to the line, if any.
• EXCEPTION_SET_NAME — The exception set associated with the line.
• ORGANIZATION_ID, LINE_ID, ATP_RULE_ID — Surrogate keys for joins and integrations.
• UPDATED_ON, UPDATED_BY, CREATED_ON, CREATED_BY — Audit columns from WIP_LINES.

Common Use Cases and Queries

Typical scenarios include capacity and scheduling reports that enumerate active production lines per organization, rate-based costing extracts, and ATP configuration audits. Because organization security is enforced internally, the view is convenient for MOAC-aware reporting.

List all active lines in a given organization:

SELECT line_name, description, organization_code,
       minimum_hourly_rate, maximum_hourly_rate,
       line_start_time, line_stop_time
FROM   apps.bomfv_manufacturing_lines
WHERE  organization_code = 'M1'
AND   (inactive_date IS NULL OR inactive_date > SYSDATE);

Retrieve lines with their assigned ATP rule:

SELECT line_name, organization_name, rule_name, exception_set_name
FROM   apps.bomfv_manufacturing_lines
WHERE  rule_name IS NOT NULL
ORDER  BY organization_name, line_name;

Search by line name across accessible organizations:

SELECT line_name, organization_code, organization_name, inactive_date
FROM   apps.bomfv_manufacturing_lines
WHERE  UPPER(line_name) LIKE UPPER(:line_name || '%');

As with all APPS views, queries should be issued with the appropriate MOAC initialization (for example, via fnd_global or a secured Oracle EBS responsibility) so that the organization security predicate resolves to the intended operating unit context.