Search Results pn_var_bkdt_defaults_all

Overview

The PN_VAR_BKDT_DEFAULTS_ALL table is a core setup table within the Oracle E-Business Suite (EBS) Property Manager (PN) module. It functions as a repository for default breakpoint detail configurations that are defined at the organization level. In the context of lease management, breakpoints are clauses in a lease agreement that trigger changes in payment amounts, typically based on a tenant's sales volume or other performance metrics. This table stores the master definitions for these breakpoint details, enabling standardized, organization-wide setup that can be consistently applied across multiple lease agreements. Its role is critical for ensuring accurate and automated variable rent calculations within the Property Manager application.

Key Information Stored

While the specific column list is not detailed in the provided metadata, the table's primary key and relationships indicate its core structure. The primary identifier is the BKDT_DEFAULT_ID, a unique system-generated key for each default breakpoint detail record. Based on its purpose, the table likely stores descriptive and calculation-related attributes for a breakpoint detail template. This can include fields such as a default breakpoint name or description, a default breakpoint type (e.g., natural, cumulative), default calculation methods, and the associated ORG_ID (implied by the "_ALL" suffix) to support multi-organization architecture (MOAC). The data stored here serves as a template that is referenced when creating specific, lease-level breakpoint details.

Common Use Cases and Queries

The primary use case is the administration and application of standardized breakpoint rules. Property administrators use this setup to define common variable rent structures, which are then selected when configuring individual leases. For reporting and analysis, common queries involve listing all organization-level defaults or verifying setup completeness. A typical SQL pattern to audit these defaults would be:

SELECT bkdt_default_id, name, description, org_id
FROM pn_var_bkdt_defaults_all
WHERE org_id = :p_org_id
ORDER BY name;

Another critical use case is troubleshooting lease calculation errors by tracing the source default setup. Integration or data migration scripts may also query this table to extract or validate breakpoint configuration master data before loading transactional lease information.

Related Objects

This table has a direct, documented relationship with the transactional table that implements its defaults. The foreign key relationship is as follows:

• The table PN_VAR_BKPTS_DET_ALL references PN_VAR_BKDT_DEFAULTS_ALL via the column PN_VAR_BKPTS_DET_ALL.BKDT_DEFAULT_ID. This relationship shows that individual breakpoint details created for specific leases (stored in PN_VAR_BKPTS_DET_ALL) can inherit their configuration from a master default record defined in this table. The standard join for querying a lease's breakpoint details with their source default setup is: SELECT det.*, def.name AS default_name
FROM pn_var_bkpts_det_all det, pn_var_bkdt_defaults_all def
WHERE det.bkdt_default_id = def.bkdt_default_id(+);