Search Results fv_treasury_confirmations




Overview

FV_TREASURY_PAYMENTS_PKG is the Treasury Payments processing package in the Oracle E-Business Suite Treasury module. It is owned by APPS and is classified as an "OTHER" API, meaning it is not a formally published public interface but is instead an internal engine invoked by Treasury confirmation processing flows. Its principal purpose is to create and manage treasury payment events arising from treasury confirmations — the instruments by which Treasury records the settlement of obligations against Oracle Payables payments and checks.

The package body carries a fixed module identifier of fv.plsql.fv_treasury_payments_pkg and maintains package-level globals for the ledger, operating unit, treasury confirmation, accounting date, payment instruction, checkrun name, and DIT flag. Logging is performed through FND_LOG at statement level, with debug messages routed to FV_UTILITY.DEBUG_MESG. Error status is tracked in module state (x_err_code, x_err_stage) and returned to callers through NOCOPY OUT parameters rather than raised exceptions.

Key Procedures and Functions

The documented interface exposes two procedures, MAIN and VOID, with additional internal routines that support the overall processing model.

  • MAIN — The primary entry point. It accepts a treasury confirmation identifier and a button-name argument, sets a SAVEPOINT FV_TREAS, initializes module state, and dispatches the appropriate business action (confirmation or backout) based on the supplied button. It returns an error buffer and return code in the standard concurrent-program convention.
  • VOID — Handles void processing for treasury payment records, including the capture of voided checks and the related reversal of payment history.
  • CREATE_TREASURY_PAYMENT_EVENT — Creates a treasury payment event for a given event type and treasury confirmation identifier, returning status and return code.
  • DO_CONFIRM_PROCESS — Executes the confirmation path, generating and validating payment instructions associated with the confirmation.
  • DO_BACKOUT_PROCESS — Reverses a previously confirmed treasury payment, restoring prior state.
  • GET_OPEN_PERIOD — Resolves an open accounting period for the accounting date passed in, adjusting the date in place (NOCOPY IN OUT) so downstream processing posts to a valid open period. This routine carries a forward declaration referencing Bug 5727409, indicating its role in correcting period determination during payment creation.

Tables Accessed

The package reads and writes treasury and Payables tables through APPS synonyms. Treasury confirmations are managed via FV_TREASURY_CONFIRMATIONS and FV_TREASURY_CONFIRMATIONS_ALL, with offset and check-range configuration in FV_TC_OFFSETS and FV_TREASURY_CHECK_RANGES. Void handling uses FV_VOIDED_CHECKS and FV_VOIDED_CHECKS_S. Operating unit attributes, including the DIT flag, are read from FV_OPERATING_UNITS. Payables integration uses AP_CHECKS and AP_CHECKS_ALL for check records, AP_CHECKS_ALL and AP_PAYMENT_HISTORY_ALL for checkrun names, AP_INVOICE_PAYMENTS_ALL and AP_PAYMENT_HISTORY for payment detail, AP_PAYMENT_PROGRAMS and AP_INV_SELECTION_CRITERIA_ALL for payment program context, and GL_INTERFACE for accounting entries generated against the resolved open period.

Usage Notes

FV_TREASURY_PAYMENTS_PKG is invoked from the Treasury confirmation user interface and from concurrent processing rather than called directly by customer code. The MAIN procedure follows the concurrent-program parameter contract (errbuf, retcode, treasury confirmation id, button name), which allows it to be registered against a host form or program. Because the package is classified as OTHER and is referenced by no other documented packages, it should be treated as an internal implementation detail; customizations should avoid direct calls and instead rely on the supported Treasury confirmation and Payables payment flows. Any extension should preserve the NOCOPY OUT status convention and account for the period-resolution behaviour of GET_OPEN_PERIOD when posting to GL_INTERFACE.