Results for “grouping_rule_id”

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

Overview

The PN_PAY_GROUP_RULES_V view is an APPS-owned database object within the Oracle E-Business Suite Property Manager (PN) product family. As documented in the ETRM repository for releases 12.1.1 and 12.2.2, the object carries a status of VALID and is described as storing "grouping rules information." Functionally, the view exposes the set of grouping rules that govern how payment and billing transactions are aggregated or partitioned for processing within Property Manager. Grouping rules determine the criteria by which related transactions are condensed into a single payment or grouping entity, making them central to lease payment generation, tenant billing, and related financial workflows.

The view serves a reporting and integration role rather than a transactional one. Because it presents a readable, denormalized surface over the underlying grouping rule definition, it is well suited to concurrent programs, Oracle Reports, BI Publisher data models, and inbound/outbound interface extracts that must resolve a GROUPING_RULE_ID to its descriptive name and attributes. The user search term "grouping_rule_id" corresponds directly to the leading column of this view, which is the primary key reference used by dependent transaction tables to associate a transaction with its governing rule.

Underlying Base Objects

The documented view text is a direct, unfiltered projection over a single base object:

SELECT GROUPING_RULE_ID, NAME, DESCRIPTION, ... 
FROM PN_PAY_GROUP_RULES

The ETRM metadata lists exactly one referenced base object: PN_PAY_GROUP_RULES (a SYNONYM). The view performs no joins, unions, or aggregations; it is a one-to-one column mapping from the base table to the view. Consequently, row counts and key uniqueness are identical between the view and its base synonym. There is no WHERE clause, so no soft-deletion, date-effective, or organizational filtering is applied at the view layer. Callers requiring filtering by business criteria must supply their own predicates. The synonym PN_PAY_GROUP_RULES resolves in the APPS schema to the underlying Property Manager table, and the view inherits the same privileges and grants as that base object.

Key Columns

• GROUPING_RULE_ID — Numeric primary key uniquely identifying each grouping rule. Referenced as a foreign key by dependent payment grouping transaction entities; this is the column most commonly used in joins and lookups.
• NAME — User-defined name of the grouping rule, typically the value displayed in Property Manager setup forms and selection lists.
• DESCRIPTION — Free-text explanation of the rule's purpose or aggregation logic.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS WHO columns providing audit lineage for each record.
• ATTRIBUTE_CATEGORY — Descriptive flexfield context column, enabling the rule to carry a context-sensitive set of extension attributes.
• ATTRIBUTE1 through ATTRIBUTE15 — The fifteen standard descriptive flexfield segment columns, available for customer-defined configuration of grouping rules.

Common Use Cases and Queries

Typical usage resolves an ID to a name for reporting, or lists all available rules for a setup or validation screen. The following query retrieves all grouping rules ordered by name:

SELECT grouping_rule_id,
       name,
       description,
       attribute_category,
       attribute1
FROM   apps.pn_pay_group_rules_v
ORDER  BY name;

To look up a single rule by its identifier — the most frequent pattern driven by the "grouping_rule_id" search — the following is used:

SELECT grouping_rule_id,
       name,
       description
FROM   apps.pn_pay_group_rules_v
WHERE  grouping_rule_id = :p_grouping_rule_id;

In integration or extract scenarios, the view is joined to transaction tables on GROUPING_RULE_ID to enrich payment grouping records with the rule name and flexfield attributes. Because the view is a straight projection with no filtering, applications should apply their own WHERE clauses for performance and to avoid returning rules that are not in scope for the current operating unit or business context.