Search Results pmi_sales_pkg




Overview
Explore in AI Chat

Overview

APPS.PMI_SALES_PKG is a PL/SQL package body in the Oracle E-Business Suite Process Manufacturing Intelligence (PMI) schema family. It provides the sales analytics layer used by Process Manufacturing Intelligence reporting and dashboards, exposing the data retrieval logic that drives sales order, pricing, and charge analysis for process manufacturing organizations. The package is classified as a non-API utility (API classification: OTHER), meaning it is intended primarily for internal consumption by ETRM/PMI reporting components rather than as a public integration interface. It is dependent on both Oracle Order Management base tables and Process Manufacturing (OPM) order tables, which reflects its role in reconciling discrete order management data with OPM-specific order and charge structures.

Key Procedures and Functions

The package body exposes seven documented procedures and functions. Their purposes are as follows:

  • PMISA_GET_TOP_N — Retrieves a ranked "top N" set of sales results (for example top customers, items, or sales amounts) across the organization, using the parameters and thresholds supplied by the caller. It serves as the core ranking query used by PMI sales dashboards.
  • PMISA_GET_TOP_N_BY_OU — A variant of PMISA_GET_TOP_N that restricts the ranked result set to a single operating unit, allowing operating-unit-specific sales performance reporting.
  • PMISA_VALIDATE_DATE — Validates a supplied date (typically against the PMI GL calendar view) to confirm that it falls within an open or valid reporting period before the sales queries are executed.
  • PMISA_GET_CHARGE — Returns charge information associated with sales order lines, drawing on the OPM charges master and order charge tables so that freight, handling, or other applied charges are available to the reporting logic.
  • PMIOM_GET_CHARGE — The Order Management–oriented counterpart to PMISA_GET_CHARGE, resolving charge data through the OE pricing adjustment structures for order lines originating from the discrete order management flow.

Additional internal helper procedures are present in the body but are not part of the documented public surface. No parameter lists should be inferred; callers should reference the package specification before invoking any member.

Tables Accessed

The package reads and references a broad set of APPS synonyms spanning order management, process manufacturing, pricing, and reference data:

Usage Notes

PMI_SALES_PKG is invoked by ETRM/PMI reporting components and is referenced by three other database packages, indicating that it acts as a shared sales data provider within the PMI schema. It is not referenced by any external database object and is not intended as a public integration API. In practice it is called from PMI dashboard forms, concurrent programs, and custom analytic code that need ranked sales results, charge details, or date validation within the process manufacturing intelligence reporting model. Because it depends on OE_SYSTEM_PARAMETERS_ALL and GL calendar views, the effective operating unit and accounting context of the calling session must be correctly initialized. Customizations should wrap, not modify, the package, since it is shipped under the APPS schema and is subject to patching.