Search Results pn_pay_group_rules




Overview
Explore in AI Chat

Overview

PN_PAY_GROUP_RULES is a Property Manager (PN) table in Oracle E-Business Suite that stores grouping rules information used to organize payment and disbursement processing for property leases, tenant billing, and related financial transactions. In the EBS 12.1.1 and 12.2.2 data models, the PN schema supports real estate and property lease management, and grouping rules defined in this table drive how individual payment or charge lines are consolidated — for example, by lease, tenant, property, or payment term — before being passed downstream to Oracle Payables, Receivables, or Cash Management.

From a Data Vault modeling perspective, the heuristic classification for this table is standalone. That classification suggests it functions as a reference or setup entity rather than a transactional hub or link. It can reasonably be modeled as a satellite-like or reference-table construct that holds descriptive attributes keyed by its own surrogate identifier, with no documented foreign-key dependencies to other tables. Because the table appears standalone in the mined FK structure, it is typically treated as configuration data that other processes reference by value rather than enforce through declarative constraints.

Key Information Stored

The table is defined with 24 columns. The most significant are:

The primary key (GROUPING_RULE_ID) is the surrogate identifier, while NAME acts as the natural or business key through unique index PN_PAY_GROUP_RULES_U2. A second unique index, PN_PAY_GROUP_RULES_U1, also covers GROUPING_RULE_ID, reinforcing its uniqueness. The 15 attribute columns are unpopulated by seed data and exist purely for extensibility.

Common Use Cases and Queries

Typical uses involve reviewing, reporting, and troubleshooting the grouping rules that govern how payables and receivables lines are consolidated for property transactions. A common lookup by business key:

  • SELECT grouping_rule_id, name, description FROM pn.pn_pay_group_rules WHERE name = :p_name;
  • SELECT grouping_rule_id, name, attribute_category, attribute1 FROM pn.pn_pay_group_rules WHERE attribute_category = :ctx;
  • Audit query: SELECT name, created_by, creation_date, last_updated_by, last_update_date FROM pn.pn_pay_group_rules ORDER BY last_update_date DESC;

Reporting use cases include extracting all configured grouping rules for data-migration reconciliation, validating flexfield attribute usage, and joining to payment or charge lines that reference the rule during grouping. Because the table is standalone, queries generally do not require joins within the PN schema; joins to downstream transactional tables should be based on the rule identifier or name held as a foreign value.

Related Objects

The documented metadata shows no enforced foreign keys, consistent with its standalone classification. Related objects that logically reference or depend on this table include:

  • PN_PAY_GROUP_RULES_PK — primary-key constraint on GROUPING_RULE_ID.
  • PN_PAY_GROUP_RULES_U1 — unique index on GROUPING_RULE_ID.
  • PN_PAY_GROUP_RULES_U2 — unique index on NAME, the business-key candidate.
  • Property Manager payment and disbursement tables that store a grouping rule reference value.
  • Lease and tenant billing line tables where grouped amounts originate.
  • Oracle Payables and Receivables interfaces that consume the grouped output.

Because the source metadata is limited to the standalone structure, any additional joins should be confirmed against the specific ETRM release's data model.