Results for “iby_payment_rules”

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

Overview

IBY_PAYMENT_RULES is a table in the IBY (Payments) product schema of Oracle E-Business Suite, present and valid in both release 12.1.1 and 12.2.2. It stores the header-level definition of a payment method defaulting rule. A defaulting rule allows an application or administrator to establish, for a given transaction context, which payment method should be selected by default. The header record anchors the rule's identity, target payment method, priority, and owning application, while the detailed matching criteria that drive the rule are held in child records.

Under a heuristic Data Vault classification mined from the foreign key structure, IBY_PAYMENT_RULES is satellite-leaning. It carries descriptive and operational attributes of a defaulting rule and is referenced by a dependent child table, rather than behaving purely as a hub of business keys or as a pure link between two hubs. This classification should be treated as a modeling suggestion for warehouse design and not as a constraint on the EBS data model itself.

Key Information Stored

The documented physical schema contains eleven columns in the IBY schema. The most significant are:

• PAYMENT_RULE_ID — the surrogate primary key, uniquely generated and enforced by the IBY_PAYMENT_RULES_PK constraint and the unique index IBY_PAYMENT_RULES_U1. This is the column used by all downstream references.
• PAYMENT_RULE_NAME — the user-facing name of the defaulting rule, the principal business-key candidate by which rules are identified in setup and maintenance.
• PAYMENT_METHOD_CODE — foreign key to IBY_PAYMENT_METHODS_B, identifying the payment method that the rule defaults when its conditions are satisfied.
• PAYMENT_RULE_PRIORITY — numeric precedence that resolves conflicts when more than one rule matches the same transaction context.
• APPLICATION_ID — foreign key to FND_APPLICATION, identifying the application that owns the rule and scoping it to the relevant product.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle Application Framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns recording insert and update provenance and timing.

Note that while PAYMENT_RULE_ID is unique, PAYMENT_RULE_NAME is the practical business identifier presented to users; the documented unique index is on the surrogate key only.

Common Use Cases and Queries

Typical use cases include auditing which payment method a given rule defaults, reporting rule priority ordering, and joining rule headers to their condition rows to reconstruct the full defaulting logic. A representative query lists enabled rules with their target methods:

• SELECT pr.payment_rule_id, pr.payment_rule_name, pr.payment_method_code, pr.payment_rule_priority FROM iby.iby_payment_rules pr ORDER BY pr.payment_rule_priority;
• SELECT pr.payment_rule_name, pm.payment_method_name, pr.payment_rule_priority FROM iby.iby_payment_rules pr, iby.iby_payment_methods_b pm WHERE pr.payment_method_code = pm.payment_method_code AND pr.application_id = :app_id;
• SELECT pr.payment_rule_name, rc.* FROM iby.iby_payment_rules pr, iby.iby_rule_conditions rc WHERE pr.payment_rule_id = rc.payment_rule_id AND pr.payment_rule_id = :rule_id;

Reporting scenarios commonly center on priority gaps, rules pointing at inactive payment methods, and the distribution of rules by owning application.

Related Objects

The following objects are most significant in relation to IBY_PAYMENT_RULES, based on the documented foreign key relationships:

• IBY_RULE_CONDITIONS — child table referencing IBY_PAYMENT_RULES.PAYMENT_RULE_ID via IBY_RULE_CONDITIONS.PAYMENT_RULE_ID; stores the contextual criteria that trigger each rule.
• IBY_PAYMENT_METHODS_B — referenced through IBY_PAYMENT_RULES.PAYMENT_METHOD_CODE; supplies the defaulted payment method definition.
• FND_APPLICATION — referenced through IBY_PAYMENT_RULES.APPLICATION_ID; identifies the owning application.
• IBY_PAYMENT_RULES_PK / IBY_PAYMENT_RULES_U1 — the primary key constraint and unique index enforcing PAYMENT_RULE_ID.

Together these objects define and constrain how default payment methods are resolved for a transaction context within the IBY Payments module.