Search Results fv_third_party_remit_pkg




Overview
Explore in AI Chat

Overview

The FV_THIRD_PARTY_REMIT_PKG package body in the APPS schema supports the Oracle EBS Third-Party Remittance (TPP) feature for U.S. federal financial management. Its role is to consolidate payment and invoice data so that a paying agency can remit amounts withheld or payable on behalf of another (third) party — for example, a buyer reimbursing a supplier's financing institution or a federal agency forwarding vendor payments to the Treasury. The package body is marked VALID and is classified as an OTHER API, indicating it is an internal engine invoked by concurrent processing rather than a published, externally callable interface.

In the 12.1.1 and 12.2.2 releases the package operates against the FV (Federal Financials) TPP tables alongside standard Payables tables. Its processing scope spans assigning payment records to third-party recipients, staging check-level details, and driving a concurrent program that builds the remittance extract.

Key Procedures and Functions

The ETRM 12.2.2 metadata documents a single procedure:

  • MAIN — The sole documented entry point and driver of the package. It orchestrates the third-party remittance run: reading selection and assignment data, resolving vendor and site information, calculating remittance amounts, staging results, and submitting or coordinating the extract. Because no parameter list is published in the metadata, the procedure should be treated as a concurrent-program driver whose inputs are passed through the concurrent request parameters and profile options rather than an explicit API signature.

No additional public functions or procedures are documented for this package body. Any further internal logic is private to the body and not exposed through the ETRM listing.

Tables Accessed

The package references the following tables (via APPS synonyms), each serving a distinct purpose in the remittance flow:

  • FV_TPP_ASSIGNMENTS and FV_TPP_ASSIGNMENTS_ALL — The core assignment tables that map payments or invoices to third-party recipients. These are the primary tables users search for when querying fv_tpp_assignments, and they determine which records the run processes.
  • FV_TPP_CHECK_DETAILS — Holds payment/check-level detail used to build the remittance records.
  • FV_THIRD_PARTY_TEMP — A staging table for intermediate results during the remittance build.
  • AP_CHECKS, AP_INVOICES, AP_INVOICE_PAYMENTS — Standard Payables tables supplying payment, invoice, and payment-to-invoice link data.
  • AP_INVOICE_SELECTION_CRITERIA — Defines the invoice selection rules applied when driving the run.
  • GL_LEDGERS — Supplies ledger context for the accounting entity.
  • DBMS_SQL — Used for dynamic SQL, typically for flexible selection or extraction logic.

Supporting dependencies include FND_CONCURRENT, FND_DATE, FND_LOG, FND_PROFILE, FND_REQUEST, FV_UTILITY, MO_GLOBAL, MO_UTILS, PO_VENDORS, and PO_VENDOR_SITES, which provide logging, profile retrieval, request submission, multi-org security, and vendor/site resolution.

Usage Notes

This package is not referenced by any other database object, confirming that it is an entry-point-level component rather than a shared library. It is typically invoked by the Third-Party Remittance concurrent program in the Federal Financials (FV) responsibility, and it should not be called directly from custom code because its procedure interface is unpublished. The presence of MO_GLOBAL and MO_UTILS indicates it is multi-org aware, so the correct operating unit must be set before execution. Users investigating assignments should query FV_TPP_ASSIGNMENTS and FV_TPP_ASSIGNMENTS_ALL to trace which records a given remittance run will select, and review the FND_LOG output for diagnostic detail when a run produces unexpected results.