Search Results gr_xml_reports

Overview

APPS.GR_XML_REPORTS is a PL/SQL package delivered as part of the Oracle E-Business Suite Process Manufacturing (OPM) product family, where the "GR" prefix denotes its association with the Oracle Global Regulatory (GR) module. The package provides server-side support for XML-based regulatory reporting, most notably generating the dispatch history report that traces the movement of regulated items and ingredients between recipients and locations. Its purpose is to bridge the GR data model — including hazardous material identifiers such as CAS numbers and ingredient item definitions — with XML output that can be rendered, archived, or transmitted to internal and external parties. The package encapsulates both report-generation logic and a general-purpose XML transfer routine, allowing callers to produce structured XML documents without embedding query and formatting logic in client code. It is classified as an "OTHER" API, meaning it is not a public, general-purpose business API but a specialized utility used by GR-related concurrent programs and forms. The header comment indicates a last significant revision in 2005, consistent with a stable, mature utility that has persisted across the 12.1.1 and 12.2.2 releases with little functional change.

Key Procedures and Functions

• DISPATCH_HISTORY_REPORT — The primary report procedure. It is a standard concurrent-program entry point that returns the conventional errbuf and retcode out parameters, enabling it to be registered and executed as an Oracle EBS concurrent request. Its input parameters allow the caller to scope the report by organization, item range, recipient range, document category range, date-sent range, CAS number, and a specific ingredient item identifier. A final p_order_by parameter controls the sort sequence of the report output, giving users flexibility over how dispatch records are presented. The procedure assembles the qualifying dispatch history records into XML form for downstream rendering or transfer.
• XML_TRANSFER — A utility procedure that accepts a CLOB containing XML content and handles its transfer or persistence. Because it takes only the XML payload, it acts as a reusable helper for moving generated XML documents to their destination, decoupled from the report's query logic.

Both procedures are declared in the package specification, exposing them to other PL/SQL callers and to concurrent program registration.

Tables Accessed

According to the documented metadata, the package references the DBMS_LOB and DBMS_XMLGEN supplied packages through APPS synonyms. DBMS_XMLGEN is the Oracle-supplied PL/SQL package that converts arbitrary SQL query results into XML documents, and its presence confirms that DISPATCH_HISTORY_REPORT builds its XML output dynamically by passing queries to DBMS_XMLGEN rather than constructing XML strings manually. DBMS_LOB indicates that the resulting XML document, held as a CLOB, is manipulated using large-object operations — for reading, appending, or transferring the payload handled by XML_TRANSFER. No base application tables are listed in the documented metadata; the package's data access occurs through the SQL queries fed to DBMS_XMLGEN, whose target tables are not enumerated in the source excerpt. In practice these queries draw from the GR dispatch, item, recipient, and ingredient tables that underpin the dispatch history report.

Usage Notes

The package is most commonly invoked in two ways. First, DISPATCH_HISTORY_REPORT is registered as an Oracle EBS concurrent program, so users launch the Dispatch History Report from the standard concurrent request submission form (or its OPM/GR menu equivalent), supplying the organization, item, recipient, category, and date ranges as report parameters. The concurrent manager then calls the procedure and captures the XML output for delivery through the standard output and log mechanism. Second, because both procedures are declared in the package specification, custom extensions — such as a custom concurrent program, an Oracle Forms trigger, or a BPEL/XML gateway integration — can call them directly to retrieve dispatch history XML or to route an existing XML CLOB via XML_TRANSFER. Organizations integrating GR data with external regulatory or hazardous-materials systems typically invoke XML_TRANSFER to hand the generated document to an outbound interface. As an "OTHER"-classified utility referenced by no other documented packages, GR_XML_REPORTS should be treated as a self-contained reporting aid rather than a core dependency of other application logic, and any customization should preserve the documented parameter signatures of DISPATCH_HISTORY_REPORT to avoid breaking concurrent program registration.