Search Results jmf_gta_reports_pkg




Overview
Explore in AI Chat

Overview

APPS.JMF_GTA_REPORTS_PKG is a PL/SQL package in Oracle E-Business Suite that supports the Golden Tax Adaptor (GTA) functionality within Oracle's process manufacturing and financials reporting framework. As indicated by its header comment, the package "is used to generate Golden Tax Adaptor reports." The GTA is the interface by which Chinese statutory VAT invoices (Golden Tax invoices) are reconciled against the Oracle Receivables transactions that generated them, and this package supplies the reporting and comparison logic that surfaces discrepancies between the two data sets.

The package was created in 2005 and carries a revision header dated 2008/11/17 (JMFRREPS.pls 120.6.12010000.2). The revision comments reflect the module's evolution, including added procedures for header and line comparison, unmatched line retrieval, discrepancy XML and report generation, and later renames such as Get_Gt_Tax_Reg_Count to Get_Gt_Count. A 2007 change updated the G_MODULE_PREFIX global to align with FND logging standards, establishing the logging namespace as 'jmf.plsql.JMF_GTA_REPORTS_PKG'.

Key Procedures and Functions

The ETRM 12.2.2 metadata classifies this object as API classification OTHER and lists no documented procedures under the standard catalog extract. The package specification excerpt nevertheless records the following members, which are the basis of its public interface:

  • Get_Gt_Count — Returns a count of Golden Tax transactions associated with a given AR transaction. The header block documents it as accepting an AR transaction header id, a first-party tax registration number, and Golden Tax invoice date and invoice number ranges, returning a VARCHAR2. It was originally named Get_Gt_Tax_Reg_Count before the rename noted in the revision history.
  • Get_Gt_Trx and Get_Ar_Trx — Retrieval functions that fetch Golden Tax transaction data and corresponding Receivables transaction data respectively. Both were updated during the 2005–2006 revision cycle to support the comparison workflow.
  • Compare_Header and Compare_Lines — Comparison routines that evaluate Golden Tax invoice header and line data against the corresponding AR records to identify mismatches.
  • Get_Unmatched_Lines — Retrieves lines present in one system but not reconciled in the other, feeding the discrepancy reports.
  • Generate_Discrepancy_Xml and Generate_Discrepancy_Rep — Produce the discrepancy output in XML form and as a formatted report.
  • Generate_Mapping_Rep — Generates the mapping report linking AR transactions to Golden Tax invoices.

Tables Accessed

The ETRM metadata extract for this package lists no referenced tables via APPS synonyms, and none are declared in the specification excerpt shown. Functionally, the package operates over the Golden Tax Adaptor and Receivables data model: it reads AR transaction headers and lines (identified by the AR transaction header id parameter), and it reads Golden Tax invoice data (invoice date and invoice number ranges, first-party tax registration number) to perform its counts, comparisons, and discrepancy reporting. Because the documented catalog exposes no synonym list, specific table names should be confirmed by inspecting the package body in the target environment.

Usage Notes

Given the API classification OTHER and the absence of documented callers in the ETRM extract, JMF_GTA_REPORTS_PKG is best treated as an internal report-support package rather than a general-purpose public API. The user search term "get_gt_trxs" corresponds to the package's Golden Tax transaction retrieval capability (Get_Gt_Trx / Get_Gt_Count family). In practice, these routines are invoked from the Golden Tax Adaptor concurrent programs and related reporting flows that reconcile AR transactions to Golden Tax invoices, including the discrepancy and mapping reports. Custom code should call the documented public members only, and any call must supply the AR transaction header id and Golden Tax selection criteria. The package emits log messages under the FND logging prefix jmf.plsql.JMF_GTA_REPORTS_PKG, so diagnostics are available through the standard FND log mechanism during concurrent program execution.