Search Results iby_pmt_logical_grp_rules_pk

Overview

The IBY_PMT_LOGICAL_GRP_RULES table is a core repository within the Oracle E-Business Suite Payments (IBY) module, specifically for versions 12.1.1 and 12.2.2. It defines the configurable business rules that govern how individual payment requests are logically aggregated into distinct groups within a single payment instruction. This logical grouping is a critical step in the payment process execution, enabling the system to batch payments efficiently based on shared attributes, which directly influences the structure and number of payment files transmitted to banks. The table's integrity is maintained by its primary key and its foreign key relationship to the system payment profiles table, anchoring these grouping rules to specific payment system configurations.

Key Information Stored

The table's primary function is to store rule definitions. The most critical column is SYSTEM_PROFILE_CODE, which serves as the foreign key linking each grouping rule to a specific payment system profile defined in IBY_SYS_PMT_PROFILES_B. While the provided metadata does not list all columns, typical attributes stored in such a rule table would include identifiers for the rule itself, the specific payment attribute used for grouping (e.g., payment method, currency, supplier bank account, payment date, or legal entity), and the sequence or priority of the rule application. The presence of a primary key constraint (IBY_PMT_LOGICAL_GRP_RULES_PK) on SYSTEM_PROFILE_CODE indicates that, within this table, the profile code is a unique identifier for a rule set, or is part of a composite key with another column like RULE_SEQUENCE_NUM or GROUPING_ATTRIBUTE.

Common Use Cases and Queries

This table is primarily referenced during the "Build Payments" and "Format Payments" stages of the Payment Process Request. A common operational use case is auditing or verifying the grouping logic applied to a payment batch. For instance, an administrator might query to see all grouping rules for a specific payment system profile to troubleshoot why payments were split into multiple instructions. A typical diagnostic SQL pattern would join this table to the profiles table:

• SELECT prof.system_profile_code, prof.profile_name, grp.* FROM iby.iby_pmt_logical_grp_rules grp, iby.iby_sys_pmt_profiles_b prof WHERE grp.system_profile_code = prof.system_profile_code AND prof.profile_name = '&PROFILE_NAME';

Reporting use cases include documenting the payment process setup for compliance or creating implementation guides that detail the hierarchical grouping logic (e.g., group first by currency, then by payment method).

Related Objects

The table has a documented, direct foreign key relationship with the IBY_SYS_PMT_PROFILES_B table, which stores the master definition of payment system profiles. The relationship is defined as:

• Foreign Key from: IBY_PMT_LOGICAL_GRP_RULES.SYSTEM_PROFILE_CODE
• References Primary Key in: IBY_SYS_PMT_PROFILES_B (presumably on its SYSTEM_PROFILE_CODE column)

This relationship ensures that every grouping rule is associated with a valid system profile. The table is also intrinsically related to the payment instruction entities (e.g., IBY_PAYMENTS_ALL, IBY_PMT_INSTRUCTIONS_ALL) whose creation it governs, though these may not be enforced via a direct database foreign key. The Payment Process Request (IBY_PAY_SERVICE_REQUESTS) execution engine relies on the rules stored here to perform logical grouping.