Search Results gmp_despatch_load_rpt_pkg




Overview
Explore in AI Chat

Overview

APPS.GMP_DESPATCH_LOAD_RPT_PKG is a Process Manufacturing (OPM) reporting package that generates despatch and resource load reports in Oracle E-Business Suite 12.1.1 and 12.2.2. The package body encapsulates the logic required to submit, format, and deliver dispatch reports that present resource-level loading and despatch information for a given organization, resource range, and date range. It is classified in ETRM as an OTHER API, meaning it is invoked primarily through concurrent program submission rather than as a callable business API exposed to external integration.

The package maintains a set of global variables used to carry runtime context between the report-driving procedure and the XML/output generation routines. These globals include organization codes (G_forg, G_torg), resource identifiers and their instances (G_fres, G_tores, G_fres_instance, G_tores_instance), date boundaries (G_start_date, G_to_date), template information (G_template, G_template_locale), and instance/plan codes (G_inst, G_plan). The presence of G_template and G_template_locale reflects the package's reliance on XML Publisher (BI Publisher) template-driven output, where a report definition is matched to a template and its locale at runtime. The source header indicates the file GMPRDESB.pls at version 120.13, last modified 2012/03/29.

Key Procedures and Functions

The package exposes eleven documented procedures and functions:

  • PRINT_RES_DESP — The primary driver procedure, invoked with the concurrent request parameters (organization, resource range, instances, dates, template, and locale). It initializes the output return codes, resolves organization and resource codes into their internal identifiers, and orchestrates report submission.
  • PRINT_RES_LOAD — Generates the resource load report, paralleling PRINT_RES_DESP for the load-related output.
  • GME_RES_GENERATE_XML — Produces the XML payload consumed by the XML Publisher engine for the resource report.
  • APS_RES_GENERATE_XML — Produces the XML payload for the APS (Advanced Planning) resource variant of the report.
  • RESDL_GENERATE_OUTPUT — Assembles the final report output from the generated XML and template.
  • RD_XML_TRANSFER — Handles transfer of the generated XML document, supporting delivery of the report content.
  • GET_ORGN_CODE — Resolves an organization identifier into its organization code for display and XML tagging.
  • GET_INST_CODE — Returns the instance code corresponding to a given instance identifier.
  • GET_PLAN_CODE — Returns the plan code for a given plan identifier.
  • GET_RESOURCE_DESC — Returns the descriptive text for a resource.
  • GET_RESOURCE_INST — Resolves a resource instance value, used to normalize the resource-instance parameters passed into the report.

A local procedure, LOG_MESSAGE, writes diagnostic text into the package log buffer.

Tables Accessed

The package references the following objects through APPS synonyms:

  • MSC_DEPARTMENT_RESOURCES and MSC_DEPT_RES_INSTANCES — Provide the department resource definitions and their instances used to resolve resource codes and instance identifiers via GET_RESOURCE_DESC and GET_RESOURCE_INST.
  • MSC_APPS_INSTANCES — Supplies instance information resolved by GET_INST_CODE.
  • MSC_PLANS — Supplies plan definitions resolved by GET_PLAN_CODE.
  • GMP_RESDISP_XML_TEMP — A temporary staging table that holds the generated XML content before it is transferred to the output/reporting layer.
  • DBMS_LOB and DBMS_XMLGEN — Oracle-supplied packages used to construct and manipulate the large-object XML documents that form the report payload.

Usage Notes

GMP_DESPATCH_LOAD_RPT_PKG is designed to be invoked as a concurrent program in the Process Manufacturing responsibility. The concurrent program passes the report parameters—from and to organization, from and to resource, resource instances, start and end dates, XML template, and template locale—directly into PRINT_RES_DESP or PRINT_RES_LOAD. The template parameters (G_template, G_template_locale) drive the XML Publisher formatting step, so the request requires a valid template registered against the report definition.

Because the package is classified as OTHER and is referenced by zero other packages, it is not part of a shared API surface and should not be called from custom code without careful consideration. Direct invocation is possible but unsupported; the documented and intended path is through the standard concurrent request submission, which handles return codes and XML transfer through RD_XML_TRANSFER and RESDL_GENERATE_OUTPUT. The internal LOG_MESSAGE and global variables are not exposed and provide no external interface.