Search Results aging_days

Overview

APPS.PJM_BORROW_PAYBACK_DETAIL_V is a supplementary view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is registered under FND Design Data as PJM.PJM_BORROW_PAYBACK_DETAIL_V and is currently VALID. Its purpose, as stated in the Oracle ETRM metadata, is to simplify forms coding for the Project Manufacturing (PJM) borrow and payback functionality. The view presents denormalized borrow/payback transaction detail — combining loan quantities, outstanding balances, payback quantities, and aging information into a single queryable structure.

Because it is a supplementary forms-support view, Oracle explicitly warns that it should not be queried or altered as a supported interface: its definition may change dramatically across minor or major releases. It is therefore suitable for read-only reporting and diagnostic investigation, not for programmatic dependency.

Underlying Base Objects

The view is defined over the following documented objects:

• APPS.PJM_BORROW_PAYBACKS — the core borrow/payback header or detail table holding payback and scheduled date information.
• APPS.PJM_BORROW_TRANSACTIONS — the borrow transaction records linking borrowing and lending projects/tasks.
• APPS.MTL_MATERIAL_TRANSACTIONS — the inventory transaction that physically moves the borrowed material.
• APPS.MTL_TRANSACTION_TYPES — the transaction type definition used to derive transaction type name and display values.

These are referenced as SYNONYM objects within the APPS schema. Notably, APPS.PJM_BORROW_PAYBACK_DETAIL_V is not referenced by any other database object, confirming its leaf position in the dependency tree. It does not expose an org-level filter through a base table join in the documented query text, so multi-org context should be applied explicitly.

Key Columns

The view exposes 18 columns. The most significant include:

• ORGANIZATION_ID — inventory organization owning the transaction.
• INVENTORY_ITEM_ID and REVISION — the borrowed item and its revision.
• BORROW_PROJECT_ID / BORROW_TASK_ID — the project and task receiving the borrowed material.
• LENDING_PROJECT_ID / LENDING_TASK_ID — the project and task supplying the material.
• TRANSACTION_ID / BORROW_TRANSACTION_ID — identifiers for the transaction and its originating borrow transaction.
• TRANSACTION_DATE, TRANSACTION_TYPE_ID, TRANSACTION_TYPE_NAME, TRANSACTION_TYPE_DISP — transaction timing and type descriptors.
• LOAN_QUANTITY, OUTSTANDING_QUANTITY, PAYBACK_QUANTITY — the quantitative lifecycle of the borrowed quantity.
• SCHEDULED_PAYBACK_DATE — the due date for returning the borrowed material.
• AGING_DAYS — the age of the borrow, which is the column most relevant to the user's search.

Common Use Cases and Queries

AGING_DAYS is the central metric for aging reports on borrowed material that remains outstanding. Analysts use it to identify borrows exceeding a policy threshold, prioritize payback, and reconcile inter-project balances.

Sample query identifying over-aged borrows:

• SELECT organization_id, inventory_item_id, borrow_project_id, lending_project_id, loan_quantity, outstanding_quantity, scheduled_payback_date, aging_days FROM apps.pjm_borrow_payback_detail_v WHERE outstanding_quantity > 0 AND aging_days > 90 ORDER BY aging_days DESC;

Additional practical queries include aggregating outstanding quantity by lending project to expose exposure, and comparing SCHEDULED_PAYBACK_DATE against the current date to flag overdue obligations. Because the view is unsupported for direct interrogation, queries should be confined to read-only reporting, joined carefully to MTL_SYSTEM_ITEMS_VL for item descriptions, and revalidated after any EBS patch or upgrade.