Search Results pjm_borrow_paybacks




Overview
Explore in AI Chat

Overview

PJM_BORROW_PAYBACKS is a Project Manufacturing (PJM) table that records inter-project borrow/payback allocations in Oracle E-Business Suite 12.1.1 and 12.2.2. In project manufacturing environments, material issued to one project is sometimes physically consumed by another project before ownership is formally transferred. The borrow transaction captures the outward movement; the payback transaction captures the return or settlement. PJM_BORROW_PAYBACKS is the intersection record that ties a specific payback event back to the originating borrow event, preserving the audit trail required for project cost and quantity reconciliation.

The table resides in the PJM schema and is documented as VALID with 16 columns. Its heuristic Data Vault classification, mined from the foreign key structure, is a link table. This is a modeling suggestion: the object primarily resolves many-to-many relationships between transactions, projects, and tasks rather than storing descriptive attributes of a single business entity. Because it also carries transactional measures such as PAYBACK_QUANTITY, it functions as a link with limited satellite characteristics.

Key Information Stored

The composite primary key, PJM_BORROW_PAYBACKS_PK, is defined on PAYBACK_TRANSACTION_ID and BORROW_TRANSACTION_ID. A second unique index, PJM_BORROW_PAYBACKS_U1, is defined on the same two columns in reverse order (BORROW_TRANSACTION_ID, PAYBACK_TRANSACTION_ID) and serves as a documented business-key candidate.

Common Use Cases and Queries

Typical usage centers on reconciliation, audit, and cost transfer reporting. A project accountant may reconcile borrow-to-payback completeness to ensure no borrowed quantity remains outstanding. A manufacturing analyst may report payback volumes by lending and borrowing project pair.

  • Open borrow analysis: Join PJM_BORROW_TRANSACTIONS to PJM_BORROW_PAYBACKS on BORROW_TRANSACTION_ID and compare borrowed versus summed PAYBACK_QUANTITY to identify unreconciled quantities.
  • Project-to-project transfer reporting: Aggregate PAYBACK_QUANTITY grouped by BORROW_PROJECT_ID and LENDING_PROJECT_ID, resolving names via PA_PROJECTS_ALL.
  • Transaction trail audit: Join PAYBACK_TRANSACTION_ID to MTL_MATERIAL_TRANSACTIONS to trace the physical inventory movement for a given payback.
  • Concurrent program diagnostics: Filter by REQUEST_ID or PROGRAM_ID to isolate allocations created by a specific PJM concurrent process run.

Related Objects

  • PJM_BORROW_TRANSACTIONS — Parent table of the borrow side; joined via BORROW_TRANSACTION_ID.
  • MTL_MATERIAL_TRANSACTIONS — Inventory transaction source for the payback; joined via PAYBACK_TRANSACTION_ID.
  • PA_PROJECTS_ALL — Supplies borrowing and lending project definitions; joined via BORROW_PROJECT_ID and LENDING_PROJECT_ID.
  • PA_TASKS — Supplies borrowing and lending task definitions; joined via BORROW_TASK_ID and LENDING_TASK_ID.
  • MTL_TRANSACTION_ACCOUNTS — Distributes the accounting for the payback inventory transaction.
  • PJM_BORROW_PAYBACKS_PK / PJM_BORROW_PAYBACKS_U1 — Primary and unique indexes enforcing allocation uniqueness.

Because PJM_BORROW_PAYBACKS carries both transactional foreign keys and quantity measures, it should be treated as the authoritative junction for inter-project material settlement analysis in Project Manufacturing.