Search Results fnd_installation




Overview
Explore in AI Chat

Overview

FND_INSTALLATION is a foundational PL/SQL package in the APPS schema of Oracle E-Business Suite, present in both the 12.1.1 and 12.2.2 releases. Its purpose is to expose installation and product-registration metadata about the running EBS instance to any calling program. Rather than querying the underlying installation tables directly, Oracle's own code and customer extensions invoke this package to resolve questions such as which applications are installed, which database schema (Oracle user) owns a given application, and how a product installation is identified against its registered application. The package is classified under the ETRM as an OTHER API, meaning it is an internal-use utility rather than a public, versioned interface, but it remains a stable and ubiquitous dependency across the technology stack.

The ETRM record confirms the object is VALID in the APPS schema and lists three documented program units, giving it a compact but strategically important surface area.

Key Procedures and Functions

The documented program units of FND_INSTALLATION are three:

  • GET — The primary retrieval routine. It returns installation-related information for the environment, resolving values from the product installation and application registration tables. It is the general-purpose entry point used by callers that need installation facts without knowing the specifics of the schema lookup.
  • GET_APP_INFO — Returns descriptive information about a specific application, derived from the application registration data. This is the routine invoked when a caller needs to map an application short name or identifier to its registered attributes.
  • GET_APP_INFO_OTHER — A companion to GET_APP_INFO that returns application information for an alternate or "other" context. It follows the same lookup pattern but accommodates the case where the caller is querying against a different application or schema reference than the default resolution path.

No parameter lists are documented in the ETRM metadata, so the exact signatures are not reproduced here. In practice these routines are called from PL/SQL and are not exposed as concurrent program entry points.

Tables Accessed

The package reads from three tables through APPS synonyms:

  • FND_APPLICATION — the application registration table, supplying the application short name, base path, and related attributes returned by GET_APP_INFO and GET_APP_INFO_OTHER.
  • FND_PRODUCT_INSTALLATIONS — the product installation table, which records which products are installed in the current instance along with their status and patch level. This drives the default resolution performed by GET.
  • FND_ORACLE_USERID — the Oracle schema registration table, used to resolve an application to its owning database user and password reference.

The dependency listing further shows the package body references itself (FND_INSTALLATION), which indicates internal recursive or helper calls within the body, and SYS.STANDARD, the default PL/SQL package. No write operations are implied by the metadata; the package is a read-only metadata accessor.

Usage Notes

FND_INSTALLATION is most heavily consumed internally. The ETRM records that it is referenced by 575 other packages in the APPS schema, which makes it one of the more widely depended-upon utilities in the application tier. Because it is not referenced by any database object in the reverse direction, it sits near the bottom of the dependency hierarchy and is effectively a leaf utility.

Typical invocation occurs during concurrent program execution, especially installation and patching-related programs, and within forms and OAF pages that need to display or validate application and product installation information. Custom code should treat the package as read-only and be aware that it is not a formally documented public API; Oracle may alter its internals across releases. The recommended pattern for customizations is to call GET, GET_APP_INFO, or GET_APP_INFO_OTHER rather than querying FND_APPLICATION, FND_PRODUCT_INSTALLATIONS, or FND_ORACLE_USERID directly, since the package encapsulates the correct resolution logic across the 12.1.1 and 12.2.2 data models.