Results for “iby_payee_payeeid_u1”

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

Overview

IBY.IBY_PAYEE is a foundational Oracle E-Business Suite payments table that stores a single row for each payee registered at a site, including billers, merchants, and stores served by the electronic commerce and payment processing framework. In Oracle EBS 12.1.1 and 12.2.2, it acts as the master registry that links an internal system-generated payee identity to externally supplied identifiers used by electronic commerce applications. The table resides in the APPS_TS_TX_DATA tablespace, carries FND Design Data ownership under IBY.IBY_PAYEE, and is documented as VALID in the ETRM repository.

Under a heuristic Data Vault classification mined from its foreign key structure, IBY_PAYEE is best modeled as a hub. It holds stable business identity keys, notably PAYEEID and MPAYEEID, with relatively few descriptive attributes and numerous downstream references, which is characteristic of a hub that satellites and links would surround.

Key Information Stored

The documented physical schema contains 27 columns, of which the following are most consequential:

• MPAYEEID (NUMBER 15) — the system-generated payee identifier. Documented as the primary key (IBY_PAYEE_PK) and enforced by the unique index IBY_PAYEE_MPAYEEID_U2.
• PAYEEID (VARCHAR2 80) — the payee identifier passed by the electronic commerce application. Enforced by the unique index IBY_PAYEE_PAYEEID_U1, which is the index associated with the user's search term.
• NAME (VARCHAR2 80) — the display name of the payee.
• ECAPPID (NUMBER 15) — identifies the electronic commerce application that owns the payee; foreign key to IBY_ECAPP.
• USERNAME and PASSWORD — credentials used for payee authentication.
• ACTIVESTATUS — Y/N flag indicating whether the merchant is active.
• RISK_ENABLED, THRESHOLD, and SUPPORTEDOP — risk management configuration and the bit-map of operations the payee supports.
• MCC_CODE — merchant category code where applicable.
• SECURITY_GROUP_ID — used in hosted environments; foreign key to FND_SECURITY_GROUPS.
• INACTIVE_DATE and SECURITY_ENABLED — lifecycle and security state flags.
• OBJECT_VERSION_NUMBER plus the standard WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) — concurrency control and audit trail.

The distinction between the surrogate key (MPAYEEID) and the business-key candidates (PAYEEID, and separately MPAYEEID via its unique index) is central to any integration design.

Common Use Cases and Queries

Typical scenarios include resolving an external payee reference to its internal identity, listing active merchants for a given electronic commerce application, and auditing risk configurations.

SELECT p.MPAYEEID, p.PAYEEID, p.NAME, p.ACTIVESTATUS
FROM   IBY.IBY_PAYEE p
WHERE  p.PAYEEID = :p_payee_id;

SELECT p.MPAYEEID, p.NAME, p.RISK_ENABLED, p.THRESHOLD
FROM   IBY.IBY_PAYEE p, IBY.IBY_ECAPP e
WHERE  p.ECAPPID = e.ECAPPID
AND    p.ACTIVESTATUS = 'Y';

Reporting use cases often join IBY_PAYEE to transaction summary and routing tables to attribute payment volumes to a payee, or to risk formula tables to validate configured limits.

Related Objects

The following dependent objects are the most significant for integration and query design:

• IBY_ECAPP — referenced by IBY_PAYEE.ECAPPID; defines the owning application.
• FND_SECURITY_GROUPS — referenced by IBY_PAYEE.SECURITY_GROUP_ID.
• IBY_ROUTINGINFO and IBY_DEFAULT_BEP — reference MPAYEEID for payment routing and default bank entry point configuration.
• IBY_BATCHES_ALL and IBY_TRXN_SUMMARIES_ALL — reference MPAYEEID for batch and transaction summary aggregation.
• IBY_FNDCPT_PAYEE_APPL and IBY_ACCPPMTMTHD — reference MPAYEEID for payee-application and payment method mappings.
• IBY_RISK_FORMULAS and the IBY_IRF_* tables (IBY_IRF_PMT_AMOUNT, IBY_IRF_PMT_FREQUENCY, IBY_IRF_TRXN_AMT_LIMIT) — reference PAYEEID for risk rule configuration.
• IBY_MAPPINGS and IBY_PAYEE_SUBKEYS — reference PAYEEID and MPAYEE_ID respectively for external key mapping and subkey storage.