Search Results get_report_title

Overview

GMD_QCRCOA03_XMLP_PKG is an Oracle E-Business Suite PL/SQL package body owned by APPS and classified under the ETRM as OTHER. It supports the XML Publisher (BI Publisher) concurrent report associated with the Certificate of Analysis (COA) functionality in Oracle Process Manufacturing (OPM) Quality. The package header revision referenced in the source is QCRCOA03B.pls, last updated in December 2007, which places it firmly within the OPM COA reporting lineage that remains in use across EBS 12.1.1 and 12.2.2.

The package serves as the report logic container for an XML Publisher template. At runtime the Oracle Reports/XML Publisher bridge invokes its before-report, before-form, after-form, and after-report entry points, and resolves the printable report title from a lookup table rather than from a hard-coded literal. This design allows the printed certificate title to be localized or reconfigured without modifying the report definition itself.

Key Procedures and Functions

• CF_REPORT_NAMEFORMULA — A formula column function that accepts a report title code and returns the corresponding display meaning. It queries GEM_LOOKUPS for lookup type GMD_COA_REPORT_TITLE using the supplied code, and returns the resolved title string for the report layout.
• QCRCOA01_HEADER — A header-level procedure that performs no processing (a NULL body). It exists to satisfy the report layout's expected entry point and to preserve backward compatibility with the report definition.
• BEFOREREPORT — Initialization function executed before the report runs. It captures the concurrent request identifier from FND_GLOBAL.CONC_REQUEST_ID into P_CONC_REQUEST_ID so that subsequent logic and any output file handling can reference the request. It returns TRUE to signal successful setup.
• BEFOREPFORM — Executed before the report parameter form is rendered. It returns TRUE unconditionally, acting as a well-defined hook in the report execution sequence.
• AFTERPFORM — Executed after the parameter form is completed. This is the substantive control block: it declares cursors to resolve report titles from GEM_LOOKUPS and GMD_COA_HEADERS, a blank-title fallback cursor, a parameter record typed to GMD_COA_DATA_OM_NEW.T_COA_PARAMETERS, and cursors that count rows in the COA header, detail, specification text, and result text tables, plus an API version constant defaulting to 1.5.
• AFTERREPORT — Post-processing function invoked after report output is produced. ETRM lists it among the documented entry points, though its body is not included in the excerpt; it typically releases resources and finalizes the request.
• PRINT_TEXT_FLAG_P — A documented procedure associated with controlling whether long specification or result text is printed on the certificate output.

Tables Accessed

• GEM_LOOKUPS — Read via lookup type GMD_COA_REPORT_TITLE to translate a report title code into its printed meaning, and to supply a blank-title fallback through code 'BLK'.
• GMD_COA_HEADERS — Read to drive report title resolution and to count certificate headers, establishing which COAs qualify for the run.
• GMD_COA_DETAILS — Read to count and retrieve certificate detail lines for the report body.
• GMD_COA_SPEC_TEXT and GMD_COA_SPEC_HDR_TEXT — Read to obtain specification narrative text at line and header level for inclusion on the certificate.
• GMD_COA_RSLT_TEXT — Read to obtain result narrative text associated with certificate results.

Usage Notes

The package is invoked indirectly by the Oracle XML Publisher concurrent program that produces the Certificate of Analysis, identified by the QCRCOA03 naming convention. It is not referenced by any other PL/SQL package according to the ETRM dependency data. Parameter submission values are passed into AFTERPFORM, where the request identifier captured in BEFOREREPORT is available alongside the resolved report title. Operational behavior depends on the report title lookup being populated with the codes used by the submitted report; if a requested title code is absent from GEM_LOOKUPS, the query in CF_REPORT_NAMEFORMULA raises NO_DATA_FOUND. Because the package is a report-support artifact rather than a public API, customizations should be confined to the underlying lookup data, report templates, and the concurrent program parameters rather than to the package body itself, which remains under APPS ownership.