Search Results iby_ext_payee_relationships_pk

Overview

IBY_EXT_PAYEE_RELATIONSHIPS is a transactional table in the IBY (Payments) schema that stores third-party payment relationships and their associated attributes. It captures relationships that are entered manually through the Relationship region on the supplier page in Oracle E-Business Suite. Each row represents a defined payment relationship between a party or supplier site and a remit-to party or remit-to supplier site, together with effective dating, a primary indicator, and descriptive flexfield context. The object is documented in ETRM 12.2.2 with the owner IBY and 32 columns, and is present in both 12.1.1 and 12.2.2 environments.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure is standalone. Because no dependent hub or link relationships were mined, this table is best treated as an independent entity rather than a hub, link, or satellite. Modelers should therefore key it by its own surrogate identifier and treat the party and supplier site references as business attributes rather than as enforced parent relationships.

Key Information Stored

The surrogate primary key is RELATIONSHIP_ID, enforced by the IBY_EXT_PAYEE_RELATIONSHIPS_PK constraint. The remaining documented columns fall into several functional groups.

• Relationship participants: PARTY_ID and SUPPLIER_SITE_ID identify the source party and supplier site; REMIT_PARTY_ID and REMIT_SUPPLIER_SITE_ID identify the corresponding remit-to party and remit-to supplier site. Together these are the principal business-key candidates for the relationship.
• Effective dating: FROM_DATE and TO_DATE define the validity window of the relationship, supporting date-ranged queries and historical tracking.
• Ranking and status: PRIMARY_FLAG marks whether the relationship is the primary one for the party or site, while ACTIVE indicates whether the row is currently in use.
• Descriptive data: ADDITIONAL_INFORMATION holds free-form text supplied during manual entry.
• Flexfield support: ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 provide the standard descriptive flexfield context and segment columns.
• Audit and concurrency: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER provide the standard Oracle audit trail and optimistic locking column.

Common Use Cases and Queries

Typical scenarios include verifying the remit-to party assigned to a supplier site, reporting on all third-party payment relationships active as of a given date, and identifying relationships that have been superseded or terminated. A common pattern joins the source and remit participants in a single query:

• SELECT relationship_id, party_id, supplier_site_id, remit_party_id, remit_supplier_site_id, from_date, to_date, primary_flag FROM iby.iby_ext_payee_relationships WHERE active = 'Y'
• Point-in-time extraction: WHERE SYSDATE BETWEEN from_date AND NVL(to_date, SYSDATE)
• Primary relationship lookup: WHERE primary_flag = 'Y' AND party_id = :party_id
• Audit reporting on recently changed relationships using LAST_UPDATE_DATE, CREATED_BY, and LAST_UPDATED_BY.

Because the table is populated manually through the supplier page, reconciliation queries are frequently used to confirm that payment processing uses the expected remit-to party for each supplier site.

Related Objects

Although the mined metadata classifies this table as standalone, the following objects are the most significant points of integration and reference:

• IBY_EXT_PAYEES — the payee extension table; join on PARTY_ID and supplier site identifiers to link a relationship to its extended payee record.
• IBY_PAYEE_RELATIONSHIPS — the base payee relationship table, the primary logical counterpart for relationship validation.
• HZ_PARTIES — join on PARTY_ID and REMIT_PARTY_ID to resolve participant names.
• HZ_PARTY_SITES — join on SUPPLIER_SITE_ID and REMIT_SUPPLIER_SITE_ID to resolve site addresses.
• POZ_SUPPLIER_SITES_ALL — supplier site definitions used as the source of supplier site identifiers.
• IBY_PAYMENT_INSTRUCTIONS and IBY_EXTERNAL_PAYEES_ALL — payment-processing objects that consume the remit-to assignments established by these relationships.