Results for “system_profile_code”

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

Overview

IBY.IBY_PMT_LOGICAL_GRP_RULES is a configuration table within the Oracle Payments (IBY) module of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. The table specifies the attributes that Oracle Payments uses to group individual payments into logical groups within a payment instruction. Each row represents a grouping rule set tied to a specific system payment profile, determining how payment documents are consolidated or separated during the payment instruction build process.

From a Data Vault modeling perspective, the metadata classifies this table as satellite-leaning. This is a heuristic derived from its foreign key structure. The table behaves as a satellite because it holds descriptive, attribute-style configuration data that qualifies a parent business entity — here, the system payment profile — rather than acting as an independent hub or as a pure many-to-many resolution link. Each row is effectively descriptive context for a payment profile row in IBY_SYS_PMT_PROFILES_B.

Key Information Stored

The table contains 18 documented columns in the 12.2.2 schema. The surrogate primary key is enforced through the constraint IBY_PMT_LOGICAL_GRP_RULES_PK, defined on SYSTEM_PROFILE_CODE. A second unique index, IBY_PMT_LOGICAL_GRP_RULES_U1, is defined on the composite (SYSTEM_PROFILE_CODE, ZD_EDITION_NAME), which serves as the business-key candidate supporting editions-enabled multi-tenant operations.

• SYSTEM_PROFILE_CODE — Primary key and foreign key identifying the owning system payment profile.
• GROUP_BY_PAYMENT_DATE — Flag indicating whether payments are grouped by payment date.
• GROUP_BY_PAYMENT_CURRENCY — Controls grouping by disbursement currency.
• GROUP_BY_INTERNAL_BANK_ACCOUNT — Determines whether the internal bank account drives grouping.
• GROUP_BY_LEGAL_ENTITY — Indicates grouping by legal entity.
• GROUP_BY_OPERATING_UNIT — Indicates grouping by operating unit.
• GROUP_BY_PAYMENT_METHOD — Determines whether payment method is a grouping attribute.
• GROUP_BY_PAYMENT_REASON — Controls grouping by payment reason.
• GROUP_BY_SETTLEMENT_PRIORITY — Controls grouping by settlement priority.
• GROUP_BY_PAYMENT_FUNCTION — Determines grouping by payment function.
• GROUP_BY_DELIVERY_CHANNEL — Determines whether delivery channel drives grouping.
• ZD_EDITION_NAME — Edition discriminator supporting EBS 12.2 online patching.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns.

Common Use Cases and Queries

The most frequent usage is troubleshooting why payments are consolidated or split within a single payment instruction. Administrators query this table to confirm the active grouping rules for a given profile before a payment run.

A typical query joining to the parent profile table:

• SELECT r.SYSTEM_PROFILE_CODE, r.GROUP_BY_PAYMENT_CURRENCY, r.GROUP_BY_PAYMENT_METHOD, r.GROUP_BY_LEGAL_ENTITY FROM IBY.IBY_PMT_LOGICAL_GRP_RULES r WHERE r.SYSTEM_PROFILE_CODE = :profile;
• Reporting on which profiles group by a specific attribute, for example: SELECT SYSTEM_PROFILE_CODE FROM IBY_PMT_LOGICAL_GRP_RULES WHERE GROUP_BY_PAYMENT_CURRENCY = 'Y';
• Audit extraction of configuration changes using LAST_UPDATE_DATE.

Related Objects

The principal relationship is the foreign key from SYSTEM_PROFILE_CODE to IBY_SYS_PMT_PROFILES_B.SYSTEM_PROFILE_CODE, meaning each rule set belongs to exactly one system payment profile. Related tables that reference or depend on the payment profile hierarchy include IBY_PAYMENT_INSTRUCTIONS, IBY_PAYMENTS_ALL, IBY_PMT_INSTR_USES_ALL, and IBY_SYS_PMT_PROFILES_TL for translated profile names. Reporting queries typically join IBY_PMT_LOGICAL_GRP_RULES to IBY_SYS_PMT_PROFILES_B and IBY_SYS_PMT_PROFILES_TL to produce readable configuration reports.