Results for “bkdt_start_date”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PN_VAR_BKDT_DEFAULTS_ALL is a Property Manager (PN) table within the Oracle E-Business Suite 12.1.1 and 12.2.2 environments. Its documented description is that it stores setup information for breakpoint details by organization. In functional terms, the table holds the tiered or graduated breakpoint definitions that govern how variable rent amounts, volumes and rates are calculated for a lease or property, with each definition scoped to a specific operating unit or organization through the ORG_ID column. Because the table name carries the _ALL suffix, records are partitioned by ORG_ID, and all queries should filter on this column to return only the rows relevant to the current organization.

From a Data Vault modeling perspective, the provided metadata classifies this object as hub-leaning. This is a heuristic suggestion derived from the foreign key structure, and it implies that the table's core identity — the BKDT_DEFAULT_ID — behaves much like a business hub key around which dependent detail and relationship attributes are attached. It is not a pure hub, since the table also carries descriptive and execution columns, but the classification is useful when designing downstream integration or analytics models.

Key Information Stored

The surrogate primary key is BKDT_DEFAULT_ID, physically enforced through the index PN_VAR_BKDT_DEFAULTS_PK, and also documented as a business-key candidate via the unique index PN_VAR_BKDT_DEFAULTS_U1. Beyond the key, the most significant columns include:

• BKDT_DETAIL_NUM — the sequencing number identifying the individual breakpoint detail line within a default set.
• BKHD_DEFAULT_ID — the foreign key linking the detail to its parent header record in PN_VAR_BKHD_DEFAULTS_ALL.
• VAR_RENT_ID — the foreign key pointing to the variable rent definition in PN_VAR_RENTS_ALL.
• BKDT_START_DATE / BKDT_END_DATE — the effective date range over which the breakpoint detail applies.
• PERIOD_BKPT_VOL_START / PERIOD_BKPT_VOL_END — the period breakpoint volume boundaries that define the tier.
• GROUP_BKPT_VOL_START / GROUP_BKPT_VOL_END — the group-level breakpoint volume boundaries.
• BKPT_RATE — the rate applied to the tier.
• BKPT_DET_TEMPLATE_ID — the template used to derive the breakpoint detail.
• PROCESSED_FLAG — indicates whether the row has been processed.
• ANNUAL_BASIS_AMOUNT — the annualized base amount used in the calculation.
• ORG_ID — the organization/operating unit that owns the setup row, mandatory for multi-org filtering.
• Audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) and the fifteen ATTRIBUTE descriptor columns, which support OA Framework extensions and DFF usage.

Common Use Cases and Queries

Typical scenarios include validating that breakpoint tiers are contiguous and free of gaps or overlaps, reviewing rates for a given variable rent, and auditing changes to breakpoint setup. A representative query joins the detail to its header and rent definition:

• SELECT d.bkdt_default_id, d.bkdt_detail_num, d.bkpt_rate, d.period_bkpt_vol_start, d.period_bkpt_vol_end FROM pn_var_bkdt_defaults_all d WHERE d.org_id = :org_id AND d.var_rent_id = :rent_id ORDER BY d.bkdt_detail_num;
• Detecting unprocessed rows: SELECT * FROM pn_var_bkdt_defaults_all WHERE processed_flag = 'N' AND org_id = :org_id;
• Effective-dating checks using BKDT_START_DATE and BKDT_END_DATE to find tiers active on a given transaction date.

Related Objects

• PN_VAR_BKHD_DEFAULTS_ALL — parent header table, joined on BKHD_DEFAULT_ID.
• PN_VAR_RENTS_ALL — variable rent master, joined on VAR_RENT_ID.
• PN_VAR_BKPTS_DET_ALL — child detail table that references this table via BKDT_DEFAULT_ID.
• Standard EBS multi-org views and the PN Property Manager setup and rent calculation forms, which consume this table through the Application Object Library and OA Framework layers.