Search Results pn_var_abat_defaults_u1

Overview

PN.PN_VAR_ABAT_DEFAULTS_ALL is an Oracle E-Business Suite table that resides in the PN (Property Manager) schema and stores default setup information for abatements and allowances associated with variable rent agreements. It is a transactional data table that supports lease and property management functionality, enabling organizations to define fixed abatements and rolling allowances that reduce rent obligations over defined periods. Each row represents a single abatement or allowance default configuration linked to a variable rent agreement.

The table is registered under FND Design Data as PN.PN_VAR_ABAT_DEFAULTS_ALL and has a status of VALID. It is stored in the APPS_TS_TX_DATA tablespace with a PCT FREE of 10. From a data modeling perspective, the metadata's relationship structure is best characterized as a standalone table. Although it holds a foreign key reference to PN_VAR_RENTS_ALL via VAR_RENT_ID, it functions independently as a primary entity owning its own abatement configuration records rather than serving purely as a dependent satellite or associative link. Its descriptive columns and standard Who columns support both transactional and audit requirements, while its descriptive flexfield (DFF) columns accommodate organization-specific extensibility.

Key Information Stored

The table's physical schema comprises 31 columns. The most significant are listed below.

• ABATEMENT_ID (NUMBER): The surrogate primary key and identifier for the abatement or allowance. It is the column behind the unique index PN_VAR_ABAT_DEFAULTS_U1, making it both the primary key (PN_VAR_ABAT_DEFAULTS_PK) and the documented business-key candidate.
• VAR_RENT_ID (NUMBER): Foreign key to PN_VAR_RENTS_ALL, identifying the variable rent agreement to which the abatement applies.
• START_DATE and END_DATE (DATE): Define the effective period during which the abatement or allowance is applied.
• TYPE_CODE (VARCHAR2, 30): Classifies the record as either a fixed abatement (AB) or a rolling allowance (AL).
• AMOUNT (NUMBER): The monetary value of the abatement or allowance.
• ALLOWANCE_APPLIED (NUMBER): Tracks the amount of a rolling allowance that has been applied to date.
• DESCRIPTION and COMMENTS (VARCHAR2, 2000): Free-text fields describing the abatement and capturing related remarks.
• ORG_ID (NUMBER): The operating unit identifier supporting multi-org partitioning.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN: Standard Who audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15: Descriptive flexfield columns for capturing additional organization-specific attributes.

Common Use Cases and Queries

Typical usage centers on reporting and validation of abatement and allowance defaults for variable rent agreements. Common scenarios include extracting active abatements for a rent agreement, reconciling allowance amounts applied, and auditing default setups by operating unit.

A representative query lists active abatements for a given variable rent agreement:

SELECT abatement_id, var_rent_id, start_date, end_date,
       type_code, amount, allowance_applied
FROM   pn_var_abat_defaults_all
WHERE  var_rent_id = :var_rent_id
AND    start_date <= SYSDATE
AND    (end_date IS NULL OR end_date >= SYSDATE);

Another reporting pattern aggregates allowances by type and operating unit:

SELECT org_id, type_code,
       SUM(amount)           total_amount,
       SUM(allowance_applied) total_applied
FROM   pn_var_abat_defaults_all
GROUP  BY org_id, type_code;

Because the table is an _ALL table, multi-org security is enforced through ORG_ID, so production queries should filter on ORG_ID or rely on the client extension (MO) views.

Related Objects

The following objects are most significant in relation to PN_VAR_ABAT_DEFAULTS_ALL.

• PN.PN_VAR_RENTS_ALL: Parent variable rent agreement table. Joined via PN_VAR_ABAT_DEFAULTS_ALL.VAR_RENT_ID = PN_VAR_RENTS_ALL.VAR_RENT_ID; this is the sole documented foreign key relationship.
• PN.PN_VAR_ABAT_DEFAULTS_PK: Primary key constraint on ABATEMENT_ID.
• PN.PN_VAR_ABAT_DEFAULTS_U1: Unique index on ABATEMENT_ID in the APPS_TS_TX_IDX tablespace; also the documented business-key candidate.
• PN_VAR_ABAT_DEFAULTS_ALL MO views: Multi-org secured synonyms/views generated for this _ALL table for operating unit filtering.
• PN_VAR_ABAT_DEFAULTS_ALL DFF setup: Descriptive flexfield definitions attached through ATTRIBUTE_CATEGORY.