Results for “iby_fndcpt_payee_appl”

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

Overview

IBY_FNDCPT_PAYEE_APPL is a mapping table in the Oracle Payments (IBY) module of Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. It records the association between internal payees and operating units (business units / orgs). The cardinality is deliberately asymmetric: a single internal payee may be linked to many operating units, while any given operating unit may be associated with at most one payee. This design makes the table the authoritative source for determining which payee record a payment process should use when a transaction originates from a specific operating unit.

The table is owned by the IBY schema and holds nine documented columns. It is a low-volume, high-value configuration table rather than a transactional ledger; its rows change relatively infrequently and are typically maintained during implementation or when organizational structures change.

From a Data Vault modeling perspective, the ETRM metadata classifies this object heuristically as satellite-leaning. This is a modeling suggestion rather than a physical property: the table carries descriptive attributes and effective associations rather than acting as a pure hub of business keys or a pure many-to-many link. Analysts building a warehouse layer should treat it as an attribute-bearing relationship construct anchored to the payee hub.

Key Information Stored

The most significant columns are the following:

• MPAYEEID — The internal payee identifier. This is the foreign key to IBY_PAYEE and the primary linkage column of the table.
• ORG_TYPE — Classifies the type of operating unit referenced, distinguishing the organizational construct being mapped.
• ORG_ID — The operating unit identifier to which the payee is assigned.
• CREATED_BY, CREATION_DATE — Standard WHO audit columns recording who inserted the mapping and when.
• LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard WHO audit columns recording the most recent modification.
• LAST_UPDATE_LOGIN — The login session associated with the last update.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Applications framework to detect concurrent updates.

The business-key candidate is documented through the unique index IBY_FNDCPT_PAYEE_APPL_U1, defined over (ORG_TYPE, ORG_ID). This enforces the rule that an operating unit can be tied to at most one payee. Note that the uniqueness is expressed on the org-side columns, not on MPAYEEID, which is consistent with the one-payee-to-many-orgs relationship. The payee-side key MPAYEEID is captured as a foreign key rather than part of the unique constraint. Auditing columns and OBJECT_VERSION_NUMBER are framework-managed and should not be treated as business identifiers.

Common Use Cases and Queries

Typical scenarios include resolving the payee for a given operating unit during payment processing, validating that a payee is properly configured across business units, and auditing payee assignments after a reorganization.

A representative query to find the payee for an operating unit:

• SELECT p.payee_name, a.mpayeeid, a.org_id FROM iby.iby_fndcpt_payee_appl a JOIN iby.iby_payee p ON p.payee_id = a.mpayeeid WHERE a.org_id = :org_id;

A query to list all operating units mapped to a single payee:

• SELECT a.org_type, a.org_id FROM iby.iby_fndcpt_payee_appl WHERE a.mpayeeid = :payee_id;

Reporting use cases include reconciliation of payee-to-business-unit coverage, exception reporting for operating units with no assigned payee, and impact analysis before merging or retiring a payee. Because the unique index is on (ORG_TYPE, ORG_ID), queries filtering by operating unit benefit from that index, while queries filtering only by MPAYEEID rely on the foreign key index.

Related Objects

The following objects are most significant in relation to IBY_FNDCPT_PAYEE_APPL:

• IBY_PAYEE — The parent payee table, joined via IBY_FNDCPT_PAYEE_APPL.MPAYEEID = IBY_PAYEE.PAYEE_ID. This is the documented foreign key relationship.
• HR_OPERATING_UNITS — Supplies the operating unit definition referenced by ORG_ID.
• IBY_FNDCPT_PAYER — Payer-side configuration that, together with payee mappings, shapes payment processing for a business unit.
• IBY_PAYMENT_INSTRUCTION — Payment instructions that depend on a resolved payee for the originating operating unit.
• IBY_FNDCPT_PAYEE_APPL related views and Payables/Receivables payee lookups that join through the payee and org identifiers.
• The Oracle Payments payee and payer application programming interfaces, which read and maintain these mappings programmatically.

Together these objects connect organizational structure in EBS to the Payments engine, making IBY_FNDCPT_PAYEE_APPL a critical configuration bridge for correct payee resolution at transaction time.