Results for “mrp_unit_payback_qty_v”

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

Overview

MRP_UNIT_PAYBACK_QTY_V is an APPS-owned view in Oracle E-Business Suite (validated in 12.1.1 and 12.2.2) that belongs to the Master Scheduling/MRP product family. It exposes unit-level payback information associated with project borrow transactions, aggregating serialized end-item units that have been returned against outstanding borrow obligations. In practice, the view answers a narrow but operationally significant question: for a given borrow transaction on a serialized, unit-effective item, how many individual end units have been scheduled or accounted for as paybacks against a specific payback date and project/task combination.

Its role is primarily analytical and reporting-oriented. It is not a transactional entry view; rather it consolidates data drawn from project manufacturing (PJM) borrow and payback records, inventory serial number and unit transaction data, and planning item/organization definitions. Because it links borrow transactions to their associated paybacks at the serialized unit granularity, it supports reconciliation of lending and borrowing projects and helps planners understand remaining unit-level obligations. The view is also relevant when users search under the term pjm_borrow_paybacks, since the PJM_BORROW_PAYBACKS table is a core member of its join set.

Underlying Base Objects

The view is defined over the following documented base objects:

• PJM_BORROW_TRANSACTIONS — the header-level borrow record, supplying outstanding quantity, project/task, and scheduled payback date.
• PJM_BORROW_PAYBACKS — the payback linkage, connecting a payback transaction back to its originating borrow transaction.
• MTL_SERIAL_NUMBERS — provides the serialized unit identity and end-item unit number.
• MTL_UNIT_TRANSACTIONS — associates serial numbers with inventory transactions and organizations.
• MRP_SYSTEM_ITEMS — the planning item definition, filtered on effectivity control for unit-effective items.
• MRP_PLAN_ORGANIZATIONS_V — a view supplying planned organization context and the compile designator.

The joins progress from borrow header, through paybacks, to unit transactions matched on serial number and item, then to the serial number master and planning item/organization definitions. Only borrow transactions with OUTSTANDING_QUANTITY greater than zero and items under unit effectivity control (NVL(EFFECTIVITY_CONTROL,1)=2) qualify, and results are grouped by item, organization, borrow transaction, payback date, project/task, and end-item unit number.

Key Columns

• COMPILE_DESIGNATOR — planning compile identifier linking the record to a plan/organization set.
• INVENTORY_ITEM_ID / ORGANIZATION_ID — the item and owning organization of the borrow.
• OWNING_ORG_ID — the planned organization resolved via MRP_PLAN_ORGANIZATIONS_V.
• BORROW_TRANSACTION_ID — identifier of the originating borrow transaction.
• PAYBACK_DATE — the scheduled payback date for the obligation.
• BORROW_PROJECT_ID / BORROW_TASK_ID — the project and task receiving the borrowed units.
• LENDING_PROJECT_ID / LENDING_TASK_ID — the project and task supplying the units.
• END_ITEM_UNIT_NUMBER — the serialized end-item unit identifier.
• QUANTITY — the summed count (SUM(1)) of matched unit records.

Common Use Cases and Queries

Typical scenarios include reconciling outstanding borrows by project/task, verifying scheduled payback volumes by date, and auditing serialized unit returns. A representative query follows:

• Outstanding unit paybacks for an item/organization:

SELECT borrow_project_id, borrow_task_id, lending_project_id, payback_date, end_item_unit_number, quantity FROM apps.mrp_unit_payback_qty_v WHERE inventory_item_id = :item_id AND organization_id = :org_id ORDER BY payback_date;

• Aggregate scheduled payback quantity by date:

SELECT payback_date, SUM(quantity) FROM apps.mrp_unit_payback_qty_v GROUP BY payback_date ORDER BY payback_date;

Because the view filters on outstanding quantity and unit effectivity, results represent only open, unit-controlled obligations, making it suitable for planning dashboards and reconciliation reports tied to the pjm_borrow_paybacks process.