Search Results null_param

Overview

APPS.PN_INDEX_RENT_PUB is the public application programming interface for the Oracle E-Business Suite Property Manager (PN) module, responsible for the creation and maintenance of index rent records. Index rent refers to the periodic rent adjustment mechanism in which lease payments are recalculated based on a published index (for example, a consumer price index or a similar inflationary benchmark) applied to a base rent amount. The package serves as the outer, publicly callable layer of the index rent API, delegating all substantive business logic to the corresponding private package, PN_INDEX_RENT_PVT. This public/private split is the standard Oracle EBS API architecture: the private package encapsulates validation, defaulting, and DML, while the public package enforces the published interface contract, performs savepoint management, and handles standard message stack initialization.

The package body is versioned with the header identifier PNIRPUBB.pls, revision 120.2, dated 09-MAY-2011. It is owned by APPS and classified as a PUB API, meaning it is a supported entry point for external and internal callers. The body initializes a package-level constant derived from the FND_PROFILE value ORG_ID, reflecting the multi-org architecture under which index rent data is partitioned by operating unit.

Key Procedures and Functions

• CREATE_INDEX_RENT — Creates a new index rent record. The procedure is documented in the package body with a formal header comment naming its subordinate call, PN_INDEX_RENT_PVT.CREATE_INDEX_RENT. It accepts an API version parameter, the standard initialization, commit, and validation flags, an index rent record structure, an index constraint collection, and the standard return status, message count, and message data outputs. The implementation opens a savepoint named CREATE_INDEX_RENT, sets the return status to success, conditionally initializes the FND message list, and invokes FND_API.COMPATIBLE_API_CALL to verify caller version compatibility before delegating to the private layer.
• UPDATE_INDEX_RENT — Modifies an existing index rent record. Although the excerpt does not reproduce its source, it is documented as one of the two procedures comprising the published interface. It follows the same conventions as CREATE_INDEX_RENT: a versioned API signature, savepoint bracketing, message stack initialization, and delegation to the private package for validation and DML.

Tables Accessed

The ETRM metadata for this package does not enumerate any directly referenced tables. This is consistent with the design: PN_INDEX_RENT_PUB performs no direct SQL. All persistence operations occur in PN_INDEX_RENT_PVT, which writes to the underlying Property Manager index rent tables. The only data access visible in the public body is the FND_PROFILE lookup for ORG_ID at package initialization. Callers should therefore consult the documentation for PN_INDEX_RENT_PVT to identify the concrete base tables affected.

Usage Notes

Because this is a PUB-classified API, it is the sanctioned integration point for index rent creation and update. It is typically invoked from Property Manager forms, from concurrent programs that apply index adjustments in bulk, or from custom PL/SQL that must create index rent data through supported interfaces rather than direct table manipulation. Callers should supply a valid p_api_version, observe the standard p_init_msg_list, p_commit, and p_validate flags, and retrieve error information through x_return_status, x_msg_count, and x_msg_data in the usual FND_API pattern. A search for the parameter string "null_param" does not correspond to any documented parameter of this package; the published parameters use the standard p_ and x_ naming convention. The package is referenced by zero other packages, indicating it is a top-level entry point rather than an internal dependency. No tables are documented as referenced via APPS synonyms.