Search Results is_utilization_implemented




Overview
Explore in AI Chat

Overview

PA_INSTALL is a utility package in the Oracle EBS Projects (PA) application, owned by APPS and classified as an "OTHER" API. Its primary business purpose is to expose Oracle Projects feature, product, and licensing checks to other PL/SQL code at runtime. Rather than hard-coding product conditions, the Projects application calls PA_INSTALL to determine whether a given sub-product — such as Project Intelligence, Project Billing, Project Resource Management, Project Costing, or Project Tracking — is installed or licensed in the current environment. This supports conditional execution paths, menu and region enabling, and validations across the Projects suite.

The package is declared AUTHID CURRENT_USER, meaning its SQL executes with the privileges of the invoking user (definer rights are not assumed). Each of the licensing and installation functions carries pragma RESTRICT_REFERENCES (…, WNDS), guaranteeing that the respective function writes no database state. The header identifies the source as PAXINSS.pls, version 120.0.

Key Procedures and Functions

Nine documented functions constitute the public interface:

  • IS_PJT_LICENSED — Returns 'Y' if Project Tracking is licensed/installed; otherwise 'N'. This is the function the user's query, "is_pjt_licensed," targets; it answers whether the Project Tracking product is available for use.
  • IS_PJI_INSTALLED — Returns the installation status of Project Intelligence.
  • IS_PJI_LICENSED — Returns 'Y' if Project Intelligence is licensed; otherwise 'N'.
  • IS_BILLING_LICENSED — Returns 'Y' if Project Billing is licensed/installed; otherwise 'N'.
  • IS_PRODUCT_INSTALLED — Accepts a product short name as input and returns a BOOLEAN, TRUE if that product is installed.
  • IS_PRM_LICENSED — Returns 'Y' if Project Resource Management is licensed/installed; otherwise 'N'.
  • IS_COSTING_LICENSED — Returns 'Y' if Project Costing is licensed/installed; otherwise 'N'.
  • IS_UTILIZATION_IMPLEMENTED — Returns 'Y' if any row exists in PA_UTILIZATION_OPTIONS_ALL; otherwise 'N'.
  • IS_ORD_MGMT_INSTALLED — Returns 'Y' based on the presence of rows in PA_UTILIZATION_OPTIONS_ALL; otherwise 'N'.

Tables Accessed

The documented tables accessed via APPS synonyms are FND_APPLICATION, FND_LOOKUP_VALUES, FND_PRODUCT_INSTALLATIONS, PJI_SYSTEM_PARAMETERS, and PJI_SYSTEM_SETTINGS.

  • FND_PRODUCT_INSTALLATIONS — the primary source for installation status, consulted by the installation-checking functions (IS_PJI_INSTALLED, IS_PRODUCT_INSTALLED, IS_ORD_MGMT_INSTALLED).
  • FND_APPLICATION — resolves application/product short names used by IS_PRODUCT_INSTALLED.
  • FND_LOOKUP_VALUES — supplies lookup-driven configuration values used in the licensing checks.
  • PJI_SYSTEM_PARAMETERS and PJI_SYSTEM_SETTINGS — Project Intelligence configuration tables consulted by the PJI-related checks.

PA_INSTALL performs read-only lookups against these objects; consistent with the WNDS pragmas, it does not modify data.

Usage Notes

PA_INSTALL is an internal helper package for the Projects suite and is referenced by approximately 49 other packages. It is typically invoked from PL/SQL regions in Oracle Forms, from concurrent program logic, and from custom extensions that must branch on whether Project Tracking, Billing, Costing, or related sub-products are licensed in a given environment. Typical usage follows the pattern of calling a boolean-style function such as PA_INSTALL.IS_PJT_LICENSED (comparing the returned 'Y'/'N') or PA_INSTALL.IS_PRODUCT_INSTALLED (testing a BOOLEAN) before exposing or executing product-specific functionality.

Because licensing registration and product installation are environment-specific, results vary between instances (for example, development versus production). Consumers, especially custom code, should test the returned value rather than assume availability, and should be aware that the licensing functions return VARCHAR2 'Y'/'N' while IS_PRODUCT_INSTALLED returns BOOLEAN. No parameters are documented for the function interfaces beyond those described, so callers must rely on the established signatures.