Results for “borrow_task_id”

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

Overview

The MRP_ITEM_BORROW_PAYBACK_QTY_V view is a PL/SQL-based reporting object owned by the APPS schema in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It belongs to the MRP (Master Scheduling/MRP) product family and is registered with a status of VALID. Its purpose is to expose item-level borrow/payback quantities associated with inter-project and inter-task material lending transactions, aggregated at the item, organization, project, task, and scheduled payback date level. The view is most relevant to planners and project-driven supply chain users who need a consolidated picture of outstanding borrowed quantities that are expected to be returned or "paid back."

The view is particularly significant because it surfaces the LENDING_PROJECT_ID column, which is the exact term the user searched for. In EBS project manufacturing and Oracle Project Manufacturing (PJM) flows, a borrowing transaction records both the borrowing side (BORROW_PROJECT_ID, BORROW_TASK_ID) and the lending side (LENDING_PROJECT_ID, LENDING_TASK_ID). This view makes those relationships queryable at the MRP item level, enabling supply/demand visibility for borrowed inventory that has not yet been returned.

Underlying Base Objects

According to the ETRM 12.2.2 metadata, the view is defined over the following objects:

• PJM_BORROW_TRANSACTIONS (SYNONYM) — the transactional source of borrow/payback records; the view filters on OUTSTANDING_QUANTITY > 0 and aggregates the outstanding quantity.
• MRP_SYSTEM_ITEMS (SYNONYM) — provides the item master context (INVENTORY_ITEM_ID, ORGANIZATION_ID, COMPILE_DESIGNATOR) and applies the NVL(EFFECTIVITY_CONTROL,1) = 1 filter.
• MRP_PLAN_ORGANIZATIONS_V (VIEW) — supplies planned organization data used to align the item's organization with the planned organization.

The joins bind inventory item, organization, and compile designator across these sources, ensuring the view reports only for planned organizations and effective items.

Key Columns

• COMPILE_DESIGNATOR — identifies the MRP plan or designator context.
• INVENTORY_ITEM_ID — the item for which borrow/payback is tracked.
• ORGANIZATION_ID — the item's organization from MRP_SYSTEM_ITEMS.
• OWNING_ORGANIZATION_ID — the planned/owning organization derived from MRP_PLAN_ORGANIZATIONS_V.
• PAYBACK_DATE — the scheduled payback date (PBT.SCHEDULED_PAYBACK_DATE), used for time-phased aggregation.
• BORROW_PROJECT_ID / BORROW_TASK_ID — the project and task that borrowed the material.
• LENDING_PROJECT_ID / LENDING_TASK_ID — the project and task that supplied (lent) the material. These are the columns most relevant to users searching on "lending_project_id."
• QUANTITY — SUM of OUTSTANDING_QUANTITY, representing the total unrecovered borrowed quantity.

Common Use Cases and Queries

Typical uses include outstanding borrow/payback reporting, planned organization supply visibility, and cross-project material reconciliation. A representative query filtering by lending project is:

SELECT inventory_item_id, organization_id, lending_project_id, lending_task_id, borrow_project_id, payback_date, quantity FROM apps.mrp_item_borrow_payback_qty_v WHERE lending_project_id = :p_lending_project_id ORDER BY payback_date;

Planners may also aggregate quantity by item and organization, or filter by payback_date to identify near-term returns. Because the view already restricts to OUTSTANDING_QUANTITY > 0, results reflect only open obligations, making it directly suitable for dashboards, concurrent reports, and integration extracts in both 12.1.1 and 12.2.2.