Search Results is_pji_installed




Overview
Explore in AI Chat

Overview

APPS.PA_INSTALL is a utility package body in the Oracle E-Business Suite Projects (PA) schema whose primary business function is to determine whether specific Oracle Projects products, features, and licensing options are installed, licensed, or implemented within a given EBS instance. Rather than performing transactional project accounting work, PA_INSTALL acts as a configuration and capability-detection layer. It allows other Projects modules, forms, and concurrent programs to branch their behavior at runtime based on what the customer has actually purchased and deployed. The package is classified as an "OTHER" API within the ETRM metadata, reflecting its role as an internal infrastructure package rather than a public, externally callable business API.

Key Procedures and Functions

The documented package exposes nine procedures and functions, each returning a boolean-style indicator of installation, licensing, or implementation status:

  • IS_PJI_INSTALLED — Determines whether Oracle Project Intelligence (PJI) is installed in the current instance.
  • IS_PJI_LICENSED — Determines whether the PJI product is licensed, independent of installation.
  • IS_BILLING_LICENSED — Returns whether the Projects Billing product is licensed for use.
  • IS_PRODUCT_INSTALLED — General check for whether a given Oracle product is installed, based on product installation records.
  • IS_PRM_LICENSED — Indicates whether Oracle Project Resource Management (PRM) is licensed.
  • IS_COSTING_LICENSED — Indicates whether Projects Costing is licensed.
  • IS_PJT_LICENSED — Indicates whether Project Tracking (PJT) is licensed.
  • IS_UTILIZATION_IMPLEMENTED — Reports whether utilization functionality has been implemented, drawing on system settings and parameters.
  • IS_ORD_MGMT_INSTALLED — Reports whether the Order Management product is installed, supporting cross-module integration checks.

Parameter lists are not documented in the ETRM metadata and should not be assumed; each routine is best understood by its status-checking purpose.

Tables Accessed

PA_INSTALL reads from several foundation and Projects configuration tables via APPS synonyms:

  • FND_APPLICATION — Resolves Oracle application definitions used to identify installed products.
  • FND_PRODUCT_INSTALLATIONS — The authoritative source for determining whether an EBS product is installed (status code "I").
  • FND_LOOKUP_VALUES — Supplies lookup-based configuration and licensing indicators.
  • FND_PROFILE — Supports profile-option-driven decisions where installation or licensing depends on site or responsibility settings.
  • PJI_SYSTEM_PARAMETERS and PJI_SYSTEM_SETTINGS — Provide Project Intelligence configuration data used by the PJI-specific checks.

The dependencies list further confirms PA_INSTALL depends on STANDARD (the database standard package) and recursively on itself. The package is not referenced by any database object directly, but is referenced by 49 other packages, underscoring its wide internal footprint.

Usage Notes

PA_INSTALL is an internal utility invoked indirectly by other Projects packages, forms, and concurrent programs rather than by end users. Because detection is centralized here, developers should call PA_INSTALL routines instead of querying FND_PRODUCT_INSTALLATIONS or FND_LOOKUP_VALUES directly, ensuring consistent interpretation of installation and licensing state. Typical invocation scenarios include conditional display of billing, costing, or resource-management functionality, gating of PJI-dependent code paths, and enabling cross-module checks such as Order Management integration. Given that 49 packages depend on it, changes to PA_INSTALL carry broad regression risk and should be validated against the full Projects dependency chain in EBS 12.1.1 and 12.2.2.