Search Results ext_budget_type

Overview

PA_CC_ENC_IMPORT_FCK is an Oracle Projects package that supports the import of encumbrance and commitment cost transactions into Oracle Projects budgetary control and funds checking structures. Its primary responsibility is to load budgetary control packets (PA_BC_PACKETS) that represent project-related encumbrances originating from external sources such as Oracle Purchasing or Oracle Payables. In the Oracle EBS 12.1.1 and 12.2.2 releases, this package forms part of the integration layer that aligns project cost collection with the commitment and encumbrance accounting model.

The package declares an FC_Record PL/SQL record type modeled on columns of PA_BC_PACKETS, providing default values for status, document type, burden cost flag, balance posted flag, and actual flag. The default EXT_BUDGET_TYPE of 'GL' indicates that the packet is intended for General Ledger budgetary control unless overridden to 'CC'. The AUTHID CURRENT_USER declaration means the package executes with the privileges of the calling user, requiring appropriate grants on the underlying project tables.

Key Procedures and Functions

• LOAD_PKTS — The core entry point referenced in the user search. It loads packet records, constructed from the FC_Record type, into the PA_BC_PACKETS and PA_BC_PACKETS_S tables for subsequent funds checking and budgetary control processing.
• PA_ENC_IMPORT_FCK — The main import driver for encumbrance funds check activity, coordinating validation and population of packet data.
• PA_ENC_IMPORT_FCK_TIEBACK — Handles the tie-back step, updating the originating transaction or result status after the funds check has completed, ensuring the source document and the project packet remain synchronized.
• IS_PA_INSTALL_IN_OU — Determines whether Oracle Projects is installed and operational for the specified operating unit, gating the import logic accordingly.
• GET_FC_REQD_FLAG — Retrieves the funds check required indicator, determining whether validation must be performed for the transaction in question.
• GET_BDGT_VERSION_ID — Returns the applicable budget version identifier used to bind the encumbrance packet to the correct budget definition.
• TIE_BACK_RESULT_CODE — Resolves and supplies the result code applied during the tie-back update process.

Tables Accessed

• PA_BC_PACKETS / PA_BC_PACKETS_S — The primary insertion targets; hold packet header and detail rows for encumbrances and commitments.
• PA_BUDGETARY_CONTROL_OPTIONS — Determines whether funds checking and budgetary control are enabled, influencing the required flag logic.
• PA_BUDGET_TYPES / PA_BUDGET_VERSIONS — Supply the budget type and version used by GET_BDGT_VERSION_ID.
• PA_IMPLEMENTATIONS — Supports the IS_PA_INSTALL_IN_OU installation check.
• DUAL — Used for single-row selection and default value retrieval.
• PLITBLM — The standard Oracle PL/SQL index-by table of VARCHAR2, supporting array-style parameter passing.

Usage Notes

PA_CC_ENC_IMPORT_FCK is typically invoked from concurrent programs and integration routines that import commitment and encumbrance transactions from Purchasing, Payables, or external feeder systems into Oracle Projects. It is also referenced programmatically by one other package, indicating a dependency in the funds check call chain. Custom extensions should call LOAD_PKTS with properly populated FC_Record structures, ensuring PERIOD_NAME and ENCUMBRANCE_TYPE_ID are supplied, as the declaration notes these are mandatory. Because the package runs under AUTHID CURRENT_USER and relies on APPS synonyms, execution should occur within the APPS schema context or with equivalent grants. Organizations upgrading between 12.1.1 and 12.2.2 should verify that the referenced tables and synonyms remain valid, as online patching in 12.2.x affects editioning of code objects.