Search Results pn_var_bkdt_defaults_pkg




Overview
Explore in AI Chat

Overview

The APPS.PN_VAR_BKDT_DEFAULTS_PKG package is a PL/SQL database object within the Oracle E-Business Suite Property Manager (PN) module. Its name indicates its role: managing variable booking detail defaults — the default values that are applied to booking detail records when lease or property booking transactions are created or modified. The package carries a status of VALID in the APPS schema and is classified under the ETRM metadata as an OTHER API classification, signifying that it is a supporting data-maintenance package rather than a formally published public API.

The package provides the standard CRUD (create, read, update, delete) operations used to maintain the booking detail default configuration. These defaults allow organizations to pre-populate booking-related attributes so that users creating new bookings inherit sensible, policy-compliant values without manual entry. In Oracle EBS 12.1.1 and 12.2.2, this package operates as an internal dependency consumed by other Property Manager packages rather than as an end-user-facing API.

Key Procedures and Functions

Five documented procedures comprise the package interface. Each follows the conventional naming pattern used by Oracle EBS table-handler packages:

  • INSERT_ROW — Creates a new booking detail default record in the underlying defaults table, populating the configured attribute values for subsequent use during booking creation.
  • LOCK_ROW — Acquires a row-level lock on an existing default record, ensuring serialized access when concurrent sessions attempt to modify the same configuration row.
  • UPDATE_ROW — Modifies the stored values of an existing booking detail default record, allowing changes to the pre-populated attributes.
  • DELETE_ROW — Removes a booking detail default record when the configuration is no longer required.
  • MODIFY_ROW — Provides a combined locking-and-modification entry point, typically implemented as a convenience wrapper that invokes lock and update logic in sequence.

The metadata does not expose parameter signatures; parameter lists should never be assumed and must be verified against the deployed package specification on the target instance.

Tables Accessed

The package operates against four documented tables and views, accessed via APPS synonyms:

  • PN_VAR_BKDT_DEFAULTS_ALL — The primary multi-organization (ALL) table storing booking detail default definitions across operating units; the target of insert, update, and delete operations.
  • PN_VAR_BKDT_DEFAULTS_S — The corresponding sequence or security view used for key generation and row-level security filtering consistent with EBS multi-org architecture.
  • PN_VAR_BKHD_DEFAULTS_ALL — The booking header defaults table, referenced for header-level default context that constrains or complements the detail-level defaults.
  • DUAL — The standard Oracle pseudo-table, used for single-row queries and expression evaluation.

Usage Notes

PN_VAR_BKDT_DEFAULTS_PKG is not invoked directly by end users. It is referenced by four other APPS packages — including PN_VAR_BKDT_DEFAULTS_PKG itself, PN_VAR_CHG_CAL_PKG, PN_VAR_NATURAL_BP_PKG, and PN_VAR_RENT_PKG — confirming it functions as a shared data-access layer for variable-booking processing logic such as charge calculation, natural business partner handling, and rent computation.

Typical invocation occurs from Property Manager forms and concurrent programs that create or maintain variable bookings, where defaults are retrieved and applied before user review. Because the package is classified as a private supporting object, customizations should call it only with caution and after validating behavior on the specific EBS release (12.1.1 or 12.2.2), since internal signatures are not guaranteed stable. For supported extensions, the developer should prefer documented public APIs and use this package primarily as a diagnostic reference when tracing booking-default behavior.