Search Results get_fc_reqd_flag




Overview
Explore in AI Chat

Overview

PA_CC_ENC_IMPORT_FCK is a funds-checking package body in the Oracle E-Business Suite Projects (PA) module, owned by APPS. It supports the encumbrance and budgetary control import flow by determining whether funds checking is required for a given project and budget type, resolving the applicable budget version, and returning tie-back results to the calling process. The naming convention (FCK for funds check) and the header comment confirm that the package exists to evaluate budgetary control configuration against incoming encumbrance or budget data.

The package is classified as OTHER in the ETRM repository and is not an end-user API. It is an internal utility invoked by the encumbrance import concurrent program logic and by at least one other package. Its design emphasizes performance through lightweight caching of prior lookups, avoiding repeated SQL execution within a single import run.

Key Procedures and Functions

  • LOAD_PKTS — Initializes or loads the package state required before the funds-check routines execute. Exact parameters are not documented in the excerpt.
  • PA_ENC_IMPORT_FCK — The primary entry point coordinating the funds-check evaluation for the encumbrance import process.
  • PA_ENC_IMPORT_FCK_TIEBACK — Handles the tie-back stage of the import, reconciling funds-check results against imported encumbrance records.
  • IS_PA_INSTALL_IN_OU — Determines whether Oracle Projects is installed and enabled for the operating unit in context, gating further processing.
  • GET_FC_REQD_FLAG — Returns 'Y' or 'N' indicating whether budgetary control is enabled for a given project and external budget code combination. The documented logic uses an EXISTS clause against PA_BUDGETARY_CONTROL_OPTIONS and PA_BUDGET_TYPES (restricted to budget_amount_code = 'C'), with results cached in package globals such as G_prev_flag_project_id, G_prev_flag_ext_budget_code, and G_Prev_budget_control_flag.
  • GET_BDGT_VERSION_ID — The function matching the user's search term. It resolves the budget version identifier associated with a project and budget type, using the PA_BUDGET_VERSIONS table. A cache variable, G_prev_budget_version_id, is declared for this purpose.
  • TIE_BACK_RESULT_CODE — Produces the result code used during tie-back processing to communicate the outcome of funds-check evaluation to the caller.

The package declares global cache variables (G_debug_mode, G_prev_bdgt_project_id, G_prev_bdgt_ext_budget_code, and others) plus a print_msg helper that routes diagnostic text to pa_debug when debug mode is enabled.

Tables Accessed

  • PA_BUDGETARY_CONTROL_OPTIONS — Source of the budgetary control flag and external budget code per project.
  • PA_BUDGET_TYPES — Supplies budget type attributes, including budget_amount_code, used to qualify controlled budget types.
  • PA_BUDGET_VERSIONS — Provides the budget version identifier resolved by GET_BDGT_VERSION_ID.
  • PA_BC_PACKETS / PA_BC_PACKETS_S — Budgetary control packet and packet-set definitions used in the funds-check import flow.
  • PA_IMPLEMENTATIONS — Installation status lookup supporting IS_PA_INSTALL_IN_OU.
  • DUAL — Used as the driving row for the EXISTS-based flag query.
  • PLITBLM — Oracle Applications standard character buffer table used in message handling.

Usage Notes

This package is invoked internally rather than directly from Oracle Projects forms. It is most commonly reached through the encumbrance import and budgetary control processes in Oracle EBS 12.1.1 and 12.2.2. Custom code that calls GET_BDGT_VERSION_ID or GET_FC_REQD_FLAG directly should account for package-global caching: the cached values persist for the duration of the session, so successive calls with different project or budget inputs will correctly refresh the cache only when the cached keys differ from the new inputs. Because the package is classified as OTHER, Oracle does not guarantee backward compatibility of its signatures. Developers should treat it as a private implementation detail of the funds-check import, and any reliance on it should be limited to diagnostics or tightly controlled extensions. Enabling debug mode causes print_msg to write stage information through pa_debug, which assists in tracing funds-check decisions during import troubleshooting.