Search Results pn_payment_schedules




Overview
Explore in AI Chat

Overview

APPS.PN_PAYMENT_SCHEDULES_V is a reporting and integration view within the Oracle E-Business Suite Property Manager (PN) module, exposing the payment schedule records that drive lease-related disbursement planning. Payment schedules represent the dated installments against which lease payments are approved, transferred, placed on hold, or processed through period-based accounting. In Oracle EBS 12.1.1 and 12.2.2, this view serves as the primary denormalized read interface for payment schedule data, joining the base schedule rows to their parent lease and to the FND_USER records of the approving and transferring users. Because it resolves user identifiers into user names and includes lease descriptors such as lease name, lease number, lease class code, and lease status, the view eliminates the need for report authors and interface developers to construct multi-table joins manually. It is commonly consumed by custom reports, outbound conversion programs, and diagnostic queries that require a complete, human-readable picture of a lease payment schedule.

Underlying Base Objects

The view is defined over three documented base objects, all referenced through APPS-owned synonyms:

  • PN_PAYMENT_SCHEDULES — the driving table (aliased ps), supplying the payment schedule identifier, schedule date, lease identifier, change identifier, payment status, approval and transfer details, period name, hold indicator, descriptive flexfield attributes, and organization identifier.
  • PN_LEASES_ALL — the parent lease table (aliased lease), supplying the lease name, lease number, lease class code, lease status, and general status.
  • FND_USER — joined twice (aliased fna and fnt) as outer joins to resolve APPROVED_BY_USER_ID and TRANSFERRED_BY_USER_ID into user names.

The join conditions relate the schedule to its lease on LEASE_ID, with the organization identifier compared using NVL(…, -99) on both sides to preserve rows where ORG_ID is null. Both user joins are outer joins, so schedules without an approving or transferring user remain visible.

Key Columns

Common Use Cases and Queries

Typical uses include payment schedule status reporting, approval and transfer auditing, hold analysis, and extracts feeding downstream payment processing. A representative query lists pending approved schedules for a lease:

  • SELECT payment_schedule_id, schedule_date, payment_status_lookup_code, user_approved_by, approval_date FROM apps.pn_payment_schedules_v WHERE lease_number = :lease_number AND payment_status_lookup_code = 'APPROVED' ORDER BY schedule_date;
  • SELECT lease_number, COUNT(*) schedules, SUM(CASE WHEN on_hold = 'Y' THEN 1 ELSE 0 END) on_hold_count FROM apps.pn_payment_schedules_v WHERE org_id = :org_id GROUP BY lease_number;
  • SELECT payment_schedule_id, period_name, user_transferred_by, transfer_date FROM apps.pn_payment_schedules_v WHERE transfer_date BETWEEN :start_date AND :end_date;

Because the view exposes descriptive flexfield attributes and audit columns, it also supports data-conversion validation and change-tracking reports across both 12.1.1 and 12.2.2 releases.