Results for “get_ap_payment_term”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.PN_INDEX_LEASE_COMMON_PKG is a stored PL/SQL package body in the Oracle E-Business Suite Property Manager (PN) module. Its documented status is VALID and it resides in the APPS schema. The package provides the common, shared program logic that supports indexed lease processing — the mechanism by which lease payment terms and payment schedules are periodically escalated or adjusted based on an index (such as a consumer price index). Because indexing logic is required from several entry points within the Property Manager application, this package centralizes the reusable validation, retrieval, logging, and maintenance routines so that index lease processing behaves consistently across concurrent programs, forms, and dependent packages.

The ETRM classification of this object is OTHER, and it is documented as exposing 45 procedures and functions. It is referenced by eight other packages, confirming that it acts as a shared service layer rather than a standalone program. Its dependency footprint spans both Property Manager base tables and Oracle Payables, Oracle Receivables, and HR/PA reference objects, reflecting the fact that index lease processing crosses the lease, payment, and accounting boundaries.

Key Procedures and Functions

The documented routines fall into several functional groups. Validation routines include CHK_FOR_APPROVED_INDEX_PERIODS, CHK_FOR_PAYMENT_REQD_FIELDS, CHK_FOR_EXPORTED_ITEMS, FIND_IF_PERIOD_EXISTS, FIND_IF_TERM_EXISTS, FIND_IF_NORM_TERM_EXISTS, and FIND_IF_TEMPLATE_USED, which confirm the state of index periods, payment terms, and templates before processing proceeds. Retrieval routines include GET_INDEX_LEASE, GET_INDEX_PERIOD, GET_INDEX_START_END_DATES, GET_INDEX_DETAILS, GET_INDEX_PERIOD_DETAILS, and GET_TERM_STATUS, which return lease, period, and date information to callers.

Reference-data lookups are provided by GET_AR_PAYMENT_TERM, GET_AP_PAYMENT_TERM, and GET_AR_TRX_TYPE. Maintenance routines include DELETE_INDEX_PAYMENT_TERM and GET_LEASE_CHANGE_ID. Diagnostic and output routines include PUT_LOG and PUT_OUTPUT, both built on the FND_FILE and FND_API utilities for concurrent program logging and report output.

Tables Accessed

The package operates primarily against Property Manager base and interface tables, including PN_INDEX_LEASES_ALL, PN_INDEX_LEASE_PERIODS_ALL, PN_INDEX_EXCLUDE_TERM_ALL, PN_INDEX_HISTORY_HEADERS, PN_INDEX_HISTORY_LINES, PN_LEASES_ALL, PN_LEASE_CHANGES_ALL, PN_LEASE_DETAILS_ALL, PN_LOCATIONS_ALL, PN_PAYMENT_ITEMS_ALL, PN_PAYMENT_SCHEDULES_ALL, PN_PAYMENT_TERMS_ALL, and PN_TERM_TEMPLATES_ALL. These support reading and writing index lease definitions, periods, history, and payment terms.

• PN_INDEX_LEASES_ALL, PN_INDEX_LEASE_PERIODS_ALL, PN_INDEX_EXCLUDE_TERM_ALL — index lease headers, periods, and excluded terms.
• PN_INDEX_HISTORY_HEADERS, PN_INDEX_HISTORY_LINES — audit history of index processing.
• PN_LEASES_ALL, PN_LEASE_CHANGES_ALL, PN_LEASE_DETAILS_ALL, PN_LOCATIONS_ALL — core lease data.
• PN_PAYMENT_ITEMS_ALL, PN_PAYMENT_SCHEDULES_ALL, PN_PAYMENT_TERMS_ALL, PN_TERM_TEMPLATES_ALL — payment terms and schedules.
• AP_TERMS, AP_DISTRIBUTION_SETS_ALL, AR_RECEIPT_METHODS, RA_TERMS, RA_CUST_TRX_TYPES_ALL, RA_RULES, RA_SALESREPS, PO_HEADERS_ALL — cross-module reference data used to resolve terms and transaction types.
• PA_PROJECTS_ALL, PA_ORGANIZATIONS_EXPEND_V, HR_ORGANIZATION_UNITS, FND_USER — project, organization, and user context.

Usage Notes

This package is typically invoked indirectly. Because it is referenced by eight other packages, including PN_INDEX_AMOUNT_PKG and PNP_DEBUG_PKG, it functions as a utility layer called during index lease generation and adjustment concurrent programs, and from Property Manager forms that maintain index lease terms. The presence of PUT_LOG and PUT_OUTPUT indicates it is designed to be driven from concurrent program execution, writing to the standard FND log and output files. Custom code should call the documented procedures rather than manipulate the underlying PN index tables directly, preserving the validation and history logic required for consistent index lease processing in both Oracle EBS 12.1.1 and 12.2.2.