Results for “ext_payee_id”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
FV_TPP_ASSIGNMENTS_ALL is a Federal Financials (FV) table that defines third party assignments. In the Oracle E-Business Suite 12.1.1 / 12.2.2 data model, it functions as an intersection and execution table that associates suppliers, supplier sites, third party agents, and external payees with an effective date range. This enables an agency to direct a payment obligation owed to one supplier (the original supplier) to a different party — a third party agent or an external payee — for a defined period, typically to satisfy a federal assignment of claims, a garnishment, a factoring arrangement, or a similar legal redirection of funds.
Under a heuristic Data Vault classification, this table is satellite-leaning. It is not a pure hub because it does not define the business identity of a supplier or a payee; those are established in supplier and payee master tables. Nor is it a pure link, since it carries descriptive and temporal attributes. Instead it reads as a satellite hanging off the parties and payee keys, capturing the assignment relationship and its effective dating. This classification is a modeling suggestion only; the table itself is a conventional Oracle EBS transaction-support table within the FV schema.
Key Information Stored
The table contains 32 documented columns. The most significant are listed below.
- ASSIGNMENT_ID — the surrogate primary key, enforced by the unique index FV_TPP_ASSIGNMENTS_U1. This is the only documented business-key candidate and is the column other tables and APIs reference.
- ORIGINAL_SUPPLIER_ID and ORIGINAL_SUPPLIER_SITE_ID — identify the supplier and supplier site to whom the obligation was originally owed. These are the "assignor" keys.
- THIRD_PARTY_AGENT_ID and THIRD_PARTY_SITE_ID — identify the third party agent and site receiving or facilitating the assignment, forming the "assignee" side of the relationship.
- EXT_PAYEE_ID — foreign key to IBY_EXTERNAL_PAYEES_ALL, identifying the external payee to whom payment is directed.
- EXT_BANK_ACCOUNT_ID — foreign key to IBY_EXT_BANK_ACCOUNTS, identifying the external bank account used for disbursement.
- START_DATE and END_DATE — the effective dating of the assignment, used to determine whether the assignment is active for a given payment date.
- ORG_ID — the operating unit that owns the assignment record, supporting multi-org security and reporting.
- SET_OF_BOOKS_ID — the ledger context in which the assignment applies.
- CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard who-columns used for audit and change tracking.
- ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard descriptive flexfield columns available for agency-specific extension of the assignment record.
Common Use Cases and Queries
Typical uses include identifying the active third party assignment for a supplier at the time a payment is processed, reconciling assignments to external payees and bank accounts, and auditing expiring or expired assignments. A common query pattern joins the assignment to the external payee master on the EXT_PAYEE_ID foreign key:
- List active assignments for a supplier: filter on ORIGINAL_SUPPLIER_ID where SYSDATE between START_DATE and END_DATE.
- Resolve the payee and bank account: join FV_TPP_ASSIGNMENTS_ALL to IBY_EXTERNAL_PAYEES_ALL on EXT_PAYEE_ID and to IBY_EXT_BANK_ACCOUNTS on EXT_BANK_ACCOUNT_ID.
- Reporting by operating unit or ledger: group by ORG_ID and SET_OF_BOOKS_ID to summarize assignments for multi-org and multi-ledger environments.
- Effective-date validation: report assignments whose END_DATE is approaching to trigger renewal or termination review.
Related Objects
- IBY_EXTERNAL_PAYEES_ALL — referenced via FV_TPP_ASSIGNMENTS_ALL.EXT_PAYEE_ID; defines the external payee receiving payment.
- IBY_EXT_BANK_ACCOUNTS — referenced via FV_TPP_ASSIGNMENTS_ALL.EXT_BANK_ACCOUNT_ID; defines the disbursement bank account.
- AP_SUPPLIERS and AP_SUPPLIER_SITES_ALL — supply the original supplier and third party agent identities used in the assignment.
- FV_TPP_ASSIGNMENTS_U1 — the unique index on ASSIGNMENT_ID that enforces the primary key.
Because the metadata for downstream dependents is limited, additional references to FV_TPP_ASSIGNMENTS_ALL from payment or invoice processing logic should be confirmed against the specific deployment's foreign key definitions in FV and AP.
-
Defines the third party assignments
-
View: FV_TPP_ASSIGNMENTS_V 12.1.1
Payables(AP) will join with this view to provide third party information to Payments(IBY).
APPS.FV_TPP_ASSIGNMENTS_V·↳ AP_SUPPLIERS·↳ AP_SUPPLIER_SITES_ALL·↳ FND_PROFILE·Explore FV module →
-
View: IBY_PAYMENTS_SEC_V 12.2.2
APPS.IBY_PAYMENTS_SEC_V·↳ CE_SECURITY_PROFILES_V·↳ FND_ACCESS_CONTROL_UTIL·↳ FND_GLOBAL·Explore IBY module →
-
View: IBY_DOCS_PAYABLE_SEC_V 12.2.2
APPS.IBY_DOCS_PAYABLE_SEC_V·↳ CE_SECURITY_PROFILES_V·↳ FND_ACCESS_CONTROL_UTIL·↳ FND_GLOBAL·Explore IBY module →
-
"This table contains records of the documents payable which are updated by system while processing 'Build payments' program. IBY_DOCS_PAYABLE_ALL stores Oracle Payments' representation of source products' documents payable. A document pay
-
View: IBY_PAYMENTS_SEC_V 12.1.1
APPS.IBY_PAYMENTS_SEC_V·↳ CE_SECURITY_PROFILES_V·↳ FND_ACCESS_CONTROL_UTIL·↳ FND_GLOBAL·Explore IBY module →
-
View: FV_TPP_ASSIGNMENTS_V 12.2.2
Payables(AP) will join with this view to provide third party information to Payments(IBY).
APPS.FV_TPP_ASSIGNMENTS_V·↳ AP_SUPPLIERS·↳ AP_SUPPLIER_SITES_ALL·↳ FND_PROFILE·Explore FV module →
-
View: IBY_EXTERNAL_PAYEES_V 12.2.2
APPS.IBY_EXTERNAL_PAYEES_V·↳ IBY_EXTERNAL_PAYEES_ALL·Explore IBY module →
-
IBY_DOCUMENTS_PAYABLE_H stores historical snapshots of documents payable. This table contains denormalized versions of documents payable from specific points in time, such as when the payment for this document was submitted to a payment sys
-
Defines the third party assignments
-
View: IBY_FD_PAYMENTS_V 12.1.1
APPS.IBY_FD_PAYMENTS_V·↳ IBY_FD_EXTRACT_GEN_PVT·↳ IBY_PAYMENTS_ALL·↳ IBY_PAY_INSTRUCTIONS_ALL·Explore IBY module →
-
IBY_PAYMENTS_H table stores historical snapshots of payments. This table contains denormalized versions of payments from specific points in time, including when the payment was submitted to a payment system. Different snapshots of the same
-
View: IBY_FD_PAYMENTS_V 12.2.2
APPS.IBY_FD_PAYMENTS_V·↳ IBY_FD_EXTRACT_GEN_PVT·↳ IBY_PAYMENTS_ALL·↳ IBY_PAY_INSTRUCTIONS_ALL·Explore IBY module →
-
View: IBY_EXTERNAL_PAYEES_V 12.1.1
APPS.IBY_EXTERNAL_PAYEES_V·↳ IBY_EXTERNAL_PAYEES_ALL·Explore IBY module →
-
"This table contains payment details of an external payee automatically created by the source product. For example when supplier or supplier site is created manually system automatically inserts row in to the IBY_EXTERNAL_PAYEES_ALL table.
-
View: IBY_FD_DOCS_PAYABLE_V 12.2.2
APPS.IBY_FD_DOCS_PAYABLE_V·↳ IBY_DOCS_PAYABLE_ALL·Explore IBY module →
-
View: IBY_FD_DOCS_PAYABLE_V 12.1.1
APPS.IBY_FD_DOCS_PAYABLE_V·↳ IBY_DOCS_PAYABLE_ALL·Explore IBY module →
-
View: IBY_DOCS_PAYABLE_SEC_V 12.1.1
APPS.IBY_DOCS_PAYABLE_SEC_V·↳ CE_SECURITY_PROFILES_V·↳ FND_ACCESS_CONTROL_UTIL·↳ FND_GLOBAL·Explore IBY module →
-
"This table contains records of the payments which are created by system while processing 'Build payments' program. A payment can be a single check or an electronic fund transfer between first party payer and third party payee. A row in
-
VIEW: APPS.POS_BANK_MERGE_V 12.2.2
-
VIEW: APPS.POS_BANK_MERGE_V 12.2.2