Search Results generate_net_batch




Overview
Explore in AI Chat

Overview

FUN_NET_CONC_PROG_PKG is a PL/SQL package in the APPS schema that supports the Oracle E-Business Suite netting functionality, part of the Oracle Financials product family. Netting allows an organization to consolidate receivable and payable balances across trading partners and legal entities, offsetting them, and settling the resulting net amount rather than processing gross payments in both directions. This package provides the concurrent-program entry points that drive a net batch through its full lifecycle, from creation through submission, settlement, and reversal. As reflected in its source header, the package dates to the earlier releases of the Financials family and remains present through EBS 12.1.1 and 12.2.2. Its API classification in ETRM 12.2.2 is OTHER, indicating it is an internal, program-oriented utility package rather than a formally published public API. It is referenced by no other packages, so its consumers are typically concurrent programs and forms rather than dependent PL/SQL code.

Key Procedures and Functions

The package exposes five documented procedures, each corresponding to a stage in the net batch life cycle. All are declared with the standard concurrent-program signature returning errbuf and retcode, plus a batch identifier that identifies the net batch being processed.

  • CREATE_NET_BATCH — Creates a net batch, establishing the batch header and assembling the underlying netting transactions for the specified batch identifier.
  • SUBMIT_NET_BATCH — Submits an existing net batch for processing. This is the procedure most commonly associated with the search term submit_net_batch and is the usual target of the net batch submission concurrent program.
  • SETTLE_NET_BATCH — Performs settlement of a submitted net batch, applying the netted balances and producing the settlement results expected by the downstream accounting and payment processes.
  • REVERSE_NET_BATCH — Reverses a net batch, backing out the effects of a previously processed batch so that the affected balances are restored.
  • GENERATE_NET_BATCH — Documented in the ETRM 12.2.2 metadata, this procedure supports generation of net batch data, working alongside CREATE_NET_BATCH in the batch-building stage.

No parameter lists are invented here; the documented procedure names and their errbuf/retcode/batch-id signature pattern define their usage.

Tables Accessed

The package operates against the core netting tables, accessed through APPS synonyms.

  • FUN_NET_BATCHES_ALL — The primary net batch table. It stores batch headers and is the source of the batch_id passed to every procedure in the package. Because it is an _ALL table, it is partitioned by operating unit or org, consistent with multi-org access control.
  • FUN_NET_BATCHES_S — The sequence/identifier table associated with the batches table, used to generate unique batch identifiers during creation and generation.
  • FUN_NET_AGREEMENTS_ALL — The netting agreements table. It defines the trading partner agreements and settlement rules that determine which transactions are eligible to be netted within a given batch.

Usage Notes

FUN_NET_CONC_PROG_PKG is normally invoked indirectly. In a standard EBS implementation, the procedures are registered as concurrent programs (for example, a net batch submission program calling SUBMIT_NET_BATCH) and are launched from the Netting responsibility's concurrent program and form interfaces. Users create and submit net batches through the relevant netting forms, and the form's underlying logic calls the corresponding procedure in this package. Because the procedures follow the standard errbuf/retcode convention, they can also be scheduled directly from the Concurrent Programs and Request Set frameworks, and can be called from custom PL/SQL code where a batch must be created, submitted, settled, or reversed programmatically. The package is not referenced by other packages, so it should be treated as an application-internal entry point rather than a reusable API; customizations should call it only with a valid batch_id from FUN_NET_BATCHES_ALL and should respect the same operating unit context under which the batch was created. Behavior is consistent across 12.1.1 and 12.2.2, as the package's interface has remained stable.