Search Results p_mstk_struct

Overview

INV_INVISMMX_XMLP_PKG is an Oracle E-Business Suite PL/SQL package owned by APPS that underpins the Oracle Inventory Min-Max Reordering report, exposed through the XML Publisher (BI Publisher) concurrent program framework. The package is declared with AUTHID CURRENT_USER, meaning its SQL executes with the privileges of the invoking user rather than the definer, which is standard practice for XML Publisher report packages in EBS. Its principal role is to hold the runtime state and bind variables that drive the Min-Max report query: the package does not itself define a rich set of public APIs, but instead exposes a flat namespace of package-level variables that an XML Publisher data template, an Oracle Reports bridge, or an internal packaged query consumes during report execution.

The report addresses inventory replenishment planning. Min-Max planning compares on-hand and available quantities against user-defined minimum and maximum stocking levels and produces suggested replenishment actions. This package supports the report variants that let users filter by item, category, subinventory, organization, and WIP batch, and that control how reservations, non-nettable subinventories, WIP demand, and purchase order supply are treated when computing net requirements.

Key Procedures and Functions

The ETRM metadata documents two callable program units within the package:

• BEFOREREPORT — Invoked by the XML Publisher/report engine before the main data query is executed. Its purpose is to perform pre-report initialisation: resolving and populating the numerous package-level bind variables (such as the item, category, and range selection strings) from the concurrent program parameters, and establishing the runtime context the report body depends upon. Because so many package variables carry default values (for example P_INCLUDE_NONNET := 1, P_NET_WIP := 2, P_HANDLE_REP_ITEM := 3), BEFOREREPORT is the point at which those defaults are reconciled with user-supplied parameter values.
• AFTERREPORT — Invoked after the main report query completes. It serves as the post-processing hook for the report, typically used to release or reset the package's session state and to finalise any derived values needed by the report layout.

No public functions such as a P_ITEM_SELECT function are documented; the user's search term p_item_select corresponds to the package-level variable P_ITEM_SELECT VARCHAR2(1000), a bind variable holding the item selection fragment rather than a callable API.

Tables Accessed

The package references the following tables through APPS synonyms:

• INV_MIN_MAX_TEMP — The report's working/temporary table holding the computed min-max replenishment rows for the current run; the report query populates and reads this structure.
• MTL_CATEGORY_SETS and MTL_DEFAULT_CATEGORY_SETS — Used to resolve the category set and default category set associated with the category selection parameters (for example P_CAT_SET_ID).
• FND_ID_FLEX_STRUCTURES — Read to determine the key flexfield structure, supporting the P_MSTK_STRUCT and P_MCAT_STRUCT variables that identify the item and category structures in use.
• FND_USER — Provides the current user context referenced by P_USER_ID.
• HR_ALL_ORGANIZATION_UNITS_TL — Supplies the translated organisation name used to populate P_ORG_NAME for the report header.

Usage Notes

This package is not intended for direct invocation by custom code. It is a report-support package: the Min-Max Reordering concurrent program (an XML Publisher report registered against INVISMMX) executes BEFOREREPORT, runs the report query that consumes the package variables, and then calls AFTERREPORT. The ETRM metadata confirms it is referenced by zero other packages, reinforcing that its surface is private to the report infrastructure.

Customisation should be limited to registering the concurrent program, adjusting its parameters, or supplying a modified XML template; altering the package body is unsupported. Because the package relies on AUTHID CURRENT_USER and on APPS synonyms, any custom wrapper must run from a context where those synonyms and the INV schema objects are visible, and must respect the session-level nature of the package variables, which persist for the duration of the database session running the report.