Search Results pn_rec_agr_linabat_all




Overview
Explore in AI Chat

Overview

The PN_REC_AGR_LINABAT_ALL table is a core data structure within the Oracle E-Business Suite Property Manager (PN) module, specifically in the context of lease administration and recovery agreements. As documented in the ETRM, this table serves as the "Recovery Abatement set up table." Its primary role is to store the detailed configuration and rules for abatements (or rent concessions) that are applied to specific recovery lines within a lease agreement. In the standard lease management lifecycle, this table enables the systematic definition of periods where a tenant's recovery charges are reduced or waived according to the terms negotiated in the lease contract. The table is multi-org enabled, as indicated by the '_ALL' suffix and the presence of the ORG_ID column, allowing it to store data for multiple operating units within a single installation.

Key Information Stored

While the provided metadata does not list all columns, the primary and foreign key relationships reveal the critical data points. The central identifier is the REC_AGR_LINABAT_ID, which is the primary key (PN_REC_AGR_LINABAT_PK). The most significant foreign key is REC_AGR_LINE_ID, which links each abatement rule directly to a specific recovery agreement line in the PN_REC_AGR_LINES_ALL table. This establishes a parent-child relationship where a recovery line can have multiple associated abatement rules. The ORG_ID column ties each record to an operating unit defined in HR_ALL_ORGANIZATION_UNITS, enforcing data security and partitioning. Typically, such a table would also store columns defining the abatement amount or percentage, the effective start and end dates for the abatement period, and potentially the abatement type or reason code.

Common Use Cases and Queries

The primary use case is the generation of accurate recovery billing schedules that respect contractual abatement clauses. During the invoice generation process, the system queries this table to identify any active abatements for a given recovery line within a billing period and adjusts the calculated charge accordingly. A common reporting need is to audit all active abatements across portfolios. A sample SQL pattern to retrieve abatement details for a specific lease or recovery agreement would involve joining to the parent recovery lines and agreement headers.

SELECT prala.REC_AGR_LINE_ID,
       prala.ABATEMENT_AMOUNT, -- Example inferred column
       prala.START_DATE,
       prala.END_DATE
FROM PN_REC_AGR_LINABAT_ALL prala
JOIN PN_REC_AGR_LINES_ALL pral ON prala.REC_AGR_LINE_ID = pral.REC_AGR_LINE_ID
JOIN PN_REC_AGREEMENTS_ALL pra ON pral.REC_AGR_ID = pra.REC_AGR_ID
WHERE pra.LEASE_ID = <lease_id>
  AND SYSDATE BETWEEN prala.START_DATE AND NVL(prala.END_DATE, SYSDATE)
  AND prala.ORG_ID = <org_id>;

Related Objects

The table maintains defined foreign key relationships with two other EBS tables, as per the provided metadata:

  • PN_REC_AGR_LINES_ALL: This is the primary parent table. The PN_REC_AGR_LINABAT_ALL.REC_AGR_LINE_ID column references PN_REC_AGR_LINES_ALL.REC_AGR_LINE_ID. This relationship ensures every abatement is attached to a valid recovery line.
  • HR_ALL_ORGANIZATION_UNITS: The PN_REC_AGR_LINABAT_ALL.ORG_ID column references HR_ALL_ORGANIZATION_UNITS.ORG_ID. This enforces the multi-org security model, segregating data by operating unit.

Furthermore, as a setup table for the recovery billing engine, it is intrinsically linked to the core agreement tables (PN_REC_AGREEMENTS_ALL) and the invoice generation programs and views within Property Manager.