Search Results fun_net_customers_all




Overview

FUN_NET_CUSTOMERS_ALL is a transactional table in the FUN (Financials Common Modules) product of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It stores information about the Customers that are included in a Netting Agreement. In the Oracle Netting workflow, counterparties with mutual receivable and payable balances are grouped under a netting agreement so that offsetting settlements can be calculated and applied. This table holds the association between a given netting agreement and the customer accounts (and optionally customer site uses) that participate in that agreement.

The table is owned by the FUN schema and is documented as VALID, with 33 physical columns in the ETRM 12.2.2 schema. Based on the foreign key structure mined from the data model, the heuristic Data Vault classification for this table is standalone. In Data Vault terms, this suggests the table functions primarily as a link or association record rather than a full hub or satellite; it carries the identifying key for the row along with the relationship it represents, without being the master source of customer or agreement master data. This classification should be treated as a modeling suggestion only, not as an authoritative architectural ruling.

Key Information Stored

The table is keyed by a surrogate primary key and a unique business-key candidate. The unique index FUN_NET_CUSTOMERS_U1 is defined on NETTING_CUSTOMER_ID, which serves as the primary identifier for each row in this table.

  • NETTING_CUSTOMER_ID — Surrogate primary key; the unique business-key candidate enforced by FUN_NET_CUSTOMERS_U1.
  • AGREEMENT_ID — Identifies the netting agreement to which the customer is linked.
  • CUST_ACCOUNT_ID — Foreign key to HZ_CUST_ACCOUNTS; the customer account included in the netting agreement.
  • CUST_SITE_USE_ID — Optional reference to the customer site use, allowing netting at the site level rather than the account level.
  • CUST_PRIORITY — Ordering or precedence value for the customer within the agreement.
  • ORG_ID — Operating unit (multi-org) identifier, supporting partitioned access by business unit.
  • OBJECT_VERSION_NUMBER — Optimistic locking column used by the ORM layer.
  • CREATION_DATE, CREATED_BY — Who created the record and when.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Audit trail of the last modification.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE20 — Descriptive flexfield (DFF) columns for extensibility without schema change.

The surrogate key (NETTING_CUSTOMER_ID) is distinct from the business-relationship columns (AGREEMENT_ID, CUST_ACCOUNT_ID, CUST_SITE_USE_ID), which together describe the actual netting participation.

Common Use Cases and Queries

Typical usage involves reporting the customers participating in a netting agreement, validating agreement composition, and driving netting calculations. A common query joins the table to HZ_CUST_ACCOUNTS to resolve the customer name:

  • List all customers for a given agreement: SELECT nc.netting_customer_id, nc.cust_account_id, nc.cust_priority FROM fun.fun_net_customers_all nc WHERE nc.agreement_id = :agreement_id ORDER BY nc.cust_priority;
  • Join to the customer master: SELECT ha.account_number, ha.customer_name, nc.cust_priority FROM fun.fun_net_customers_all nc JOIN hz.hz_cust_accounts ha ON ha.cust_account_id = nc.cust_account_id WHERE nc.agreement_id = :agreement_id;
  • Operating-unit filtered reporting using ORG_ID to satisfy multi-org security.
  • Identifying site-level versus account-level netting by checking whether CUST_SITE_USE_ID is populated.
  • Extensibility reporting on ATTRIBUTE1–ATTRIBUTE20 and ATTRIBUTE_CATEGORY where clients have configured DFF segments.

Related Objects

The FK metadata identifies HZ_CUST_ACCOUNTS as the principal referenced table; the broader netting model and multi-org infrastructure provide additional dependencies.

  • HZ_CUST_ACCOUNTS — Referenced via cust_account_id (the only documented foreign key).
  • FUN_NET_AGREEMENTS_ALL — The parent netting agreement header referenced through agreement_id in the FUN netting model.
  • HZ_CUST_SITE_USES_ALL — Referenced conceptually through cust_site_use_id for site-level netting.
  • HZ_PARTIES — Upstream party master reached through HZ_CUST_ACCOUNTS.
  • FUN_NET_ASSIGNMENTS / netting lines — Downstream tables that consume the customer participation defined here.
  • ORG_ORGANIZATION_DEFINITIONS — Supports the ORG_ID operating unit values.
  • FND_API / ORM framework — Interacts with OBJECT_VERSION_NUMBER and the standard WHO columns maintained by Oracle Application Object Library.