Results for “group_by_pay_service_request”

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

Overview

The IBY_INSTR_CREATION_RULES table is a Payments module configuration object within the Oracle E-Business Suite IBY schema. It stores the rule definitions that govern how individual payment instructions are created and grouped from underlying payment documents, such as bills payable, invoices, and pay runs. Each row represents a set of creation rules bound to a payment system profile, determining how payments are consolidated into instructions, what limits apply, and how those instructions are sorted before transmission to a payment system.

From a data modeling standpoint, the mined relationship metadata classifies this object as satellite-leaning. This suggestion reflects the table's dependence on a parent profile entity (IBY_SYS_PMT_PROFILES_B) and its role in carrying descriptive, versioned attributes rather than serving as an independent hub or a pure association link. The table is a vertical extension of the payment system profile: it does not exist independently but derives its identity from SYSTEM_PROFILE_CODE, which is both the primary key column and a foreign key to the parent profile definition.

Key Information Stored

The surrogate key is enforced by IBY_INSTR_CREATION_RULES_PK on SYSTEM_PROFILE_CODE. The unique index IBY_INSTR_CREATION_RULES_U1 spans SYSTEM_PROFILE_CODE and ZD_EDITION_NAME, identifying the business-key candidate and indicating support for edition-based (ZD) versioning of rule definitions.

The most operationally significant columns include:

• SYSTEM_PROFILE_CODE — The primary key and foreign key linking the rule set to a payment system profile in IBY_SYS_PMT_PROFILES_B.
• GROUP_BY_PAYMENT_DATE — Controls whether payments are consolidated based on their payment date.
• GROUP_BY_PAYMENT_CURRENCY — Determines whether currency drives instruction grouping.
• GROUP_BY_INTERNAL_BANK_ACCOUNT — Groups payments by the disbursing internal bank account.
• GROUP_BY_LEGAL_ENTITY — Groups payments by legal entity, essential for regulatory separation.
• GROUP_BY_PAYMENT_METHOD — Groups payments by method such as check, wire, or ACH.
• GROUP_BY_PAYMENT_FUNCTION and GROUP_BY_PAYMENT_REASON — Refine grouping by functional purpose or reason code.
• MAX_PAYMENTS_PER_INSTRUCTION — Caps the number of payments that may be bundled into one instruction.
• MAX_AMOUNT_PER_INSTR_VALUE and MAX_AMOUNT_PER_INSTR_CURR_CODE — Define a monetary ceiling per instruction and its currency.
• SORT_OPTION_1 through SORT_OPTION_3 and SORT_ORDER_1 through SORT_ORDER_3 — Specify up to three sort criteria and their ascending or descending order within an instruction.
• Standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, OBJECT_VERSION_NUMBER) provide change tracking and optimistic locking.

Common Use Cases and Queries

The primary use case is diagnosing why payments were grouped into a particular instruction count or why a payment system rejected an instruction for exceeding a limit. A typical query retrieves the rule set for a given profile:

• SELECT group_by_payment_date, group_by_payment_currency, group_by_internal_bank_account, max_payments_per_instruction, max_amount_per_instr_value FROM iby.iby_instr_creation_rules WHERE system_profile_code = :profile_code;

Reporting scenarios include auditing grouping behavior across all payment systems, comparing editioned rule sets via ZD_EDITION_NAME, and validating that amount ceilings are configured consistently with bank agreements. Extract and reconciliation processes frequently join this table to the parent profile to confirm the active rule configuration at the time an instruction was generated.

Related Objects

The most significant related objects, based on the documented foreign key and profile relationship, are:

• IBY_SYS_PMT_PROFILES_B — The parent payment system profile referenced by SYSTEM_PROFILE_CODE; the primary join is iby_instr_creation_rules.system_profile_code = iby_sys_pmt_profiles_b.system_profile_code.
• IBY_SYS_PMT_PROFILES_TL — The translated profile table supplying user-facing profile names and descriptions.
• IBY_PAY_SERVICE_REQUEST — Payment service requests consumed by the creation process the rules govern.
• IBY_PAYMENTS — Individual payment records consolidated into instructions per the grouping rules.
• IBY_PAY_INSTR — The resulting payment instructions produced under these limits and sort options.

These objects collectively form the configuration-to-execution chain through which the IBY_INSTR_CREATION_RULES table controls payment instruction formation.