Results for “planner_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GMPPSRP is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite. It belongs to the Process Manufacturing (OPM) Planning family of objects and provides the runtime logic behind the Process Manufacturing Material Requirements Planning (MPS/MRP) reporting interface. Its principal business function is to generate and print process-shop-floor planning reports by extracting planned material supply and demand detail from the OPM planning tables (PS_MATL_HDR, PS_MATL_DTL, and PS_SCHD_HDR) and rendering that detail into a structured XML document, which is subsequently formatted for output through the concurrent manager.

The package name is closely associated with the global temporary/interface table GMP_MATL_REP_ID_S, which serves as the report identity sequence holder for material reporting runs. This explains why a search for gmp_matl_rep_id_s surfaces GMPPSRP: the package consumes the report instance identifier maintained through that object to bind a single execution run together with its material header and detail rows.

Key Procedures and Functions

The documented API surface comprises 14 procedures and functions, classified as OTHER (not a published open interface). They fall into three functional groupings:

• Report driver: GMP_PRINT_MPS is the top-level entry point that orchestrates a material planning report run, and SCHEDULE submits or arranges execution through the concurrent program framework.
• XML generation: PS_GENERATE_XML builds the planning XML payload, PS_GENERATE_OUTPUT converts that payload into formatted output, and XML_TRANSFER moves or writes the generated document. These work in conjunction with DBMS_XMLGEN and DBMS_LOB.
• Attribute lookups: CATEGORY_SET, CATEGORY, ITEM_NAME, ORGANIZATION_CODE, PLANNER_CODE, BUYER_NAME, ONHAND_QTY, and UNIT_OF_MEASURE are helper accessors that resolve coded values into their descriptive display forms for the report body.

Consistent with the metadata, no parameter signatures are documented for these units, and callers should treat them as internally scoped report utilities rather than a supported public API.

Tables Accessed

Through APPS synonyms the package reads and writes several categories of data:

• Planning tables: PS_MATL_HDR, PS_MATL_DTL, and PS_SCHD_HDR supply material header, material detail, and schedule header records — the core planning content of the report.
• Report identity and staging: GMP_MATL_REP_ID_S and the temporary table GMP_BUCKETED_XML_TEMP hold the run identifier and the bucketed XML output staged for formatting.
• Master and setup data: MTL_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS_B, MTL_SYSTEM_ITEMS_KFV, MTL_CATEGORIES_KFV, MTL_CATEGORY_SETS, and MTL_PARAMETERS provide item descriptions, category concatenations, category set definitions, and organization parameters used to enrich report rows.
• Utility objects: DBMS_LOB, DBMS_SQL, DBMS_XMLGEN, DUAL, and PLITBLM support CLOB handling, dynamic SQL, XML generation, and PL/SQL table operations.

Usage Notes

GMPPSRP is not referenced by any other database object, indicating it is invoked exclusively as a concurrent program entry point rather than being embedded in a form or called from custom code. Typical execution occurs when a planner or production scheduler submits the Process Manufacturing material planning report from the OPM planning responsibility; the concurrent manager then drives GMP_PRINT_MPS and related procedures, which use FND_REQUEST, FND_FILE, FND_MESSAGE, and FND_CONCURRENT to submit, log, and message the run. The resulting XML is written to the concurrent output file for printing or viewing.

Because the package depends on GMP_MATL_REP_ID_S for run identity and on the PS_ planning tables for content, report runs should be executed against a consistent planning snapshot to avoid partial or mismatched results. Customizations should avoid direct calls into these internals and instead use supported concurrent program interfaces.