Search Results fun_net_customers_u1

Overview

FUN.FUN_NET_CUSTOMERS_ALL is a transactional table in the Oracle E-Business Suite Financials (FUN) schema that stores the association between customers and the netting agreements they participate in. In Oracle EBS release 12.1.1 and 12.2.2, this table is a core component of the Treasury Netting functionality used to consolidate receivables and payables across trading partners, thereby reducing the number of physical settlements and foreign exchange exposures. Each row represents a single customer's inclusion in a specific netting agreement, together with priority ranking and optional site-level specification. The table is registered in FND Design Data as FUN.FUN_NET_CUSTOMERS_ALL and carries a status of VALID.

From a Data Vault modeling perspective, the mined dependency classification for this object is standalone. Heuristically, this suggests the table may be modeled as a link or an associative construct that resolves a many-to-many relationship between netting agreements and customer accounts. It is not a pure reference hub, since it carries its own surrogate identifier and transactional attributes such as priority.

Key Information Stored

The primary surrogate key is NETTING_CUSTOMER_ID, a NUMBER(15) column that uniquely identifies each netting customer record. It is enforced by the unique index FUN_NET_CUSTOMERS_U1, which is the sole business-key candidate documented for this table. Users searching for "fun_net_customers_u1" are typically looking for this constraint when diagnosing duplicate-key errors, trace or ORA-00001 violations, or when writing ad-hoc joins.

Other columns essential to interpreting a row include:

• AGREEMENT_ID — identifies the parent netting agreement; indexed by FUN_NET_CUSTOMERS_N1 along with the account and site columns.
• CUST_ACCOUNT_ID — the customer account referenced, with a foreign key to HZ_CUST_ACCOUNTS.
• CUST_SITE_USE_ID — optionally narrows the participation to a specific customer site use.
• CUST_PRIORITY — controls ordering or precedence when customers appear in multiple agreements.
• ORG_ID — the Multi-Org operating unit that owns the record.
• OBJECT_VERSION_NUMBER — supports optimistic locking in the associated OAF/BC4J application layer.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard Who columns for audit and change tracking.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE20 — descriptive flexfield storage for client-specific extensions.

Common Use Cases and Queries

Typical usage includes listing the customers participating in a given netting agreement, identifying which agreements a customer account belongs to, and ordering customers by priority for settlement processing.

• Agreement membership report: select agreement_id, cust_account_id, cust_site_use_id, cust_priority from fun_net_customers_all where agreement_id = :agreement_id order by cust_priority.
• Customer-to-agreement lookup: join on cust_account_id to hz_cust_accounts to retrieve the customer name alongside agreement membership.
• Duplicate detection: query grouping by agreement_id, cust_account_id, and cust_site_use_id to find records that collide with FUN_NET_CUSTOMERS_U1 during concurrent inserts.
• Audit and reconciliation: filter on last_update_date and org_id to identify records modified in a period for a given operating unit.

Related Objects

• HZ_CUST_ACCOUNTS — referenced by CUST_ACCOUNT_ID; provides the customer identity used in netting.
• HZ_CUST_SITE_USES_ALL — the logical parent of CUST_SITE_USE_ID, supplying the site-level context.
• FUN_NET_AGREEMENTS_ALL — the netting agreement header referenced by AGREEMENT_ID.
• FUN_NET_CUSTOMERS_U1 — the unique index enforcing the primary business key on NETTING_CUSTOMER_ID.
• FUN_NET_CUSTOMERS_N1 — the non-unique index supporting lookups by agreement, account, and site.
• FUN_NET_AGREEMENTS_ALL processing and settlement routines in the Treasury Netting modules that consume customer-priority ordering.