Search Results lending_task_number




Overview
Explore in AI Chat

Overview

APPS.PJM_BORROW_PAYBACK_SUMMARY_V is a reporting view in the Oracle EBS Projects and Cost Management modules that consolidates borrow and payback activity between lending and borrowing project/task combinations. It aggregates outstanding quantities recorded in the PJM_BORROW_TRANSACTIONS table and presents them alongside project, task, cost group, and aging bucket information derived from the transaction loan dates. The view is primarily used in the context of inter-project material transfers, where one project borrows inventory from another and later returns (pays back) the borrowed quantity.

The view's central purpose is to summarize outstanding borrow quantities grouped by organization, inventory item, revision, borrowing and lending project/task, and the cost groups assigned to each side of the transaction. It also computes aging indicators based on the difference between the system date and the loan date, divided by the package-level BUCKET_SIZE constant defined in PJM_BORROW_PAYBACK. This provides a bucketed view of how long borrowed inventory has remained outstanding, which supports cost allocation, reconciliation, and payback prioritization reporting.

Underlying Base Objects

According to the documented ETRM metadata, the view references the following base objects:

  • CST_COST_GROUPS (SYNONYM) — joined twice, as CG1 and CG2, to resolve the cost group for the borrowing project and the lending project respectively.
  • PJM_BORROW_TRANSACTIONS (SYNONYM) — the primary transactional source (aliased PBT) supplying outstanding quantities, loan dates, item, revision, organization, and project/task identifiers.
  • PJM_PROJECT_PARAMETERS (SYNONYM) — joined twice (PP1 and PP2) to link the borrowing and lending projects to their costing group assignments.
  • PJM_PROJECT (PACKAGE) — supplies the ALL_PROJ_IDTONUM, ALL_PROJ_IDTONAME, ALL_TASK_IDTONUM, and ALL_TASK_IDTONAME functions used to translate internal project and task IDs into descriptive numbers and names.
  • PJM_BORROW_PAYBACK (PACKAGE) — provides the BUCKET_SIZE constant used in the aging calculations.

The join logic requires that both the borrowing and lending project parameters match at the same organization ID as the borrow transaction, and cost groups are resolved using NVL(PP.COSTING_GROUP_ID, 1), defaulting to cost group ID 1 when no explicit costing group is assigned.

Key Columns

  • ORGANIZATION_ID — the inventory organization in which the borrow transaction occurred.
  • INVENTORY_ITEM_ID and REVISION — the item and revision being borrowed.
  • BORROW_PROJECT_ID / BORROW_TASK_ID — internal identifiers for the borrowing project and task, alongside their translated project number and name (via PJM_PROJECT functions) and the associated cost group (CG1.COST_GROUP_ID, CG1.COST_GROUP).
  • LENDING_PROJECT_ID / LENDING_TASK_ID — corresponding identifiers, translated names, and cost group (CG2) for the lending side.
  • SUM(OUTSTANDING_QUANTITY) — the aggregated quantity still not paid back.
  • Four aging bucket columns — SUM expressions using TRUNC((SYSDATE - LOAN_DATE - 1) / BUCKET_SIZE) to classify outstanding quantities into buckets prior to bucket 1, exactly bucket 1, exactly bucket 2, and beyond bucket 2.

Common Use Cases and Queries

Because the user searched for "cost_group," the most relevant use cases involve reporting outstanding borrow balances broken down by the cost groups of the borrowing and lending projects. Typical queries include cost group verification for inter-project borrow reconciliation, identifying aged outstanding borrow quantities per cost group, and driving payback processing.

Sample query by cost group:

SELECT organization_id, inventory_item_id, borrow_project_id, lending_project_id, cost_group_id, cost_group, SUM(outstanding_quantity) FROM apps.pjm_borrow_payback_summary_v GROUP BY organization_id, inventory_item_id, borrow_project_id, lending_project_id, cost_group_id, cost_group;

A second common pattern filters by a specific cost group or project to review aging: SELECT borrow_project_id, lending_project_id, cost_group, outstanding_quantity, aging_bucket_1 FROM apps.pjm_borrow_payback_summary_v WHERE cost_group = :p_cost_group;

The view is typically consumed by custom reports, cost accountants reconciling inter-project borrow activity, and integration routines feeding downstream cost allocation or inventory valuation processes.