Search Results pn_distributions_s

Overview

The APPS.PN_DISTRIBUTIONS_PKG package body is a core PL/SQL construct within the Oracle E-Business Suite Property Manager (PN) module, which governs the management of leased and owned property, including the financial distribution of rent, expenses, and other property-related transactions. This package encapsulates the data manipulation logic required to maintain records in the distributions tables that drive property accounting and expense allocation. In EBS 12.1.1 and 12.2.2, the package carries a status of VALID and is owned by the APPS schema, confirming it is a supported, standard Oracle-delivered object rather than a customer extension. Its primary responsibility is to provide the procedural interface for inserting, updating, locking, and deleting rows that represent how financial amounts are apportioned across properties, payment terms, and term templates. Because the object is documented as referenced by six other database objects and itself depends on several sibling packages and tables, it functions as a foundational utility layer within the Property Manager transaction flow rather than an end-user-facing component.

Key Procedures and Functions

The ETRM metadata documents four principal procedures, plus an additional referenced routine, giving five total entries. Their names follow the standard EBS table-handler convention, indicating that this is a table-handling package:

• INSERT_ROW — Creates a new distribution record in the underlying distributions table. This procedure typically validates and populates column values before committing the new distribution entry, allowing the calling program to register a fresh allocation of amounts against a property or term.
• UPDATE_ROW — Modifies an existing distribution record. It is used when distribution amounts, term associations, or related attributes must be revised without recreating the row.
• LOCK_ROW — Obtains a row-level lock on a distribution record to prevent concurrent modification. This supports the transactional integrity required when multiple sessions might otherwise attempt to change the same distribution simultaneously.
• DELETE_ROW — Removes a distribution record, used when an allocation is reversed or a term is no longer applicable.

The metadata explicitly notes that no parameter lists are documented, so the exact argument signatures are not reproduced here; the procedures are described solely by their established purpose within the table-handling pattern.

Tables Accessed

The package body references the following tables through APPS synonyms, each serving a distinct role:

• PN_DISTRIBUTIONS_ALL — The primary distributions table that the INSERT_ROW, UPDATE_ROW, LOCK_ROW, and DELETE_ROW procedures operate against.
• PN_DISTRIBUTIONS_S — A sequence or secondary distributions object supporting the same distribution logic; note the user's search term "pn_distributions_s" corresponds to this object.
• PN_PAYMENT_TERMS and PN_PAYMENT_TERMS_ALL — Payment term definitions that determine how distributions are scheduled and calculated.
• PN_TERM_TEMPLATES_ALL — Term templates used to standardize the generation of distribution records.
• DUAL — Used for single-row computations and validation queries.

The package additionally depends on FND_GLOBAL (for session context such as user and login information), PN_R12_UTIL_PKG, and PN_VAR_RENT_PKG, indicating interaction with Release 12 utilities and variable rent processing.

Usage Notes

PN_DISTRIBUTIONS_PKG is typically invoked indirectly through Property Manager forms, concurrent programs, and the higher-level packages that reference it (six documented referencing objects). Because it is a table-handling package, it is not intended for direct end-user invocation; instead, business logic layers and form-based transactions call its procedures to persist distribution data. In Oracle EBS 12.2.2 online patching environments, the package is compiled and managed as part of the APPS schema, and customizations should avoid modifying it directly, relying instead on its documented API surface. Developers integrating with Property Manager distributions should call these procedures rather than issuing direct DML against the underlying tables to preserve validation and locking behavior.