Results for “get_start_date_active_from_pa”

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

Overview

IGW_EXP_CATEGORIES_V_PKG is a public PL/SQL package owned by the APPS schema in Oracle EBS Release 12.1.1 and 12.2.2. It is classified as an OTHER API, meaning it is not designated as a formal business API or an open interface, but it is exposed for reuse across the application. The package exists to supply lookup-style attribute values for expenditure categories that are maintained in Oracle Projects, specifically the descriptive text and the effective date range (start and end dates) associated with each expenditure category.

The naming convention at work is significant: the suffix _V_PKG and the FROM_PA suffix on each function signal that the package wraps the Projects (PA) base table to present a denormalized view of its columns to the IGW (Internet Government / Grants) module. Rather than querying PA_EXPENDITURE_CATEGORIES directly, IGW forms and dependent packages call these accessor functions so that the retrieval logic is centralized. The package is declared AUTHID CURRENT_USER, so it executes with the privileges of the calling user, and it carries the $Header stamp igwstexs.pls 115.2 2002/03/28, indicating a lineage that predates the 12.x releases.

Key Procedures and Functions

The package declares three functions, each returning a VARCHAR2 value and each governed by a PRAGMA restrict_references(..., WNDS) declaration. The WNDS (Write No Database State) pragma asserts that the function performs no database writes, which permits Oracle to invoke these functions safely inside SQL statements and to cache results within a query.

• GET_DESCRIPTION_FROM_PA — Returns the descriptive name of an expenditure category. This is the human-readable label presented to users wherever an expenditure category is displayed as a list of values or a read-only field.
• GET_START_DATE_ACTIVE_FROM_PA — Returns the date from which the expenditure category became active. This represents the lower bound of the category's effective period.
• GET_END_DATE_ACTIVE_FROM_PA — Returns the date on which the expenditure category ceases to be active. This is the function matched by the search term "get_end_date_active_from_pa" and is the most commonly requested member of the package, since it determines whether a category is still selectable at transaction time.

No parameter lists are documented beyond the single expenditure category identifier implied by p_expenditure_category, and no explicit procedure bodies are exposed. Callers should treat the interface as three independent scalar getters rather than a single row-fetching routine.

Tables Accessed

The only documented table reference is PA_EXPENDITURE_CATEGORIES, accessed through an APPS synonym. This table is the master repository for expenditure categories in Oracle Projects and holds the description, start date active, and end date active columns that the package surfaces. All three functions read from this single table; none of them writes. Because the functions are WNDS-restricted, the package performs no DML, no commits, and no sequence consumption.

Usage Notes

IGW_EXP_CATEGORIES_V_PKG is referenced by three other packages within the EBS codebase, which is consistent with its role as a shared accessor layer rather than a standalone entry point. Typical invocation patterns include:

• Oracle Forms in the IGW/Grants modules that need to display or validate expenditure categories, calling the functions in post-query triggers or LOV validation.
• Dependent PL/SQL packages that resolve category descriptions and effective dates before inserting or validating transaction lines.
• Custom code and reports that require the active end date of a category, for example to exclude expired categories from a selection set.

Because each function returns a scalar VARCHAR2 and is WNDS-pure, the functions are safe to embed in SQL SELECT lists and WHERE clauses. Integrators working on 12.1.1 or 12.2.2 should note that the package is an internal wrapper, not a supported open interface, and that direct reads of PA_EXPENDITURE_CATEGORIES remain the alternative when a set-based query is preferred over row-by-row function calls.