Search Results entity_description

Overview

The WIP_REP_OPEN_ALLOCATIONS_V view is a reporting and integration object delivered in the APPS schema of Oracle E-Business Suite (validated against 12.1.1 and 12.2.2). It exposes open allocations for repetitive schedules within the Work in Process (WIP) module. In repetitive manufacturing, a schedule represents an ongoing production commitment across a line rather than a discrete job. This view consolidates the schedule header, its primary item, its line assignment, and the outstanding material requirements driven by those schedules so that planners, shop-floor users, and external systems can identify allocations that have not yet been fully satisfied.

Its principal role is to present, in a single denormalized result set, the repetitive schedules that are still active (status values 3 and 4, resolved through the WIP_JOB_STATUS lookup) together with the earliest date on which material is required. This makes the view suitable for supply/demand analysis, component shortage identification, and integration feeds that need an at-a-glance picture of open repetitive allocations.

Underlying Base Objects

The view is defined over a set of WIP and inventory base objects, joined to reconcile the schedule, its item, its routing requirements, and its line context. Documented referenced objects include:

• WIP_ENTITIES — the generic WIP entity header carrying WIP_ENTITY_ID, WIP_ENTITY_NAME, ORGANIZATION_ID, ENTITY_TYPE, and PRIMARY_ITEM_ID.
• WIP_REPETITIVE_SCHEDULES — schedule-level data such as STATUS_TYPE, LINE_ID, dates, and DAILY_PRODUCTION_RATE.
• WIP_REPETITIVE_ITEMS and WIP_REQUIREMENT_OPERATIONS — the item and component requirement detail underlying open allocations.
• WIP_LINES and WIP_OPERATIONS — line code and operation context, with operations joined as an outer (count-point-filtered) join.
• MTL_SYSTEM_ITEMS_KFV and MTL_SYSTEM_ITEMS_TL — concatenated item segments, primary UOM, and language-specific item description.
• MFG_LOOKUPS — resolves STATUS_TYPE to the STATUS meaning via LOOKUP_TYPE 'WIP_JOB_STATUS'.
• WIP_PARAMETERS, MTL_TXN_REQUEST_LINES — supporting organization and move-order context.

The joins enforce organization consistency across the item, entity, and translation tables, and require the translation language to match the session language via USERENV('LANG').

Key Columns

• WIP_ENTITY_NAME / WIP_ENTITY_ID / ORGANIZATION_ID — the repetitive schedule identity and its owning organization.
• REPETITIVE_SCHEDULE_ID, WIP_ENTITY_TYPE — the schedule key and entity classification.
• ENTITY_DESCRIPTION — the schedule description, sourced from WIP_REPETITIVE_SCHEDULES.DESCRIPTION.
• PRIMARY_ITEM, PRIMARY_ITEM_DESCRIPTION, PRIMARY_ITEM_ID, PRIMARY_UOM_CODE — the assembled item number, its description, internal ID, and unit of measure.
• STATUS_TYPE / STATUS — the numeric schedule status and its decoded lookup meaning.
• FIRST_OPEN_REQUIREMENTS_DATE — the minimum DATE_REQUIRED across the schedule's open requirements, i.e., the earliest outstanding need.
• START_DATE / COMPLETION_DATE — first unit start and last unit completion dates for the schedule.
• LINE_CODE — the repetitive line to which the schedule is assigned.
• DAILY_PRODUCTION_RATE and TOTAL_QUANTITY — the daily rate and the derived total (rate multiplied by PROCESSING_WORK_DAYS).

Common Use Cases and Queries

Typical usage centers on identifying open repetitive allocations with outstanding material demand, often filtered by organization, line, or earliest requirement date.

• Listing open allocations by organization: SELECT wip_entity_name, primary_item, status, first_open_requirements_date FROM wip_rep_open_allocations_v WHERE organization_id = :org ORDER BY first_open_requirements_date;
• Finding component shortages by line: SELECT line_code, wip_entity_name, primary_item, total_quantity FROM wip_rep_open_allocations_v WHERE line_code = :line;
• Feeding integration extracts that require item, UOM, and schedule status: SELECT wip_entity_id, primary_item, primary_uom_code, status, start_date, completion_date FROM wip_rep_open_allocations_v;

Because the view already restricts to active repetitive statuses and applies the count-point filter (per Bug 5504661), consumers can use it directly without re-implementing WIP allocation logic, making it a reliable source for repetitive-manufacturing reporting and downstream integration.