Search Results check_entry_method_flags_pvt

Overview

PA_BUDGET_CHECK_PVT is a private PL/SQL package in the APPS schema that provides the core validation logic used by Oracle Projects when budgets are entered, modified, or submitted for approval. It is classified as a PVT (private) API object, meaning it is not intended for direct invocation by customer extension code; instead it is consumed internally by the public budgeting APIs and by the Oracle Forms used for budget entry. The package centralizes the rules that determine whether a budget entry is valid in a given context: whether the entry falls within an open or valid GL period, whether the budget entry method chosen permits the entered amounts and flags, whether the unit of measure supplied with a resource is acceptable, and whether the project is still active for budgeting purposes.

The package appears in Oracle EBS 12.1.1 and 12.2.2 with a VALID status and is catalogued under the Oracle E-Business Suite Technical Reference Manual (ETRM). Four procedures and functions are documented for it, and it references nine database objects through APPS synonyms.

Key Procedures and Functions

• GET_VALID_PERIOD_DATES_PVT — Derives the set of valid accounting period dates against which budget entries may be validated. It is used to confirm that a budget line falls within a period that is open for the relevant ledger, drawing on GL period status information.
• CHECK_ENTRY_METHOD_FLAGS_PVT — Evaluates the flags associated with the selected budget entry method to confirm that the entered budget is consistent with the rules of that method. Budget entry methods control which dimensions, amounts, and behaviours are permitted on a budget.
• VALIDATE_UOM_PASSED — Validates the unit of measure supplied with a budget resource. Quantity-based budget lines must carry a UOM that is meaningful for the resource, and this routine enforces that requirement.
• GET_PROJECT_END_DATE — Returns the project end date, which is used to determine whether a budget entry is being made within the project's active life and to support period-boundary checks.

Tables Accessed

The package reads from PA_BUDGET_ENTRY_METHODS to obtain entry method definitions and flags, and from PA_BUDGET_LINES when existing budget data must be inspected. GL_PERIOD_STATUSES supplies accounting period open/closed status for period validation. PA_PROJECTS and PA_PROJ_ELEMENT_VERSIONS provide project and project element information, including the project end date. PA_TASKS supplies task-level context for budget lines and PA_RESOURCE_LIST_MEMBERS supports resource validation. DUAL is used for singleton lookups, and PLITBLM is the standard PL/SQL index-by table of VARCHAR2 used internally for passing collections of values, typically period names or error messages.

Usage Notes

As a PVT package, PA_BUDGET_CHECK_PVT is not a supported integration point. It is invoked by higher-level packages such as PA_BUDGET_PVT and PA_BUDGET_CHECK_PVT's own wrapper, and indirectly by the Oracle Projects budget entry forms and any concurrent process that validates budgets before they are baselined. The dependency list confirms that the package both references and is referenced by APPS objects of the same family, which is characteristic of private validation layers in Oracle Projects.

Developers integrating with Oracle Projects budgets should call the supported public APIs in PA_BUDGET_PVT or PA_BUDGET_PUB rather than calling this package directly. Because it is private, Oracle may change its signature or behaviour without notice between releases, and direct calls risk failure following patching. Custom code that must reproduce a validation decision should rely on the underlying tables and documented public APIs instead of this package.