Search Results fun_gl_transfer




Overview
Explore in AI Chat

Overview

FUN_GL_TRANSFER is a public PL/SQL package owned by APPS in the Oracle E-Business Suite Financials product family. Its core business purpose is to transfer subledger transactions originating in the Oracle Grants and related FUN transaction tables into the Oracle General Ledger interface, and ultimately into GL journals. The package acts as the controlled bridge that validates a transaction's readiness, locks it against concurrent modification, resolves currency conversion requirements, verifies the target accounting period is open, and finally stages the accounting lines in GL_INTERFACE for the standard GL journal import process. Because it enforces locking and status transitions, it protects the integrity of the transfer pipeline, preventing a transaction from being transferred twice or transferred while in an ineligible state.

The package is classified as OTHER in the ETRM metadata. It is referenced by two other packages, indicating it serves as a shared utility layer invoked by higher-level transfer orchestration code rather than as a user-facing API.

Key Procedures and Functions

  • GET_CONVERSION_TYPE — Returns the conversion type (exchange rate type) applicable to a transfer, accepting a conversion type as input and returning the resolved value as a VARCHAR2.
  • LOCK_AND_TRANSFER — Acquires a lock on the transaction and performs the transfer in a single controlled operation. It accepts the transaction identifier, ledger, GL date, currency, category, source, description, conversion date, conversion type, and party type, and returns a boolean indicating success.
  • LOCK_TRANSACTION — Locks an individual transaction identified by transaction ID and party type. If a status value is supplied, the function also validates that the status remains valid, returning a boolean result.
  • HAS_CONVERSION_RATE — Determines whether a conversion rate exists between a from-currency and a to-currency for a given exchange type and exchange date, returning a numeric result.
  • GET_PERIOD_STATUS — Returns the period closing status for a period. This function is the object surfaced by the "get_period_status" search and is used to confirm that the target accounting period is in an appropriate state before accounting entries are generated.
  • UPDATE_STATUS — Updates the status of a transaction to reflect its progress through the transfer lifecycle.
  • TRANSFER_SINGLE — Transfers a single transaction to General Ledger.
  • TRANSFER_BATCH — Transfers a batch of transactions, using party type resolution and raising the trx_no_party_type_error exception when the party type is unknown.

The package also declares two exceptions: corrupted_transaction_status, raised when a transaction is in the wrong status, and trx_no_party_type_error, raised when the party type is unknown during batch transfer.

Tables Accessed

  • FUN_TRX_HEADERS, FUN_TRX_LINES, FUN_DIST_LINES — The source FUN transaction header, line, and distribution tables that supply the transactions being transferred and whose status is updated.
  • FUN_TRX_BATCHES — Supports batch-level transfer processing.
  • GL_INTERFACE — The staging table into which accounting entries are written for journal import.
  • GL_PERIOD_STATUSES — Queried by GET_PERIOD_STATUS to determine the target period's closing status.
  • GL_DAILY_CONVERSION_TYPES — Provides valid conversion type definitions used in rate resolution.
  • GL_JE_CATEGORIES_TL and GL_JE_SOURCES_TL — Supply journal category and source names required when populating the GL interface.
  • WF_PARAMETER_LIST_T, PLITBLM, DUAL — Supporting constructs used for parameter handling, PL/SQL table operations, and singleton queries.

Usage Notes

FUN_GL_TRANSFER is typically invoked from Oracle Forms-based transfer screens, from concurrent programs that perform batch transfers, or from custom PL/SQL that needs to push FUN transactions into GL. Because it manages locking and status validation internally, callers should generally use LOCK_AND_TRANSFER, TRANSFER_SINGLE, or TRANSFER_BATCH rather than manipulating the underlying tables directly. GET_PERIOD_STATUS is commonly called as a pre-check to confirm period openness before initiating a transfer. Custom code should handle the corrupted_transaction_status and trx_no_party_type_error exceptions explicitly, and should commit only after the transfer and GL interface population succeed.