Search Results return_agreement_number

Overview

PNT_PAYMENT_TERMS_PKG is an Oracle Property Manager (PN) package in the APPS schema that provides the core data-maintenance layer for payment-term records stored in the PN_PAYMENT_TERMS_ALL table. Payment terms in Oracle Property Manager define the timing, amounts, and calculation logic used to generate payment schedules for leases, operating agreements, and other real-estate contracts. This package is classified as an OTHER API in the ETRM 12.2.2 metadata, meaning it is an internal utility package rather than a formally published public API. It supplies the standard insert, lock, update, and delete primitives used by Oracle Property Manager forms, along with business-validation routines that enforce consistency between payment terms, distributions, and approved schedules. It is a foundational dependency for several higher-level calculation packages, including PN_REC_CALC_PKG, PN_OPEX_TERMS_PKG, PN_VARIABLE_TERM_PKG, and PN_INDEX_AMOUNT_PKG. The package status is VALID in the APPS schema.

Key Procedures and Functions

• INSERT_ROW — Creates a new payment-term record in PN_PAYMENT_TERMS_ALL.
• LOCK_ROW — Acquires a row-level lock on an existing payment-term record to support multi-user form concurrency.
• UPDATE_ROW — Applies changes to an existing payment-term record.
• DELETE_ROW — Removes a payment-term record.
• MODIFY_ROW — Performs a combined update/modify operation used by maintenance flows.
• CHECK_PAYMENT_AMOUNTS — Validates that payment amounts associated with a term are internally consistent and permissible.
• CHECK_APPROVED_SCHEDULE_EXISTS — Verifies whether an approved payment schedule exists, guarding edits that would invalidate an approved schedule.
• CREATE_HIST_CORR_UPD — Writes a history/audit correction record when payment-term data is adjusted.
• UPDATE_VENDOR_AND_CUST — Propagates vendor and customer information associated with the payment term.
• RETURN_AGREEMENT_NUMBER — Returns the agreement number linked to the payment-term record.
• GET_SOURCE_MODULE_TYPE — Returns the source module type that originated the payment term, allowing callers to branch logic by originating application.

Parameter lists are not documented and should not be assumed; callers should inspect the live package specification.

Tables Accessed

The package reads and writes PN_PAYMENT_TERMS_ALL, its primary table. It also references PN_DISTRIBUTIONS, PN_DISTRIBUTIONS_ALL, PN_DISTRIBUTIONS_HISTORY, PN_DISTRIBUTIONS_HISTORY_S, PN_DISTRIBUTIONS_HISTORY_S1, and PN_DISTRIBUTIONS_S to reconcile payment terms against distribution and audit-history data. Lease and agreement context is drawn from PN_LEASES, PN_LEASES_ALL, PN_INDEX_LEASES_ALL, PN_INDEX_LEASE_PERIODS_ALL, and PN_OPEX_AGREEMENTS_ALL. Payment-item detail is validated against PN_PAYMENT_ITEMS and PN_PAYMENT_ITEMS_ALL, while OPEX estimated payments are handled through PN_OPEX_EST_PAYMENTS_ALL. All tables are accessed via APPS synonyms.

Usage Notes

PNT_PAYMENT_TERMS_PKG is invoked primarily from Oracle Property Manager payment-term maintenance forms and is called internally by PN_REC_CALC_PKG, PN_OPEX_TERMS_PKG, PN_VARIABLE_TERM_PKG, PN_INDEX_AMOUNT_PKG, PN_INDEX_EXCLUDE_TERM_V, and PN_PAYMENT_TERMS_V. Because it is an internal OTHER API, custom integrations should generally use the Property Manager public APIs and redirect rather than calling this package directly. Direct calls risk bypassing form-level validation logic and are unsupported across 12.1.1 and 12.2.2 upgrades.