Results for “net_quantity”
10 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
APPS.WIP_JOBS_RESERVATIONS_V is a Work in Process (WIP) reporting view that exposes discrete jobs eligible for material reservations. It is a filtered, read-only projection rather than a base table, and its purpose is to present only those jobs whose remaining available quantity justifies further reservation activity, or which are already linked to pending move-order/LPN supply. Because the view is owned by APPS and marked VALID in both 12.1.1 and 12.2.2, it is safe to reference from custom concurrent programs, BI Publisher reports, OAF pages, and integration extracts without concern for schema drift across these releases. The user search term start_quantity maps directly to one of the view's exposed columns, and it is central to the view's internal eligibility logic: the quantity remaining for reservation is computed as START_QUANTITY - QUANTITY_SCRAPPED - QUANTITY_COMPLETED and compared against the sum of existing primary reservations. The view therefore answers the operational question "which discrete jobs still have unreserved or partially reserved demand, or which have staged supply awaiting reservation?"
Underlying Base Objects
The view is defined over two synonyms and references additional objects within its inline subqueries. The dominant join is between WIP_DISCRETE_JOBS (aliased WDJ), which supplies job-level attributes including START_QUANTITY, and WIP_ENTITIES (WE), which supplies the job name and entity type, joined on WIP_ENTITY_ID. A correlated subquery aggregates WIP_RESERVATIONS_V to derive the sum of primary reserved quantities per job. A further set of EXISTS predicates interrogates MTL_TXN_REQUEST_LINES joined to WMS_LICENSE_PLATE_NUMBERS, restricted to undelivered lines (NVL(QUANTITY_DELIVERED,0)=0), LPN context 2, and line status other than 5, to identify jobs with pending LPN-based supply. The documented metadata also lists INV_CONVERT as a referenced object, reflecting shipped Oracle logic that may invoke conversion utilities. Note that the view does not expose move-order lines directly; it merely tests for their existence.
Key Columns
WIP_ENTITY_ID/WIP_ENTITY_NAME— The job identifier and its user-visible name; the primary keys for joining to other WIP and inventory views.ORGANIZATION_ID— The manufacturing organization owning the job; essential for multi-org secured queries.ENTITY_TYPE/JOB_TYPE— Distinguish standard versus non-standard jobs and their scheduling class.STATUS_TYPE— Job status code; the view restricts results to statuses 1, 3, 4, and 6, with stricter logic applied to non-status-4 jobs unless pending LPN supply exists.START_QUANTITY— The quantity the job was launched to build; the anchor value for the remaining-quantity calculation.NET_QUANTITY— The net planned quantity after yield and scrap considerations.PRIMARY_ITEM_ID— The assembly item being built; joins toMTL_SYSTEM_ITEMS_B.SCHEDULED_START_DATE/SCHEDULED_COMPLETION_DATE— Job schedule windows useful for date-bounded reporting.COMPLETION_SUBINVENTORY/COMPLETION_LOCATOR_ID— Destination for completions.BOM_REVISION,JOB_LOT_NUMBER,PROJECT_ID,TASK_ID,SERIALIZATION_START_OP— Supporting attributes for revision control, lot-tracked jobs, project accounting, and serialization.
Common Use Cases and Queries
Typical usage includes identifying jobs available for reservation, reconciling reserved versus remaining quantities, and driving move-order generation for LPN-enabled warehouses. A simple query filtered on the searched column might read:
SELECT wip_entity_name, organization_id, status_type, start_quantity, net_quantity FROM wip_jobs_reservations_v WHERE organization_id = :org AND status_type IN (1,3) ORDER BY scheduled_start_date;SELECT wip_entity_id, start_quantity FROM wip_jobs_reservations_v WHERE primary_item_id = :item AND start_quantity > 0;- Joining the view to
WIP_RESERVATIONS_Vto compare the view's implied remaining quantity against actual reservation records.
Because the view already applies complex eligibility filtering, developers should avoid re-implementing the START_QUANTITY arithmetic and instead treat the view as the authoritative source for reservation-eligible job lists.
-
Data for Jobs eligible for reservations
APPS.WIP_JOBS_RESERVATIONS_V·↳ INV_CONVERT·↳ MTL_TXN_REQUEST_LINES·↳ WIP_DISCRETE_JOBS·Explore WIP module →
-
Data for Jobs eligible for reservations
APPS.WIP_JOBS_RESERVATIONS_V·↳ INV_CONVERT·↳ MTL_TXN_REQUEST_LINES·↳ WIP_DISCRETE_JOBS·Explore WIP module →
-
Discrete jobs
-
Discrete jobs
-
View: WIP_DISCRETE_JOBS_V 12.2.2
Foreign-key data for WIP_DISCRETE_JOBS
APPS.WIP_DISCRETE_JOBS_V·↳ MFG_LOOKUPS·↳ MTL_KANBAN_CARDS·↳ MTL_SECONDARY_INVENTORIES·Explore WIP module →
-
Foreign-key data for WIP_JOB_SCHEDULE_INTERFACE
APPS.WIP_JOB_SCHEDULE_INTERFACE_V·↳ FND_USER·↳ HR_GENERAL·↳ HR_SECURITY·Explore WIP module →
-
View: WIP_DISCRETE_JOBS_V 12.1.1
Foreign-key data for WIP_DISCRETE_JOBS
APPS.WIP_DISCRETE_JOBS_V·↳ MFG_LOOKUPS·↳ MTL_KANBAN_CARDS·↳ MTL_SECONDARY_INVENTORIES·Explore WIP module →
-
Requests to create or modify jobs and schedules
-
Requests to create or modify jobs and schedules
-
Foreign-key data for WIP_JOB_SCHEDULE_INTERFACE
APPS.WIP_JOB_SCHEDULE_INTERFACE_V·↳ FND_USER·↳ HR_GENERAL·↳ HR_SECURITY·Explore WIP module →