Search Results fun_net_batches_all




Overview
Explore in AI Chat

Overview

FUN_NET_BATCHES_ALL is a transactional table owned by the FUN (Financials Common Modules) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores information about Netting Batches — the container records used by the Netting functionality to group payable and receivable transactions between trading partners and counterparties so that offsetting balances can be settled as a single net amount. Each row represents one netting batch, carrying the batch's identity, currency, status, settlement dates, exchange rate attributes, and the monetary total that results from the netting calculation.

The table operates as the header-level object of the netting process. Downstream activity, including settlement processing and accounting, is derived from batches defined here. The mined Data Vault classification for this object is standalone, meaning the heuristic model suggests treating it as an independent hub-style entity rather than a dependent satellite, although functional relationships to agreements and payment processes remain. In 12.2.2 the documented physical schema contains 43 columns, and the object holds VALID status.

Key Information Stored

The surrogate primary key is BATCH_ID, which is also the single documented unique-index business-key candidate (FUN_NET_BATCHES_ALL_U1). The most significant attributes are:

Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER) and twenty ATTRIBUTE columns plus ATTRIBUTE_CATEGORY provide auditing and extensibility, typically populated by the Oracle Applications Framework (OAF) Netting UI.

Common Use Cases and Queries

Typical uses include batch status reporting, settlement reconciliation, and payment-run verification. A common query pattern lists active batches for a given operating unit:

  • SELECT batch_id, batch_number, batch_name, batch_currency, batch_status_code, total_netted_amt, settlement_date FROM fun.fun_net_batches_all WHERE org_id = :p_org_id AND batch_status_code = 'APPROVED';
  • Joining to the payment run context: ... FROM fun_net_batches_all b, ap_inv_selection_criteria_all c WHERE b.checkrun_id = c.checkrun_id;
  • Currency exposure reporting by grouping on BATCH_CURRENCY and summing TOTAL_NETTED_AMT.
  • Audit/version checks using OBJECT_VERSION_NUMBER to detect concurrent updates from the OAF-based Netting screens.

Reports frequently filter on GL_DATE and SETTLEMENT_DATE to reconcile netting activity to the general ledger.

Related Objects

  • AP_INV_SELECTION_CRITERIA_ALL — referenced via FUN_NET_BATCHES_ALL.CHECKRUN_ID, tying batches to Payables payment batches.
  • FUN_NET_AGREEMENTS (AGREEMENT_ID) — the netting agreement defining counterparties and rules.
  • Netting batch transaction/detail tables in the FUN schema, which hold the individual transactions rolled into each batch.
  • Netting batch accounting and settlement tables that consume BATCH_ID to create downstream entries.
  • Oracle Payables payment APIs and the Netting OAF pages/BC4J entities that insert and update rows in this table.
  • Multi-org views over ORG_ID used for operating-unit–level reporting.