Search Results lease_class_code




Overview
Explore in AI Chat

Overview

PN_PAYMENT_SCHEDULES_V is a form-driven database view owned by the APPS schema within the Property Manager (PN) module of Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to present payment schedule information for data entry through an EBS form. Because it is a view rather than a base table, it does not store data itself; instead, it projects and decorates rows from the underlying payment schedule entity so that the form layer can display, validate, and update the same records. The view is listed with VALID status and is registered in ETRM as a reporting and integration access point to payment schedule data.

For users searching on transferred_by_user_id, the view is significant because it exposes both the raw foreign key column TRANSFERRED_BY_USER_ID and a resolved display value USER_TRANSFERRED_BY, obtained by an outer join to FND_USER. This dual exposure lets reporting tools reference the numeric user identifier while forms and reports can display the human-readable user name without additional lookups.

Underlying Base Objects

The view joins three documented base objects, each referenced through public synonyms in the APPS schema:

  • PN_PAYMENT_SCHEDULES (alias PS) — the primary transactional source, supplying the payment schedule identifier, schedule date, status, approval and transfer audit columns, descriptive flexfield attributes, and ORG_ID.
  • PN_LEASES_ALL (alias LEASE) — joined on LEASE_ID to supply lease context such as LEASE_NAME, LEASE_NUMBER, and LEASE_CLASS_CODE. The organization comparison uses NVL on both sides of ORG_ID with a sentinel of -99, allowing records where either organization is null to still match.
  • FND_USER (aliases FNA and FNT) — joined twice using outer joins. FNA resolves APPROVED_BY_USER_ID to USER_APPROVED_BY, and FNT resolves TRANSFERRED_BY_USER_ID to USER_TRANSFERRED_BY. The outer (+) syntax ensures that payment schedules without an assigned approver or transferrer remain visible.

The use of ROWID aliased as ROW_ID indicates the view is designed to be updatable for the payment schedule columns, which is consistent with its stated role as a data entry form view.

Key Columns

Common Use Cases and Queries

Typical uses include auditing who transferred payment schedules, reporting outstanding schedules by lease, and integrating payment schedule status into downstream processes. A representative query filtering on the searched column:

SELECT payment_schedule_id, lease_number, schedule_date, period_name, user_transferred_by, transfer_date
FROM apps.pn_payment_schedules_v
WHERE transferred_by_user_id = :user_id
AND org_id = :org_id;

To list all schedules pending transfer:

SELECT lease_number, schedule_date, payment_status_lookup_code, on_hold
FROM apps.pn_payment_schedules_v
WHERE transfer_date IS NULL
AND on_hold = 'N';

Analysts should apply ORG_ID predicates consistent with the NVL-based join logic to preserve multi-org security and must account for null approver or transferrer values, since the FND_USER joins are outer.