Search Results export_invoices_from_workbench

Overview

APPS.JMF_GTA_TXT_OPERATOR_PROC is a server-side PL/SQL package belonging to the Oracle E-Business Suite Process Manufacturing (OPM) family, specifically the Global Tax Application (GTA) interface layer for Oracle Financials and Oracle Order Management. Its business purpose is to move master and transactional data between EBS and an external Global Tax Application through flat files. The package exports customers, items, and invoices to delimited text files that the third-party tax engine consumes, and provides the reciprocal procedure that imports data returned from the GT application through a flat file. The package is therefore an integration utility rather than a user-facing API; it bridges EBS application tables to an external tax determination and reporting system.

The source file is JMFRIETS.pls, and the header identifies a revision dated 2008/12/12 at version 120.4.12010000.3, indicating the file was shipped for the 12.1 release family and carried forward into 12.2.2. The package is owned by APPS and is classified by ETRM under the generic category OTHER, reflecting that it is a standalone utility package rather than a registered Open Interface or public API.

Key Procedures and Functions

ETRM documentation for this object lists no individually documented procedures or functions, so no parameter signatures are asserted here. The package specification itself, however, identifies the following entry points by name:

• EXPORT_CUSTOMERS — exports customer records from EBS to a flat file for consumption by the GT application. Historically it was modified to stop exporting the tax_payer_id attribute.
• EXPORT_ITEMS — exports item master records to a flat file. Its record structure was later revised to remove the tax_rate element.
• INVOICE_EXPORT — exports invoice data to the GT interface, supported by the INVOICE_IMPORT procedure that reads returned data.
• INVOICE_IMPORT — imports data from the GT application through a flat file. It was updated to accommodate TCA changes and, in a later revision, the CLEAR_IMP_TEMP_TABLE helper was made public.
• CLEAR_IMP_TEMP_TABLE — truncates or clears the temporary staging table used by the import routine so repeated loads do not accumulate stale rows.

The package also declares the record and collection types COLUMN_VALUES, g_noreference_tbl, g_item_rec, and g_item_tbl, which are used to hold item number, description, tax name, item model, and unit of measure values during export processing.

Tables Accessed

ETRM lists no tables referenced through APPS synonyms for this package, which is consistent with its use of dynamic SQL and file-based staging rather than direct documented DML against a fixed table list. The declared collection type g_noreference_tbl is anchored to MTL_SYSTEM_ITEMS_B_KFV.CONCATENATED_SEGMENTS, establishing that the item export path sources data from the item master key flexfield view. Customer and invoice export routines necessarily read the trading community and receivables invoice tables respectively, while INVOICE_IMPORT writes into the designated GT import staging table before downstream processing. Because procedure-level documentation is absent, precise table-to-procedure mapping cannot be confirmed from ETRM alone.

Usage Notes

The package is not referenced by any other documented package and is not exposed through an ETRM-registered API. In practice it is invoked from the concurrent manager, where export and import routines are scheduled as standalone programs to synchronize EBS with the external GT system on a periodic basis, typically during tax period close or at transaction cut-off. It may also be called from custom PL/SQL wrappers where an installation requires bespoke scheduling, file naming, or directory placement. Administrators must ensure the database directory object used for flat-file I/O is correctly configured and that the concurrent program definitions are present before execution. Because the file was last revised to address an internal bug fix, customers applying 12.2.2 should confirm the file version in use matches the shipped release level.