Search Results c_transfer

Overview

FUN_GL_BATCH_TRANSFER is an Oracle E-Business Suite Oracle Financials for India subledger utility supplied under the APPS schema. In Oracle EBS 12.1.1 and 12.2.2 it provides the batch transfer mechanism that moves transaction data captured in the India localization tables (FUN_TRX_BATCHES, FUN_TRX_HEADERS, FUN_TRANSFERS) into the Oracle General Ledger interface tables for subsequent journal creation and posting. The package therefore bridges the India subledger and the GL journal import pipeline, and is the technical object behind the concurrent program commonly referenced as "Transfer Journals to GL" or "GL Batch Transfer."

The search term c_transfer is typically encountered where the transfer action is bound in the concurrent program definition or in the calling form; the package itself exposes the transfer logic through its GL_BATCH_TRANSFER entry point rather than through a literal parameter of that name, so the term is used informally to refer to the batch transfer routine. The package header and body carry the standard concurrent program signature (errbuf, retcode), confirming it is designed to be registered as a concurrent executable.

Key Procedures and Functions

• HAS_VALID_CONVERSION_RATE — Returns a numeric indicator (1 or 0) informing the caller whether a usable daily conversion rate exists for the supplied currency pair, exchange rate type, and exchange date. Identical from and to currencies are treated as valid without a rate lookup. It reads GL_DAILY_RATES.
• GET_CONVERSION_TYPE — Returns the user conversion type associated with a given conversion type, resolving the internal value to the user-facing name from GL_DAILY_CONVERSION_TYPES. It is used to validate and translate exchange rate type input during transfer processing.
• GL_BATCH_TRANSFER — The main concurrent program entry point. It accepts low/high range parameters for date, ledger, legal entity, and intercompany organization, together with two flag parameters controlling whether journal import is run and whether summary journals are created. It orchestrates the transfer of India subledger batches into GL_INTERFACE, raises workflow events using its parameter list and event key, and returns the standard errbuf/retcode pair for the concurrent manager.

Tables Accessed

• FUN_TRX_BATCHES, FUN_TRX_HEADERS, FUN_TRANSFERS — source India localization tables read and updated as batches are selected and marked transferred.
• GL_INTERFACE and GL_INTERFACE_CONTROL — target staging tables written by the transfer and used by Journal Import; the control table carries the group identifier and import options.
• GL_DAILY_RATES and GL_DAILY_CONVERSION_TYPES — exchange rate and conversion type validation supporting the two helper functions.
• GL_JE_SOURCES_TL and GL_JE_CATEGORIES_TL — provide source and category names applied to the generated interface lines.
• GL_JOURNAL_IMPORT_S — sequence used to generate unique journal import group identifiers.
• FND_NEW_MESSAGES — message lookups used for error reporting.
• WF_PARAMETER_LIST_T, DUAL, PLITBLM — workflow parameter/event structures and PL/SQL utility table types used internally.

Usage Notes

The package is invoked as a concurrent program from the India subledger responsibilities, normally through the Transfer to GL or batch transfer submission form. It is also callable from custom PL/SQL using the GL_BATCH_TRANSFER concurrent signature, provided the range parameters and the run-journal-import and create-summary-journals flags are set appropriately. ETRM records no other package as referencing this object, indicating it is a terminal entry point rather than a shared library. Because it writes directly to GL_INTERFACE, it should be run only when the GL period is open for the target ledgers and after all India subledger batches for the range are complete.