Results for “mrp_unit_borrow_qty_v”

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

Overview

The MRP_UNIT_BORROW_QTY_V view is an APPS-owned database object in Oracle E-Business Suite, delivered under the Master Scheduling/MRP (MRP) product family. It is classified as a VIEW, holds a VALID status in the ETRM data dictionary, and is available in both the 12.1.1 and 12.2.2 releases. The object is defined in the APPS schema and is documented as Oracle Proprietary, Confidential Information.

The view aggregates unit-level borrow activity for serialized inventory and exposes the identifier most commonly searched by users, BORROW_TRANSACTION_ID, together with its associated project, task, and payback context. Its principal purpose is to provide planning and project-driven supply chain reporting with a consolidated picture of the quantity of units currently on loan, rather than their full transactional history. The presence of the OUTSTANDING_QUANTITY > 0 filter in the view definition indicates the view is intentionally restricted to borrow transactions that remain open, meaning the borrowed units have not yet been returned or fully paid back.

As a view rather than a table, it carries no stored data and inherits its content dynamically from the base objects at query time. This makes it suitable for ad-hoc reporting, custom concurrent programs, Oracle Discoverer or BI Publisher data models, and integration extracts where a snapshot of outstanding unit borrowings is required.

Underlying Base Objects

Per the documented metadata, the view is defined over the following referenced base objects:

• PJM_BORROW_TRANSACTIONS (synonym) — the primary transactional source, supplying BORROW_TRANSACTION_ID, SCHEDULED_PAYBACK_DATE, BORROW_PROJECT_ID, BORROW_TASK_ID, LENDING_PROJECT_ID, LENDING_TASK_ID, ORGANIZATION_ID, INVENTORY_ITEM_ID, and OUTSTANDING_QUANTITY.
• MTL_SERIAL_NUMBERS (synonym) — provides serialized unit context, including SERIAL_NUMBER and END_ITEM_UNIT_NUMBER.
• MTL_UNIT_TRANSACTIONS (synonym) — links serial numbers to inventory transactions via TRANSACTION_ID and SERIAL_NUMBER.
• MRP_SYSTEM_ITEMS (synonym) — supplies COMPILE_DESIGNATOR, INVENTORY_ITEM_ID, ORGANIZATION_ID, and the EFFECTIVITY_CONTROL attribute used to restrict rows to effectivity-controlled items (EFFECTIVITY_CONTROL = 2).
• MRP_PLAN_ORGANIZATIONS_V (view) — supplies the planned organization context and is joined on COMPILE_DESIGNATOR and ORGANIZATION_ID.

The join path begins at the serial numbers, connects to unit transactions, then to borrow transactions, and finally restricts by planned item and organization definitions. The result set is aggregated with GROUP BY and SUM(1), so each returned row represents a counted unit.

Key Columns

• COMPILE_DESIGNATOR — the plan identifier under which the item and organization are compiled.
• INVENTORY_ITEM_ID and ORGANIZATION_ID — identify the item and its owning organization for the borrowed unit.
• OWNING_ORG_ID — the owning organization, sourced from the planned organization join.
• BORROW_TRANSACTION_ID — the unique identifier of the borrow transaction; the key searchable attribute of this view.
• PAYBACK_DATE — the scheduled date on which the borrowed unit is expected to be returned (SCHEDULED_PAYBACK_DATE).
• BORROW_PROJECT_ID / BORROW_TASK_ID — the project and task that received the borrowed unit.
• LENDING_PROJECT_ID / LENDING_TASK_ID — the project and task from which the unit was lent.
• END_ITEM_UNIT_NUMBER — the end-item unit number associated with the serialized unit.
• QUANTITY — the aggregated count (SUM(1)) of outstanding units for the grouping.

Common Use Cases and Queries

The view is typically queried to identify outstanding borrow transactions by project, by item, or by serialized end item, and to track payback exposure across organizations.

• Locating a specific borrow transaction by its identifier.
• Reporting outstanding borrow quantities by lending or borrowing project and task.
• Monitoring scheduled payback dates for units still on loan.
• Feeding project-driven supply chain or planning dashboards.
• Reconciling serialized borrow activity against inventory transactions.

Representative query by borrow transaction identifier:

SELECT borrow_transaction_id, inventory_item_id, organization_id, borrow_project_id, borrow_task_id, lending_project_id, lending_task_id, payback_date, end_item_unit_number, quantity FROM apps.mrp_unit_borrow_qty_v WHERE borrow_transaction_id = :borrow_transaction_id;

Aggregate exposure by lending project:

SELECT lending_project_id, lending_task_id, SUM(quantity) outstanding_units FROM apps.mrp_unit_borrow_qty_v GROUP BY lending_project_id, lending_task_id ORDER BY outstanding_units DESC;

Because the view restricts rows to transactions with outstanding quantity greater than zero and effectivity-controlled items, returned figures represent open borrow positions only and should not be interpreted as cumulative historical borrowing.