Search Results pjm_borrow_transactions




Overview
Explore in AI Chat

Overview

PJM_BORROW_TRANSACTIONS is a Project Manufacturing (PJM) transaction table that records inter-project borrow transactions in Oracle E-Business Suite 12.1.1 and 12.2.2. In Project Manufacturing environments, one project (the lending project) may transfer on-hand material to another project (the borrowing project) without physically moving inventory between organizations. Each row in PJM_BORROW_TRANSACTIONS captures a single borrow event, identifying the lending project and task, the borrowing project and task, the inventory item, the organization, and the quantities involved. The table is owned by the PJM schema and is documented as VALID in the ETRM repository.

The table functions as the header for a borrow-and-payback lifecycle. It is created when material is borrowed from a lending project and is later reconciled by corresponding rows in PJM_BORROW_PAYBACKS, which reference back to this table through BORROW_TRANSACTION_ID. From a Data Vault modeling perspective (heuristic classification derived from the foreign key structure), PJM_BORROW_TRANSACTIONS is satellite-leaning — it holds descriptive and quantitative attributes about a borrow event while linking to MTL_MATERIAL_TRANSACTIONS, PA_PROJECTS_ALL, PA_TASKS, MTL_SYSTEM_ITEMS_B, and MTL_ITEM_REVISIONS_B. The borrow event itself can therefore be viewed as a link between project, task, item, and inventory transaction hubs.

Key Information Stored

The table contains 21 documented columns. The most significant include:

Common Use Cases and Queries

Typical use cases include reconciling outstanding borrow balances, reporting material borrowed between projects, and aging open borrows by scheduled payback date. A representative query joining to PA_PROJECTS_ALL and MTL_SYSTEM_ITEMS_B follows:

SELECT bt.borrow_transaction_id,
       bp.segment1  AS borrow_project,
       lp.segment1  AS lending_project,
       msib.segment1 AS item,
       bt.loan_quantity,
       bt.outstanding_quantity,
       bt.loan_date,
       bt.scheduled_payback_date
FROM   pjm.pjm_borrow_transactions bt,
       pa.pa_projects_all        bp,
       pa.pa_projects_all        lp,
       mtl.mtl_system_items_b    msib
WHERE  bt.borrow_project_id  = bp.project_id
AND    bt.lending_project_id = lp.project_id
AND    bt.inventory_item_id  = msib.inventory_item_id
AND    bt.organization_id    = msib.organization_id
AND    bt.outstanding_quantity > 0;

To trace repayment activity, join PJM_BORROW_PAYBACKS on BORROW_TRANSACTION_ID. For transaction-level drill-down, join MTL_MATERIAL_TRANSACTIONS on the same column. Reporting against OUTSTANDING_QUANTITY and SCHEDULED_PAYBACK_DATE supports aging analysis.

Related Objects

  • PJM_BORROW_PAYBACKS — Child table; joins on BORROW_TRANSACTION_ID and records repayment of a borrow event.
  • MTL_MATERIAL_TRANSACTIONS — Links the borrow to the underlying inventory material transaction via BORROW_TRANSACTION_ID.
  • PA_PROJECTS_ALL — Provides project descriptions for both BORROW_PROJECT_ID and LENDING_PROJECT_ID.
  • PA_TASKS — Provides task details for BORROW_TASK_ID and LENDING_TASK_ID.
  • MTL_SYSTEM_ITEMS_B — Supplies the item definition through INVENTORY_ITEM_ID and ORGANIZATION_ID.
  • MTL_ITEM_REVISIONS_B — Supplies the revision definition through INVENTORY_ITEM_ID, ORGANIZATION_ID, and REVISION.

These relationships make PJM_BORROW_TRANSACTIONS the central reference point for inter-project borrow inquiries in Project Manufacturing.