Search Results p_encumbrance_type_id

Overview

PA_BUDGET_INTEGRATION_PKG is a table handler package in the Oracle Projects (PA) application, owned by APPS and classified as an OTHER API in the ETRM 12.2.2 metadata. Its stated purpose, taken directly from the package header, is to provide table handler APIs that insert, update, delete, and lock records in the PA_BUDGETARY_CONTROL_OPTIONS table through an Oracle Forms interface. In Oracle EBS Releases 12.1.1 and 12.2.2, this table stores the budgetary control and funds control configuration that governs how project budgets are validated against GL budget versions and encumbrance types. The package therefore acts as a thin persistence layer, shielded behind standard Forms-based DML rather than being exposed as a true business API. The absence of any dependent packages (referenced by 0 other packages) confirms its role as a leaf-level handler invoked only by the form module that maintains budgetary control options.

Key Procedures and Functions

The documented procedures comprise the four standard table-handler methods used by Oracle Forms:

• INSERT_ROW — Inserts a new budgetary control options record into PA_BUDGETARY_CONTROL_OPTIONS. The insert column list includes Project_Type, Project_ID, Balance_Type, Budget_Type_Code, External_Budget_Code, GL_Budget_Version_ID, Encumbrance_Type_ID, Bdgt_Cntrl_Flag, the four fund control level columns (Project, Task, Resource Group, Resource), Amount_Type, and Boundary_Code, along with the standard WHO audit columns. This is the procedure most directly associated with the search term p_encumbrance_type_id, since the parameter populates the Encumbrance_Type_ID column that links a budgetary control setup to an Oracle Payables/Oracle Purchasing encumbrance type.
• UPDATE_ROW — Modifies an existing budgetary control options row identified by its ROWID, applying the same set of configuration and audit attributes supplied by the form.
• DELETE_ROW — Removes an existing budgetary control options record, typically when a project type or project-level control setup is no longer required.
• LOCK_ROW — Acquires a row-level lock on the target record for the duration of the form transaction, preventing concurrent modification of the same control options row.

All four procedures accept the calling-mode convention noted in the header comments (SUBMIT / GENERATE_ACCOUNT style parameters), reflecting the generic table-handler pattern used across Oracle Projects form-based maintenance screens.

Tables Accessed

The single documented table is PA_BUDGETARY_CONTROL_OPTIONS, accessed through an APPS synonym. This table holds the budgetary and funds control options that determine whether budget checking is enabled for a given project type or project, which GL budget version is compared, which encumbrance type is used for commitments, and how far down the project hierarchy (project, task, resource group, resource) funds control applies. The package performs only DML against this table; it does not query or write any other documented object.

Usage Notes

Because this is a Forms-driven table handler, it is invoked from the Oracle EBS budgetary control options form rather than from concurrent programs or external integration code. In 12.1.1 and 12.2.2, Oracle strongly recommends that customizations avoid calling these procedures directly, since they bypass business validation and rely on the form to supply correctly derived ROWID and audit values. The parameter name p_encumbrance_type_id appears in INSERT_ROW and maps to the Encumbrance_Type_ID column, which is significant during diagnostics: an incorrectly populated encumbrance type will cause subsequent funds check and commitment accounting processes to fail or produce mismatched encumbrances. When troubleshooting budgetary control configuration, DBAs and developers typically inspect the row inserted through this package rather than executing the package itself. The header revision ($Header: PABDINTB.pls 120.3, dated 2006) indicates the file has been stable since the 11i era and carries no notable 12.2 functional changes beyond standard synonym and editioning behaviour.