Search Results get_index_id

Overview

PN_INDEX_RENT_UTILS is a public PL/SQL utility package owned by APPS in the Oracle Property Manager (PN) module of Oracle E-Business Suite. It is compiled with AUTHID CURRENT_USER, meaning that the package executes with the privileges of the calling schema rather than the definer, and its runtime behavior is therefore governed by the invoking user's grants on the underlying PN tables. In 12.1.1 and 12.2.2 the package is classified as an OTHER API, not as a formal public interface, so it should be treated as internal infrastructure rather than a supported integration point.

The package's business purpose is to resolve the identifiers and reference values required to create or update index rent records — the rent adjustments that Property Manager applies to a lease when an inflation or price index changes. Callers search for "create_index_rent" because that literal operation name appears as the default value of the p_operation parameter on several of the resolution routines. It is not a standalone procedure; it is a context label that tells the package which validations and lookups to apply. The two packages that reference PN_INDEX_RENT_UTILS rely on it to translate human-readable business keys — lease names and numbers, index names, location codes, lookup meanings — into the surrogate primary keys needed by the index rent DML.

Key Procedures and Functions

• GET_LEASE_ID — Resolves a lease identifier from a lease name and lease number within a given operating unit, and returns the lease class code, commencement, termination, execution, and extension end dates for the located lease. Defaults to the CREATE_INDEX_RENT operation.
• GET_LOCATION_ID — Returns the location identifier for a location code on a specified lease.
• GET_INDEX_ID — Returns the index identifier for a supplied index name, typically used when linking a rent adjustment to an inflation index definition.
• GET_INDEX_LEASE_ID — Resolves the combination of index lease identifier, lease identifier, org identifier, and index identifier from an index lease number. Its default operation is UPDATE_INDEX_RENT, reflecting its use in the amendment path rather than the creation path.
• GET_USER_ID — Resolves an FND_USER identifier for audit and attribute attribution.
• GET_CURRENCY_CODE — Validates or derives a currency code, drawing on currency and conversion type setup.
• GET_LOOKUP_CODE — Retrieves a lookup code from a lookup meaning and lookup type, with a default operation of CREATE_RENT_INDEX.
• GET_INCREASE_ON — Determines the basis on which the index increase is applied, feeding the rent calculation logic.
• GET_TERM_TEMPLATE_ID — Returns a term template identifier for use in generating or validating lease terms.

Consistent with the source header, each routine exposes a standard set of IN parameters, NOCOPY OUT or IN OUT parameters, and an x_return_status OUT parameter for error signaling.

Tables Accessed

The package performs its resolution work against APPS synonyms rather than directly against the PN schema. Core lease and index data is read from PN_LEASES_ALL, PN_LEASE_DETAILS_ALL, PN_INDEX_LEASES_ALL, PN_INDEX_HISTORY_HEADERS, and PN_TENANCIES_ALL. Location resolution uses PN_LOCATIONS_ALL. Payment term and term template lookups use PN_PAYMENT_TERMS_ALL and PN_TERM_TEMPLATES_ALL. Currency validation reads PN_CURRENCIES and GL_DAILY_CONVERSION_TYPES; user resolution reads FND_USER. The return types are semantically compatible with the package constants G_PN_MISS_NUM, G_PN_MISS_DATE, and G_PN_MISS_CHAR, which mark unresolved numeric, date, and character values respectively.

Usage Notes

PN_INDEX_RENT_UTILS is invoked from Property Manager forms during index rent entry and amendment, from concurrent programs that generate index rent adjustments in bulk, and from the two dependent packages identified in the ETRM metadata. Custom code should avoid calling it directly: the package is not declared as a public API, the cursor and exception behavior is subject to change across 12.1.1 and 12.2.2, and callers must handle x_return_status on every invocation. Where a supported interface exists for index rent creation in Property Manager, that interface should be preferred over this utility package.