Results for “cost_budget”

24 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_PROJECT_VERIFY is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the Projects (PA) product family and is classified under the ETRM metadata as an "OTHER" API, meaning it is a supporting validation utility rather than a public, published business API. Its name reflects its primary purpose: to verify that master and project-level attributes supplied during project setup or maintenance are complete, consistent, and valid before the record is committed.

The package encapsulates the validation rules that govern key project definition elements—organisation roles such as manager and client, contact information, budgetary structures, revenue structures, category usage, and billing events. By centralising these checks, the package enforces data integrity across the many entry points through which project data reaches the database, including the Project Super User forms and the project import interfaces. The body has no reverse dependencies, so no other database object references it; it is consumed only at the top of the call stack, typically from form-level logic or import routines.

Key Procedures and Functions

The documented package exposes twelve procedures and functions. Each performs an independent verification of a specific project attribute:

  • VERIFICATION — The principal entry point that drives the overall validation sequence for a project record.
  • MANAGER — Validates project manager assignment and related role data.
  • CLIENT — Validates client or customer information associated with the project.
  • CONTACT — Checks contact details linked to the project or its related parties.
  • COST_BUDGET — Verifies cost budget definitions and their required attributes.
  • REVENUE_BUDGET — Verifies revenue budget definitions and their required attributes.
  • CATEGORY — Validates expenditure or revenue category assignments.
  • BILLING_EVENT — Checks billing event configuration for the project.
  • GET_RULE_NAME — Retrieves the descriptive name of an applicable rule for message display.
  • GET_ERROR_MSG — Returns the error message text associated with a failed validation.
  • GET_ACTION_MSG — Returns the corrective action message shown to the user when validation fails.
  • GET_REQUIRED_FLAG — Determines whether a given attribute is mandatory in the current context.

The GET_* routines support the validation routines by supplying rule names, error text, corrective action text, and required-attribute indicators, enabling consistent, user-friendly diagnostics.

Tables Accessed

The documented ETRM metadata records no explicit base tables for this package. Its internal logic uses APPS synonyms to read configuration and project data, and its only declared dependencies are APPS.PA_PROJECT_VERIFY itself and APPS.PA_UTILS, the central utility package used throughout Oracle Projects. In practice, verification of managers, clients, contacts, budgets, categories, and billing events draws on the standard PA project structures, but the excerpt provided does not enumerate those tables, so no specific table list can be asserted from the documentation alone.

Usage Notes

PA_PROJECT_VERIFY is invoked during interactive project definition and maintenance, most commonly from the Oracle Projects forms, and during batch interfaces such as project import. Because the package is classified as OTHER and is not referenced by any other database object, it is not intended as a reusable public API. Customisations should avoid calling it directly where a documented public API exists; where direct invocation is necessary, developers should rely on PA_UTILS for shared error-handling conventions and expect that validation outcomes are surfaced through the GET_ERROR_MSG and GET_ACTION_MSG routines. The package status is VALID in both 12.1.1 and 12.2.2, indicating the body is compiled and available in the standard APPS schema.