Search Results g_installed




Overview
Explore in AI Chat

Overview

PJM_INSTALL is a PL/SQL installation and implementation-detection package in the Oracle E-Business Suite (EBS) Applications (APPS) schema, classified under the ETRM metadata as API classification OTHER. Its principal business function is to register and verify the installation state of the Project Manufacturing (PJM) product and to maintain the flexfield value set configuration required for project locators. The package body declares three package-level global variables — G_Installed, G_Implemented, and G_Implemented_Org — which cache the installation and implementation status during a session. These globals are the identifiers most frequently referenced by callers searching for the package, since G_Installed acts as the authoritative in-memory flag indicating whether Project Manufacturing has been installed.

The header comment $Header: PJMINSTB.pls 120.0.12010000.2 2009/10/20 ... huiwan ship $ confirms the source file is PJMINSTB.pls, versioned for the 12.1.1 and 12.2.2 release lines. The package includes private helper functions such as create_locator_segment, which programmatically defines locator key flexfield segments against the MTLL flexfield (application_id 401, id_flex_num 101). A documented historical fix (Bug 851461) addressed the case where Project Manufacturing is installed but the first inventory organization is not Project References Enabled, causing the AOL Flex API to attempt redundant segment creation and fail.

Key Procedures and Functions

  • CHECK_INSTALL — Determines whether Project Manufacturing has been installed in the current environment, typically by interrogating FND_PRODUCT_INSTALLATIONS. It populates or validates the G_Installed global so subsequent calls avoid repeated lookups.
  • ENABLE_INSTALL — Performs the actions required to mark or enable the PJM installation state, working in conjunction with the installation registration records.
  • CHECK_IMPLEMENTATION_STATUS — Evaluates whether Project Manufacturing has been implemented for an organization, using the PJM organization and project parameter tables. It supports the G_Implemented and G_Implemented_Org globals.
  • MAINTAIN_LOCATOR_VALUESETS — Creates and validates the flexfield value sets and segments needed for project locators, including the private create_locator_segment logic against FND_FLEX_VALUE_SETS and FND_ID_FLEX_SEGMENTS.

Tables Accessed

  • FND_PRODUCT_INSTALLATIONS — installation status records underpinning CHECK_INSTALL.
  • PJM_ORG_PARAMETERS and PJM_PROJECT_PARAMETERS — organization- and project-level implementation flags used by CHECK_IMPLEMENTATION_STATUS.
  • FND_FLEX_VALUE_SETS and FND_ID_FLEX_SEGMENTS — value set and segment definitions validated or created by MAINTAIN_LOCATOR_VALUESETS and create_locator_segment.
  • FND_ORACLE_USERID — Oracle schema/user information, typically for installation validation.
  • AD_DDL — used for DDL invocation during installation maintenance.
  • USER_SYNONYMS — synonym verification to confirm object accessibility in the APPS schema.

Usage Notes

PJM_INSTALL is invoked during Project Manufacturing installation and setup, and is referenced by two other packages in the documented dependency set. Callers should treat the globals as session-cached state: G_Installed is initialized to NULL and set when installation status is checked. Typical invocation occurs through Oracle Forms setup screens and installation or concurrent setup programs rather than end-user transactional flows. Custom code requiring a reliable Project Manufacturing installation or implementation check should call the documented subprograms instead of reading the globals directly, because the globals are only meaningful after the relevant check routine has executed in the same session. Because locator value set maintenance alters flexfield structures, it should be run under controlled setup conditions conforming to the Bug 851461 fix logic.