Results for “parameter_code”

2 results




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

Overview

IBY_PMTMTHD_CONDITIONS is a table in the IBY (Payments) module of Oracle E-Business Suite, owned by the IBY schema. It stores the individual conditions that govern a payment method. As documented in ETRM, each condition is composed of a parameter, an operation, and a value, and is evaluated at runtime to determine whether the condition is satisfied. This evaluation typically occurs during payment instruction processing, when Oracle Payments decides whether a given payment method is eligible for a transaction or a routing configuration.

In Data Vault terms, the mined foreign-key structure suggests a satellite-leaning classification. The table's dependency on IBY_ROUTINGINFO via PAYMENTMETHODID indicates that IBY_PMTMTHD_CONDITIONS behaves primarily as a descriptive satellite attached to a routing or payment-method parent, rather than as an independent hub or a pure link between two hubs. The composite nature of the primary key reinforces that these records qualify or describe a parent entity rather than exist as first-class business entities themselves.

Key Information Stored

The table contains 14 documented columns. The most important are:

The unique key IBY_PMTMTHD_CONDITIONS_UK spans PAYMENTMETHODID, ENTRY_SEQUENCE, PARAMETER_CODE, and OPERATION_CODE. This is the documented business-key candidate; it uniquely identifies a condition within a payment method. No separate single-column surrogate key is documented, so the composite unique key effectively serves as the primary identifier.

Common Use Cases and Queries

Typical use cases include auditing which conditions are configured for a payment method, diagnosing why a payment method failed to qualify at runtime, and migrating or comparing condition setups across environments. A representative query retrieves all conditions for a given payment method in evaluation order:

  • SELECT entry_sequence, parameter_code, operation_code, value, condition_name FROM iby_pmtmthd_conditions WHERE paymentmethodid = :pmt_method_id ORDER BY entry_sequence;
  • SELECT c.*, r.* FROM iby_pmtmthd_conditions c JOIN iby_routinginfo r ON c.paymentmethodid = r.paymentmethodid;
  • SELECT condition_name, COUNT(*) FROM iby_pmtmthd_conditions GROUP BY condition_name; — profiling condition usage across setups.

Reporting scenarios frequently join to IBY_ROUTINGINFO to present human-readable payment method names alongside the raw condition parameters, and to FND_SECURITY_GROUPS to filter by operating unit.

Related Objects

The most significant related objects are the foreign-key parents and the objects that depend on this table:

  • IBY_ROUTINGINFO — Parent of PAYMENTMETHODID; provides the payment method and routing context.
  • FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID for multi-org security.
  • Payment method setup forms and the Oracle Payments runtime engine, which read these rows during condition evaluation.
  • Related payment method definition tables in the IBY schema that share PAYMENTMETHODID semantics.

Because IBY_PMTMTHD_CONDITIONS is implementation/DBA data, modifications should be performed through supported Oracle Payments setup screens or approved concurrent programs rather than direct DML.