Results for “allocation_id”

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

Overview

WIPBV_WIP_RESERVATIONS is a read-only view owned by the APPS schema in Oracle E-Business Suite, registered as VALID under the Work in Process (WIP) product family. It exposes shop-floor reservations of supply against discrete work order demand, specifically those reservations tied to sales order (SO) demand through the WIP_SO_ALLOCATIONS base table. The view filters records so that only rows with a non-null organization context ('_SEC:WIP_SO_ALLOCATIONS.ORGANIZATION_ID' IS NOT NULL) are returned, and it is explicitly defined WITH READ ONLY. This construction enforces multi-org security at the view layer and prevents any DML through the view.

The object is widely referenced in reporting and integration scenarios where users need to determine how much of a work order's quantity has been allocated to a sales order line, and how much of that allocation has actually been completed. The column name demand_source_header_id is a common search term because it provides the linkage between a WIP allocation and its driving demand document in the order management flow.

Underlying Base Objects

WIPBV_WIP_RESERVATIONS is defined over a single documented base object: the synonym WIP_SO_ALLOCATIONS. The view text selects ten columns directly from that synonym with no joins, aggregation, or derived expressions, so row counts and key values in the view mirror the underlying table exactly, subject only to the organization security predicate. Because the view performs no de-normalization, all transactional attributes such as creation/update audit columns are carried through unchanged. Consumers should therefore treat the view as a secured projection of WIP_SO_ALLOCATIONS rather than as an enriched reporting structure. Any joins to work order, sales order, or inventory tables must be supplied by the query author.

Key Columns

• ALLOCATION_ID — Primary identifier for the allocation record; the natural key for row-level retrieval and for joining back to WIP_SO_ALLOCATIONS.
• DEMAND_SOURCE_HEADER_ID — Identifies the originating demand document (typically the sales order header) that drives the reservation. This is the attribute most frequently used to trace allocations back to order management.
• WIP_ENTITY_ID — References the discrete work order (job) that is receiving the allocation; the principal join key to WIP_ENTITIES.
• ORGANIZATION_ID — The inventory organization context; also the column used by the view's security predicate.
• QUANTITY_ALLOCATED — The quantity of the work order reserved against the demand source.
• QUANTITY_COMPLETED — The portion of the allocated quantity that has been completed, enabling computation of open or remaining reservation quantity.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — Standard audit columns supporting change tracking and data lineage.

Common Use Cases and Queries

Typical uses include work order reservation reports, sales order supply/demand reconciliation, and inbound interfaces that need allocation quantities for a given job or organization.

SELECT allocation_id,
       wip_entity_id,
       organization_id,
       demand_source_header_id,
       quantity_allocated,
       quantity_completed,
       quantity_allocated - NVL(quantity_completed,0) AS open_quantity
FROM   apps.wipbv_wip_reservations
WHERE  organization_id = :org_id
AND    wip_entity_id  = :wip_entity_id;

To trace reservations by demand source — the scenario implied by the demand_source_header_id search — filter on that column directly:

SELECT demand_source_header_id,
       wip_entity_id,
       SUM(quantity_allocated) AS total_allocated,
       SUM(NVL(quantity_completed,0)) AS total_completed
FROM   apps.wipbv_wip_reservations
WHERE  organization_id = :org_id
GROUP  BY demand_source_header_id, wip_entity_id;

Because the view is read-only and security-filtered, queries may be embedded safely in concurrent programs and BI Publisher reports without risk of unintended writes.