Results for “delete_rpr_docs”

10 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FV_BE_FUND_PKG is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema that supports the Funds Capture and disbursement processing model within the Financials vertical. In the EBS 12.1.1 and 12.2.2 releases, the "FV" prefix designates the Funds Capture (formerly Payments) module, and the "BE" segment of the name indicates that this package belongs to the back-end processing layer rather than the user interface layer. The package encapsulates the core business logic required to build, validate, and persist fund capture transaction records, and it is documented under an API classification of OTHER, signifying it is a supporting internal component rather than a published, externally supported public API.

The package operates as the procedural engine behind batch and concurrent fund processing. It coordinates document-level processing across transaction headers, transaction details, and reported transaction staging tables, and it relies on the EBS logging and XLA (Subledger Accounting) infrastructure to record diagnostics and accounting events. Its status is VALID in the ETRM 12.2.2 registry, and it is referenced by two other database objects, confirming that it functions as a shared dependency within the FV module rather than as a terminal, self-contained utility.

Key Procedures and Functions

The documented package exposes six procedures and functions:

  • MAIN — The primary entry point that drives overall fund processing logic. It orchestrates the sequence of validation, document creation, and status updates performed by the package.
  • CONC_MAIN — The concurrent-program entry point. It wraps MAIN so that processing can be launched from a concurrent manager request, applying the standard concurrent program calling conventions and error handling.
  • PROCESS_DOCUMENT — Processes an individual fund capture document, applying the core business rules that transform staged data into committed transaction records.
  • UPDATE_DOC_STATUS — Maintains document status transitions, ensuring that processed documents reflect their current state consistently across the transaction tables.
  • DELETE_RPR_DOCS — Removes reported (RPR) documents, providing the cleanup path for staging or reported transaction records.
  • LOG_MESSAGE — Writes diagnostic and informational messages through the FND_LOG facility, supporting debugging and audit visibility.

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

  • FV_BE_RPR_TRANSACTIONS — The reported fund capture transactions staging table, central to document reporting and cleanup.
  • FV_BE_TRX_HDRS — Transaction headers, holding document-level fund capture data.
  • FV_BE_TRX_DTLS — Transaction details, holding line-level data associated with each header.
  • GL_BC_PACKETS — General Ledger balance/accounting packets used in the subledger accounting flow.
  • GL_LEDGERS — The ledger definition table, used to resolve ledger context for accounting and processing.
  • DUAL — Used for single-row scalar operations and validation queries.

It additionally references FND_GLOBAL, FND_LOG, FV_BE_XLA_PKG, and FV_UTILITY, which provide application context, logging, subledger accounting integration, and shared utility routines respectively.

Usage Notes

FV_BE_FUND_PKG is typically invoked indirectly rather than called directly by end users. Its CONC_MAIN procedure is designed for submission from the concurrent manager, making it the standard invocation path for scheduled or batch fund capture processing. Internal callers, including the two packages that reference it, invoke MAIN, PROCESS_DOCUMENT, UPDATE_DOC_STATUS, and DELETE_RPR_DOCS as part of larger fund processing flows. Since the object is classified as OTHER and is not a documented public API, customizations should avoid direct calls and instead treat it as an internal implementation detail subject to change. When troubleshooting, the LOG_MESSAGE procedure and the FND_LOG dependency provide the primary diagnostic trail. Because the package is not referenced by any database object at the top level but is referenced by two other packages, dependency analysis should be performed before any modification, particularly given its interaction with the XLA accounting engine.