Search Results overcompletion_tolerance_value




Overview
Explore in AI Chat

Overview

The WIPBV_WIP_REPETITIVE_ITEMS view is a business view (indicated by the "BV" naming convention) owned by the APPS schema in Oracle E-Business Suite. It is part of the Work in Process (WIP) product module and exposes repetitive manufacturing definition data. In Oracle EBS 12.1.1 and 12.2.2, business views such as this one are typically consumed by Oracle Forms-based "quick" pickers, LOV (List of Values) windows, and integrations that require a flattened, user-friendly projection of the underlying transactional and setup tables.

The view consolidates attributes from the WIP entity header, the repetitive line definition, and the repetitive item setup into a single query surface. This allows forms and reports to retrieve repetitive schedule context—such as the production line, the primary assembly, completion subinventory, and overcompletion tolerances—without joining three physical tables manually. Because it carries an _LA: prefixed column naming pattern, the view is also structured to support label/LOV substitution metadata used by Oracle's generic form and picker infrastructure.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, the view is defined over three base objects, all referenced as synonyms in the APPS schema:

  • WIP_ENTITIES — the WIP entity master, providing the entity name and the entity identifier linking the schedule to its execution context.
  • WIP_LINES — the production line definitions, supplying the line code used to identify the repetitive line on which the assembly is built.
  • WIP_REPETITIVE_ITEMS — the repetitive item setup, which holds the primary assembly, alternate BOM and routing designators, supply type, completion subinventory/locator, and overcompletion tolerance attributes.

The joins are established on RE.WIP_ENTITY_ID = EN.WIP_ENTITY_ID and on the composite key RE.LINE_ID = LI.LINE_ID AND RE.ORGANIZATION_ID = LI.ORGANIZATION_ID. The view enforces organization-level security via the predicate '_SEC:RE.ORGANIZATION_ID' IS NOT NULL, and it is defined WITH READ ONLY, meaning it cannot be used as the target of DML. Consequently, it is strictly a query and reporting object.

Key Columns

The view projects a focused set of columns relevant to repetitive manufacturing. Notable attributes include:

Common Use Cases and Queries

The view is typically used to populate pickers and to report repetitive schedule setup, especially overcompletion tolerance configuration. A representative query to retrieve tolerance settings for repetitive items in an organization is:

  • SELECT WIP_ENTITY_NAME, LINE_NAME, INVENTORY_ITEM_ID, OVERCOMPLETION_TOLERANCE_VALUE, "_LA:OVERCOMP_TOLERANCE_TYPE" FROM APPS.WIPBV_WIP_REPETITIVE_ITEMS WHERE ORGANIZATION_ID = :org_id;

Other scenarios include auditing which repetitive lines carry a non-zero tolerance, listing alternate BOM/routing assignments per schedule, and driving completion validation logic. Because the view is read-only, any corrective action must be performed against WIP_REPETITIVE_ITEMS directly, while this view remains the preferred read surface for forms, reports, and integration extracts.