Search Results fun_net_extract_pkg




Overview
Explore in AI Chat

Overview

FUN_NET_EXTRACT_PKG is an APPS-owned PL/SQL package body classified under the ETRM "OTHER" API category. It supports Oracle E-Business Suite's netting functionality, in which payables and receivables obligations between related trading partners are offset to arrive at a single net settlement position. The package is the extraction engine for that process: it gathers invoice, customer transaction, agreement, and batch data from the underlying netting and subledger tables and writes the results out for downstream processing, typically as a flat file through the FND_FILE utility. Users searching for "fun_net_agreements" will encounter this package because it is one of the principal consumers of the FUN_NET_AGREEMENTS and FUN_NET_AGREEMENTS_ALL tables, which hold the netting agreements that govern which counterparties and transactions participate in a given netting cycle.

Key Procedures and Functions

The documented interface exposes a single callable unit:

  • EXTRACT_DATA — The sole documented procedure in the package. It performs the extraction itself, selecting the eligible netting transactions and agreement information and emitting the resulting data set, conventionally to a concurrent-program output file via FND_FILE. No parameter list is defined in the available metadata, so its exact signature is not reproduced here; callers should inspect the package specification in the target instance (12.1.1 or 12.2.2) before invoking it directly.

Tables Accessed

The package references a broad set of netting and subledger objects through APPS synonyms:

Usage Notes

FUN_NET_EXTRACT_PKG is a backend extraction routine rather than a user-facing API. It is most plausibly invoked from the Oracle Netting concurrent program set, where EXTRACT_DATA is executed to produce the extract file consumed by the netting settlement process, and it may also be called from custom code that requires netting agreement, batch, and transaction data in a standardized output form. Because EXTRACT_DATA depends on operating unit, ledger, and agreement selection, invocations must supply or inherit the appropriate context; running it outside the intended netting cycle can produce incomplete or irrelevant output. The package is not referenced by any other database object, confirming that it sits at the top of its call chain, and its VALID status indicates it is compiled and operational in the documented environment. Implementations upgraded between 12.1.1 and 12.2.2 should verify the package specification locally, since the ETRM extract lists only the procedure name and no formal parameter signature.