Search Results fv_cross_doc_ref




Overview
Explore in AI Chat

Overview

FV_CROSS_DOC_REF is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that supports cross-document referencing within the Federal Financials (FV) module. Its principal role is to establish and resolve the relationships between documents that originate in different Oracle EBS sub-ledgers — specifically Accounts Payable, Purchasing, and Receiving — so that a complete audit trail can be maintained from a payment or invoice back to the underlying procurement and receipt transactions. In public sector and federal accounting environments, this linkage is essential because appropriations, commitments, obligations, and outlays must be traceable across the acquisition lifecycle. The package carries a status of VALID in both 12.1.1 and 12.2.2, and it is classified under ETRM as an OTHER API rather than a published open interface, indicating that it is intended primarily for internal consumption by other Oracle processes.

Key Procedures and Functions

The ETRM metadata documents a single entry point for this package:

  • MAIN — The documented procedure that drives the package's cross-document reference processing. It orchestrates the logic that reads source documents and populates the cross-reference data used by Federal Financials reporting and reconciliation. Because the metadata does not publish a parameter list, its signature should not be assumed; callers referencing this API should confirm the actual specification in the database before use.

Tables Accessed

The package reads from a broad set of AP, PO, and RCV tables via APPS synonyms, reflecting its role as a cross-module integrator:

Usage Notes

FV_CROSS_DOC_REF is invoked internally by Oracle Federal Financials processing rather than by end users directly. It is typically called from concurrent programs and other FV packages that require document lineage, particularly during payment matching, invoice-to-purchase-order reconciliation, and receipt-based accrual processing. The ETRM records indicate the package is referenced by zero other packages, which suggests that in the documented configuration its MAIN procedure is called from external drivers such as concurrent program logic or forms rather than through package-to-package invocation. Customizations that require cross-document tracing should treat FV_CROSS_DOC_REF as an internal dependency: validate signatures against the live database before calling it, avoid modifying the package, and prefer supported public APIs where they exist. Because there is no published parameter list in the ETRM metadata, integrators should not hard-code arguments based on assumption.