Search Results pn_rec_linbill_pk

Overview

The PN_REC_LINBILL_ALL table is a core data object within the Oracle E-Business Suite Property Manager (PN) module, specifically in versions 12.1.1 and 12.2.2. As documented, it serves as the Calculation Periods table. Its primary role is to store the detailed billing and calculation schedule information generated for individual lines of a recurring agreement. This table is central to the automated generation of invoices or billing schedules for recurring charges, such as rent, common area maintenance (CAM), or other periodic lease-related expenses. Being an "ALL" table, it is multi-org enabled, meaning it contains data partitioned by operating unit (ORG_ID) to support multiple organizations within a single installation.

Key Information Stored

The table's structure is designed to manage the lifecycle of a calculation period. The most critical column is the primary key, REC_LINBILL_ID, which uniquely identifies each calculation period record. Other significant columns, as indicated by the foreign key relationships, include REC_AGR_LINE_ID, which links the calculation period back to its specific parent line in the PN_REC_AGR_LINES_ALL table. The PAYMENT_TERM_ID column links to the PN_PAYMENT_TERMS_ALL table, defining the payment terms applicable to the calculated amount. The ORG_ID column is essential for data partitioning and security. While the explicit ETRM excerpt does not list all columns, typical data stored would also include calculation dates, billing dates, calculated amounts, status flags (e.g., billed, paid), and period start/end dates.

Common Use Cases and Queries

This table is primarily accessed for reporting on billing schedules, auditing calculation accuracy, and troubleshooting invoice generation. A common use case is to generate a report of all pending billings for a specific lease or operating unit. A typical query would join to agreement lines and header tables to provide context.

• Sample Query for Open Calculation Periods:
  SELECT prla.REC_LINBILL_ID, prala.REC_AGR_LINE_ID, prla.ORG_ID
FROM PN_REC_LINBILL_ALL prla
JOIN PN_REC_AGR_LINES_ALL prala ON prla.REC_AGR_LINE_ID = prala.REC_AGR_LINE_ID
WHERE prla.BILLED_DATE IS NULL AND prla.ORG_ID = :p_org_id;
• Audit Trail: Queries often trace the history of billed amounts for a specific agreement line by filtering on REC_AGR_LINE_ID and ordering by a period sequence or date column.
• Integration: Data from this table feeds into the Oracle Receivables module via the Property Manager's billing engine to create actual invoices.

Related Objects

The PN_REC_LINBILL_ALL table sits at the center of several key relationships within the Property Manager schema, as documented by its foreign keys. These relationships are crucial for accurate data retrieval and integrity.

• PN_REC_AGR_LINES_ALL: This is the primary parent table. The foreign key on column REC_AGR_LINE_ID establishes that every calculation period belongs to one specific recurring agreement line. This is the most frequently used join for operational reporting.
• PN_PAYMENT_TERMS_ALL: The foreign key on PAYMENT_TERM_ID links each calculation period to the applicable payment terms, which control invoice due dates and discount logic.
• HR_ALL_ORGANIZATION_UNITS: The foreign key on ORG_ID enforces the operating unit for the row, enabling the multi-org security model.

The primary key constraint, PN_REC_LINBILL_PK, on REC_LINBILL_ID ensures each calculation period record is uniquely identifiable across the system.