Results for “iby_payee”

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

Overview

IBY_PAYEE is a core table in the Oracle Payments (IBY) module of Oracle E-Business Suite 12.1.1 and 12.2.2. It holds one row for each payee registered at a given site, where a payee may represent a biller, merchant, or store participating in payment and funds capture processing. The table acts as the master registry of trading partners for the Payments product, anchoring configuration for payment processing, funds capture, risk assessment, and transaction routing.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure identifies IBY_PAYEE as a hub. This is consistent with its position at the center of a star of dependent tables: IBY_PAYEE carries the durable business identifier MPAYEEID and is referenced by numerous satellite-style tables that record payment methods, routing information, risk rules, and transaction summaries. The modeling suggestion is therefore to treat IBY_PAYEE as the canonical list of payee business keys, with surrounding tables supplying descriptive and transactional context.

Key Information Stored

The table contains 27 documented columns. The most operationally significant are listed below.

• MPAYEEID — surrogate primary key defined by the constraint IBY_PAYEE_PK. It is the internal identifier referenced throughout the IBY schema and by dependent tables such as IBY_BATCHES_ALL, IBY_ROUTINGINFO, and IBY_DEFAULT_BEP.
• PAYEEID — the business-key candidate enforced by the unique index IBY_PAYEE_PAYEEID_U1, providing an alternate external identifier for the payee.
• NAME — the descriptive name of the payee, used for reporting and selection.
• ECAPPID — foreign key to IBY_ECAPP, linking the payee to the electronic commerce application configuration under which it operates.
• USERNAME and PASSWORD — credentials used when the payee is accessed by payment or funds capture processes.
• ACTIVESTATUS and INACTIVE_DATE — control whether the payee is currently selectable and record when it was retired.
• THRESHOLD — the monetary limit configured for the payee.
• RISK_ENABLED, SECURITY_ENABLED, and SUPPORTEDOP — flags governing risk evaluation, security validation, and the supported payment operations.
• MCC_CODE — merchant category code, relevant for card and funds capture processing.
• EMAIL_ADDRESS and FINANCING_PAYEE_FLAG — contact detail and an indicator of financing payee status.
• DBA_NAME, DBA_CITY, DBA_STATE_PROVINCE, and DBA_COUNTRY — the "doing business as" address attributes for the payee.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-organization data security.
• OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — standard EBS audit and concurrency columns.

Common Use Cases and Queries

IBY_PAYEE is queried when validating, reporting on, or extending payee configuration. A typical lookup resolves a payee by its external identifier:

• Payee lookup by business key: SELECT mpayeeid, name, activestatus FROM iby_payee WHERE payeeid = :p_payeeid;
• Active payee roster for reporting: SELECT payeeid, name, mcc_code FROM iby_payee WHERE activestatus = 'A' AND (inactive_date IS NULL OR inactive_date > SYSDATE);
• Risk-configuration audit: SELECT p.name, p.risk_enabled, r.* FROM iby_payee p JOIN iby_risk_formulas r ON r.payeeid = p.payeeid;
• Payment method review: SELECT p.name, m.* FROM iby_payee p JOIN iby_accppmtmthd m ON m.mpayeeid = p.mpayeeid;
• Transaction summary reporting: SELECT p.name, s.* FROM iby_payee p JOIN iby_trxn_summaries_all s ON s.mpayeeid = p.mpayeeid;

These patterns support operational monitoring, reconciliation, and configuration verification for payment processing and funds capture.

Related Objects

The documented foreign key relationships identify the most significant dependents and parents of IBY_PAYEE.

• IBY_ECAPP — parent of IBY_PAYEE.ECAPPID; defines the electronic commerce application context.
• FND_SECURITY_GROUPS — parent of IBY_PAYEE.SECURITY_GROUP_ID; enforces data security.
• IBY_ACCPPMTMTHD — references IBY_PAYEE.MPAYEEID; stores accepted payment methods for the payee.
• IBY_BATCHES_ALL — references IBY_PAYEE.MPAYEEID; payment batches associated with the payee.
• IBY_ROUTINGINFO — references IBY_PAYEE.MPAYEEID; routing and transmission configuration.
• IBY_DEFAULT_BEP — references IBY_PAYEE.MPAYEEID; default bank entry point assignment.
• IBY_TRXN_SUMMARIES_ALL — references IBY_PAYEE.MPAYEEID; aggregated transaction history.
• IBY_PAYEE_SUBKEYS — references IBY_PAYEE.MPAYEE_ID; subkey definitions used for payee matching.
• IBY_MAPPINGS, IBY_RISK_FORMULAS, and the IBY_IRF_* risk tables — reference IBY_PAYEE.PAYEEID; define funds capture routing, risk scoring, and transaction limits.