Search Results gml_audit_reports




Overview
Explore in AI Chat

Overview

GML_AUDIT_REPORTS is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite, classified as a valid database object in both release 12.1.1 and 12.2.2. It belongs to the Process Manufacturing (GML) family of modules and supports the reconciliation and audit of purchasing activity against process manufacturing expectations. Specifically, the package provides the query logic required to compare Oracle Financials (OFI) purchase order line data with corresponding process manufacturing (GEMMS / GMS) records, thereby enabling auditors and operations staff to identify discrepancies between ordered quantities, matched line counts, and total costs across the two sources.

The object is not referenced by any other database object, which indicates that it functions as a terminal consumer of shared data — a reporting and validation package rather than a shared application programming interface invoked by dependent code. Its dependency list confirms this role: it draws on order management, inventory, and process manufacturing tables and returns derived counts and cost aggregates.

Key Procedures and Functions

The ETRM metadata documents 13 callable units within the package body, organized into several logical groupings.

  • GET_OFI_LINE_COUNT — returns the count of purchase order lines originating from the OFI (Oracle Financials) source.
  • GET_OFI_BLINE_COUNT — returns the count of OFI backup or secondary (B) lines, typically used to isolate lines associated with blanket or secondary purchase documents.
  • GET_OFI_TOTAL_COST — aggregates the total cost of OFI purchase order lines.
  • GET_OFI_BTOTAL_COST — aggregates the total cost for the corresponding OFI backup line set.
  • GET_GEMMS_LINE_COUNT — returns the count of process manufacturing (GEMMS/GMS) lines for comparison with the OFI figures.
  • GET_GEMMS_BLINE_COUNT — returns the count of process manufacturing backup lines.
  • GET_GEMMS_TOTAL_COST — aggregates total process manufacturing cost.
  • GET_GEMMS_BTOTAL_COST — aggregates the backup-set process manufacturing cost.
  • MATCH_OFI_GMS_PO_LINE — performs the core comparison that aligns OFI and GMS purchase order lines, forming the basis of the audit reconciliation.
  • CHK_OFI_GMS_POLN_ITM — validates item consistency between the OFI and GMS purchase order lines.
  • CHK_OFI_GMS_POLN_STS — validates status consistency between the OFI and GMS purchase order lines.
  • GET_PO_NUM — retrieves the purchase order number associated with a given record.
  • GET_REL_NUM — retrieves the associated release number, supporting release-level auditing.

No parameter lists are documented in the ETRM metadata; the above descriptions reflect the naming conventions and functional groupings evident from the documented inventory.

Tables Accessed

The package reads from the following tables, accessed through APPS synonyms:

  • PO_LINES_ALL — the primary source of purchase order line information used for line counts, item matching, and cost aggregation.
  • PO_LINE_LOCATIONS_ALL — supplies shipment and receipt-oriented line detail used in status and quantity checks.
  • PO_ORDR_DTL — provides additional order detail for reconciliation.
  • MTL_SYSTEM_ITEMS — validates item definitions across the inventory master.
  • IC_ITEM_MST — the process manufacturing item master, used to cross-reference item identities.
  • CPG_ORAGEMS_MAPPING — the mapping table linking Oracle Financials and GEM/GMS data, central to matching OFI and GMS lines.
  • DUAL — used for single-row evaluations and constant returns.

All access appears to be read-only, consistent with an audit and reporting role.

Usage Notes

GML_AUDIT_REPORTS is typically invoked from concurrent programs, custom audit reports, or process manufacturing reconciliation procedures that need to compare OFI purchase activity against GMS records. Because it is not referenced by other database objects, it is best treated as a reporting utility rather than a reusable API. The package depends on STANDARD and other APPS objects and should be preserved with the same privileges as the APPS schema. When reviewing audit exceptions, the line-count and total-cost functions are normally run together with the matching and checking functions to produce a complete reconciliation picture.