Search Results pjm_utils




Overview
Explore in AI Chat

Overview

APPS.PJM_UTILS is a PL/SQL package body in the Oracle E-Business Suite Projects (PA/PJM) schema. It is a utility package that supports the Project Manufacturing and Project Billing integration points, providing helper logic used by other project-related programs and forms. In the ETRM metadata for release 12.2.2 it carries an API classification of OTHER, and its object status is VALID in the APPS schema. The package encapsulates common lookups and calculations that would otherwise be duplicated across project manufacturing, costing, and period-close code — specifically, resolving demand quantities, determining the last open accumulation period, and defaulting WIP accounting classes for project tasks.

The package body does not expose a formal public API and is not referenced by any database object dependency listed in the ETRM extract, although it references itself (APPS.PJM_UTILS) and is referenced by two other packages. This indicates it functions as a shared internal helper library rather than a standalone callable interface.

Key Procedures and Functions

The documented package exposes three callable units:

Parameter lists are not documented in the ETRM extract and are therefore not reproduced here.

Tables Accessed

  • MTL_DEMAND — source of inventory demand quantity for GET_DEMAND_QUANTITY.
  • PA_PERIODS, GL_PERIODS, GL_SETS_OF_BOOKS — period definitions used by LAST_ACCUM_PERIOD to resolve the correct accumulation period.
  • PA_PROJECT_ACCUM_HEADERS — project accumulation header data supporting period determination.
  • PA_PROJECTS_ALL, PA_IMPLEMENTATIONS, PA_IMPLEMENTATIONS_ALL — project and implementation context, used to scope project and set-of-books parameters.
  • PJM_PROJECT_PARAMETERS — project manufacturing parameters that drive defaults.
  • PJM_TASK_WIP_ACCT_CLASSES, WIP_ACCOUNTING_CLASSES — WIP accounting class definitions used by DEFAULT_WIP_ACCT_CLASS.

Usage Notes

PJM_UTILS is typically invoked from within other PL/SQL packages or from project manufacturing and project costing concurrent programs that need to resolve demand quantities, accumulation periods, or WIP accounting class defaults. Because it is not directly referenced by any database object in the dependency data, it is most likely called from project manufacturing forms or custom extensions. Developers extending project manufacturing should call these functions rather than reimplementing the lookups, ensuring consistency with the standard period and accounting class logic. The package should not be modified in the APPS schema; customizations should be placed in a separate wrapper package.