Search Results gl_balances_delta_s




Overview

APPS.GL_FUSION_TRANSFER_PKG is a VALID PL/SQL package body owned by the APPS schema that supports the transfer of General Ledger balances from an Oracle E-Business Suite source ledger to an Oracle Fusion General Ledger target system. It is part of the broader GL Fusion transfer infrastructure that allows EBS 12.1.1 and 12.2.2 customers to migrate or continuously replicate ledger balances into Fusion via the GL_INTERFACE and delta-tracking mechanism. The package combines the orchestration logic for extracting balances, mapping accounts and ledgers, and staging records for downstream consumption, and it also provides the report lifecycle hooks used by the concurrent program that drives the transfer. The presence of GL_BALANCES_DELTA_S and GL_TRACK_DELTA_BALANCES among its dependencies indicates that the package is specifically designed to process incremental (delta) balance changes rather than full extracts on every run.

Key Procedures and Functions

  • BEFOREREPORT — Oracle Reports before-report trigger used to initialize the runtime environment for the transfer report, including setting up logging, resolving profiles, and preparing the data structures required by the subsequent processing.
  • AFTERREPORT — Oracle Reports after-report trigger used to perform cleanup, finalize logging, and complete any post-report housekeeping once the transfer report has finished executing.
  • DO_TRANSFER — The core worker procedure. It drives the actual transfer of balances: reading delta balances, applying account and ledger mappings, populating the transfer interface tables, and coordinating the period and ledger relationship logic needed to move data toward the Fusion target.
  • PURGE_DATA — Maintenance procedure that removes processed or obsolete rows from the staging and delta tables so that the transfer tables do not grow unbounded across runs.

No parameter lists are documented for these units; callers should consult the package specification before invoking them directly.

Tables Accessed

The package references a broad set of APPS synonyms. Core balance and delta tables include GL_BALANCES_DELTA, GL_BALANCES_DELTA_S, and GL_TRACK_DELTA_BALANCES, which hold the incremental balance records processed during transfer. Mapping and configuration tables such as GL_COA_MAPPINGS, GL_ACCOUNTS_MAP_GRP, GL_XFR_CCID_MAPPINGS, GL_XFR_LEDGER_MAPPINGS, GL_XFR_PERIOD_MAPPINGS, and GL_XFR_SYSTEM_LEDGERS supply the rules that translate source chart-of-accounts, ledger, and period identifiers into their Fusion equivalents. GL_XFR_LEDGERS, GL_XFR_PERIODS, GL_XFR_SOURCE_SYSTEMS, GL_XFR_INTERFACE, and GL_XFR_TRACKING hold the transfer configuration, staging, and status data. GL_LEDGERS, GL_LEDGER_RELATIONSHIPS, GL_ACCESS_SET_LEDGERS, GL_PERIOD_STATUSES, GL_SYSTEM_USAGES, GL_INTERFACE_CONTROL_S, and GL_ACCTS_MAP_INT_GT provide ledger, period, and interface context. FND_ID_FLEX_SEGMENTS, FND_PROFILE_OPTIONS_TL, FND_PROFILE, FND_GLOBAL, FND_CONCURRENT, FND_FILE, FND_LOG, and FND_FLEX_APIS provide the standard EBS foundation services used for key flexfield metadata, profile options, concurrent request handling, file I/O, logging, and value-set validation.

Usage Notes

This package is invoked in the context of the GL Fusion transfer concurrent program, which supplies the report triggers BEFOREREPORT and AFTERREPORT while DO_TRANSFER executes the transfer logic and PURGE_DATA handles housekeeping. Because the package body references GL_BALANCES_DELTA_S and GL_TRACK_DELTA_BALANCES, it is intended for incremental balance synchronisation between EBS and Fusion, typically after the initial full transfer has been established. The package is not referenced by any other database object, so it should be treated as an entry-point API rather than a shared utility. Custom code should call it only through the supported concurrent program path and should not attempt to replicate its internal logic, since account and ledger mapping rules are driven by the GL_XFR_* configuration tables. DBAs troubleshooting a transfer should verify that the delta staging tables are populated, the GL_XFR_* mappings are current, and that FND_LOG output from DO_TRANSFER is reviewed for errors before re-running the program.