Search Results gl_fusion_transfer_pkg




Overview
Explore in AI Chat

Overview

APPS.GL_FUSION_TRANSFER_PKG is a server-side PL/SQL package in Oracle E-Business Suite General Ledger that supports the transfer of Oracle Fusion General Ledger data into the EBS environment, most commonly in the context of a coexistence or consolidation scenario where a Fusion ledger must be reconciled or reported alongside an EBS ledger. The package header is defined with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoker rather than its owner, a standard pattern for public APIs in Oracle EBS that depend on the calling user's access set and security context.

The package exposes both a business-level transfer API and a set of BI Publisher callback routines. Its primary unit of work is a "Fusion transfer" that moves balances and associated ledger data from a source Fusion ledger into interface and staging structures within EBS. The package also includes a purge routine to remove previously transferred data, providing a controlled lifecycle for the staged records.

Critically for users searching on p_from_period_name, this parameter is central to how the transfer is scoped. It is also surfaced in the BI Publisher parameter set as p_bi_from_period_name, indicating that the same period selection logic drives both the batch transfer and its associated report output.

Key Procedures and Functions

  • DO_TRANSFER — The main procedure of the Fusion transfer. It accepts standard concurrent program parameters (p_errbuf and p_retcode) plus the ledger identifier pair (p_from_ledger_shortname, p_from_ledger_id), the transfer mode, the from-period name, an access set identifier for security, and a debug flag. The ledger shortname is required (rather than the ID alone) to support balance-level reporting currencies. The transfer mode distinguishes a full transfer ('F') from an incremental transfer ('I').
  • BEFOREREPORT — A BI Publisher callback function returning BOOLEAN, invoked before report generation. It establishes context such as the concurrent request identifier and system identifier used by the report.
  • AFTERREPORT — A BI Publisher callback function returning BOOLEAN, invoked after report generation to perform cleanup or finalization.
  • PURGE_DATA — Removes previously transferred or staged Fusion data, allowing repeated transfer cycles without unbounded growth of interface tables.

Regarding p_from_period_name: for a full transfer, this parameter names the specific period to transfer. For an incremental transfer it must be null, because incremental mode always transfers data for all periods that have previously been transferred in full. Supplying a period name with incremental mode is therefore invalid usage.

Tables Accessed

Usage Notes

The package is documented as classification OTHER and is not referenced by any other package, so it is invoked directly rather than through an internal dependency chain. In practice it is driven by an Oracle EBS concurrent program that calls DO_TRANSFER, with the same parameters (including p_from_period_name) exposed to the user at submission time. The BI Publisher entry points (BEFOREREPORT, AFTERREPORT) indicate a companion report or output document bound to the same concurrent request, using the p_bi_* public variables to pass ledger, transfer mode, period, access set, and debug values to the report template.

Custom code should call DO_TRANSFER only with a valid access set to satisfy data security, and must observe the full-versus-incremental contract: pass a period name for full mode and null for incremental mode. Debug mode should be enabled ('Y') only during diagnosis, since it affects logging volume in the concurrent request output.