Search Results ps_generate_output

Overview

GMPPSRP is an Oracle EBS PL/SQL package owned by the APPS schema and classified under the generic "OTHER" API classification. It belongs to the Oracle Process Manufacturing (OPM) family of modules, as indicated by the "GMP" prefix, and supports the generation, formatting, and printing of Master Production Schedule (MPS) output. The package combines two distinct responsibilities: it drives the concurrent-program entry point for printing the Master Production Schedule through the gmp_print_mps procedure, and it provides the underlying XML generation and data lookup utilities used to assemble that report. It is declared with AUTHID CURRENT_USER, meaning its unqualified references resolve against the invoking user's schema, typically APPS via synonyms.

The package header carries an old revision marker ($Header: GMPPSRPS.pls 120.1 2005/07/19), which is consistent with a stable, long-lived reporting utility that has changed little across the 12.1.1 and 12.2.2 releases. Its role is largely read-only with respect to transactional data, acting as a reporting and presentation layer over the planning tables.

Key Procedures and Functions

The documented interface contains several public program units:

• GMP_PRINT_MPS — The concurrent-program entry point that accepts the standard errbuf and retcode OUT parameters plus a set of report-parameter arguments (organization, schedule, category set, structure, category, buyer, planner, organization, and item range values, and a template/locale pair) and produces the printed Master Production Schedule.
• PS_GENERATE_XML — Generates the XML representation of the MPS data set that feeds the report layout.
• PS_GENERATE_OUTPUT — The procedure most relevant to the user's search term "ps_generate_output." It converts the generated XML into the final rendered output format for printing or delivery.
• SCHEDULE — A function returning the descriptive name of a schedule given its schedule ID.
• CATEGORY_SET — A function returning the category set description from a category set ID.
• ITEM_NAME — A function returning an item's name from its inventory item ID and organization ID.
• ORGANIZATION_CODE — A function returning an organization's code from its organization ID.
• PLANNER_CODE — A function returning the planner code for a given item and organization.
• BUYER_NAME — A function returning the buyer name for a given item and organization.
• ONHAND_QTY — A function returning the on-hand quantity for a given item and organization.
• UNIT_OF_MEASURE — A function returning the unit of measure for a given item and organization.
• XML_TRANSFER — A utility to move or persist generated XML content.

These helpers isolate the report layout from the underlying planning and item master data, allowing the XML generation logic to resolve coded IDs into human-readable descriptions.

Tables Accessed

The package reads and writes a defined set of tables through APPS synonyms. The primary OPM planning tables are PS_SCHD_HDR (schedule header), PS_MATL_HDR and PS_MATL_DTL (material requirement headers and detail lines). Temporary XML content is staged in GMP_BUCKETED_XML_TEMP, and schedule master data is drawn from GMP_MATL_REP_ID_S. Item and category information is resolved from Oracle Inventory tables: MTL_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS_B, and MTL_SYSTEM_ITEMS_KFV; MTL_CATEGORIES_KFV and MTL_CATEGORY_SETS for categorization; and MTL_PARAMETERS for organization-level defaults. The package also uses the built-in packages DBMS_LOB, DBMS_SQL, and DBMS_XMLGEN to construct and manage XML documents, with DUAL used for simple scalar lookups.

Usage Notes

GMPPSRP is typically invoked from a concurrent program registered against GMP_PRINT_MPS, which supplies the report parameters and receives the completion status via errbuf and retcode. The XML generation and output procedures, including ps_generate_output, are called internally by that flow and are generally not invoked directly by end users. Because the package is declared AUTHID CURRENT_USER, any custom extension must be granted access to the underlying synonyms and should be executed from the APPS schema to resolve object references correctly. Organizations performing custom reporting against the same planning tables should treat these procedures as read-only helpers and avoid modification, as the package is not designed as a public write API. No other packages in the documented inventory reference GMPPSRP, indicating it is a top-level reporting consumer rather than a shared library.