Search Results actual_quantity

Overview

WIP_BIS_PERF_TO_PLAN_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, residing in the Work in Process (WIP) product. Its documented purpose is to report the "number of items produced/scheduled," making it a production-versus-plan analysis object that compares scheduled quantities against actual completed quantities at the organization, item, and week level. The view is classified as a business intelligence (BIS) view, evidenced by the naming prefix and its dependency on BOM_ORG_CAL_WEEKS_VIEW, indicating it is designed to feed operational reporting, dashboards, and downstream analytical extracts rather than to support transactional processing.

The object carries a VALID status in the ETRM catalog for 12.1.1 and 12.2.2. Because it is a view and not a table, it exposes no independent storage; all results are derived at query time from the WIP_BIS_PERF_TO_PLAN synonym joined to organization, item, calendar, and category metadata. Users searching on the term "week_end_date" arrive at this view because WEEK_END_DATE is one of its exposed columns, computed as the day immediately preceding the next week start in the manufacturing organization calendar.

Underlying Base Objects

The view is defined over the following documented objects. The driving synonym is WIP_BIS_PERF_TO_PLAN, which holds the scheduling and actual performance facts. Organization context is supplied by ORG_ORGANIZATION_DEFINITIONS (ORGANIZATION_ID, ORGANIZATION_NAME, LEGAL_ENTITY), and item context by MTL_ITEM_FLEXFIELDS (ITEM_NUMBER, DESCRIPTION, PRIMARY_UOM_CODE). Calendar bucketing is derived from BOM_ORG_CAL_WEEKS_VIEW, which provides WEEK_START_DATE, NEXT_DATE, and SEQ_NUM per organization. Categorization is resolved through MTL_ITEM_CATEGORIES, MTL_DEFAULT_CATEGORY_SETS, and MTL_CATEGORIES_KFV. Security and general value resolution are inherited through HR_GENERAL and HR_SECURITY packages referenced by the underlying objects.

The joins are strictly correlated on ORGANIZATION_ID and INVENTORY_ITEM_ID, with a range predicate placing each SCHEDULE_DATE between WEEK_START_DATE and NEXT_DATE minus one day. Only rows where EXISTING_FLAG equals 1 are returned, and the category set is restricted to the functional area identifier 1, reflecting a specific category set scope.

Key Columns

• ORGANIZATION_ID / ORGANIZATION_NAME / LEGAL_ENTITY — the manufacturing organization and its owning legal entity.
• SCHEDULE_DATE — the date against which production was scheduled.
• WEEK_START_DATE / WEEK_END_DATE — calendar week boundaries derived from BOM_ORG_CAL_WEEKS_VIEW; WEEK_END_DATE is computed as NEXT_DATE - 1.
• SEQ_NUM — the calendar week sequence number.
• ITEM_NUMBER / DESCRIPTION / PRIMARY_UOM_CODE — item identification and unit of measure.
• CATEGORY_ID / CONCATENATED_SEGMENTS — the assigned category and its concatenated key flexfield value.
• SCHEDULE_QUANTITY / ACTUAL_QUANTITY — the planned quantity versus the quantity actually produced.

Common Use Cases and Queries

Typical use cases include weekly production attainment reporting, plan-versus-actual variance analysis by item or category, and data extraction into BI Publisher or OBIEE dashboards. A representative query filtering on the week end date is:

• SELECT organization_name, week_end_date, item_number, schedule_quantity, actual_quantity FROM wip_bis_perf_to_plan_v WHERE organization_id = :p_org AND week_end_date BETWEEN :p_start AND :p_end ORDER BY week_end_date, item_number;
• Aggregate attainment: SELECT week_end_date, catalog item, SUM(schedule_quantity), SUM(actual_quantity) FROM wip_bis_perf_to_plan_v GROUP BY week_end_date;

Because the view joins to HR security packages, accessible organizations may be restricted by responsibility, a consideration worth validating when results appear limited in multi-organization deployments.