Search Results ar_gta_import_rep_temp_s




Overview
Explore in AI Chat

Overview

AR_GTA_TXT_OPERATOR_PROC is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema that supports the Global Tax and Accounting (GTA) text-file interface used to move invoice, customer, and item data between external systems and Oracle Receivables. Its primary business role is to parse, validate, and load inbound delimited text files into the GTA staging and interface tables, and to generate corresponding outbound text extracts from Oracle Receivables transactions. In the context of the Oracle EBS 12.1.1 and 12.2.2 releases, the package forms part of the localization-oriented GTA text import infrastructure, complementing the standard AutoInvoice interface by offering a file-based interchange mechanism.

The documented metadata classifies the package under API classification OTHER and confirms a status of VALID. The package body depends on a broad set of APPS-level objects, including GTA-specific tables, Receivables transaction and batch tables, and Oracle Trading Community Architecture (TCA) entities, reflecting the mixed role of transaction import and reference data export.

Key Procedures and Functions

The ETRM metadata documents eleven callable units within the package body:

  • IMPORT_INVOICES — the principal routine that reads inbound text records and loads them into Receivables interface structures.
  • CLEAR_IMP_TEMP_TABLE — purges the temporary import-report staging table prior to or following an import run.
  • EXPORT_INVOICES_FROM_CONC — drives the export of invoice data when the package is launched from a concurrent program.
  • EXPORT_INVOICES_FROM_WORKBENCH — supports exporting invoice data when invoked from the Receivables Transactions workbench context.
  • EXPORT_CUSTOMERS — extracts customer and related TCA reference data into the outbound text format.
  • EXPORT_ITEMS — extracts item and inventory reference data for the outbound file.
  • GET_TRX_CLASS — resolves a transaction class value used to categorize records during processing.
  • CHECK_HEADER — validates header-level structure and content before a record is accepted.
  • CHECK_LINE_LENGTH — validates the physical or logical length of record lines to ensure the file conforms to the expected layout.
  • PUT_LINE — writes a formatted line to the output file or log.
  • PUT_LOG — writes diagnostic or processing messages to the log destination.

Tables Accessed

The package references GTA- and Receivables-specific tables through APPS synonyms. Transaction header and line staging data is managed through AR_GTA_TRX_HEADERS, AR_GTA_TRX_HEADERS_ALL, AR_GTA_TRX_LINES, AR_GTA_TRX_LINES_ALL, AR_GTA_TRXIMP_TMP, and the AR_GTA_IMPORT_REP_TEMP and AR_GTA_IMPORT_REP_TEMP_S tables, the latter being the subject of the user's search term. AR_GTA_SYSTEM_PARAMETERS and AR_GTA_SYSTEM_PARAMETERS_ALL supply runtime configuration. Receivables batch and transaction records are read from RA_BATCHES_ALL, RA_CUSTOMER_TRX_ALL, RA_CUST_TRX_TYPES_ALL, and RA_CUST_TRX_LINE_GL_DIST_ALL. Customer and party data is sourced from HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES, HZ_CUST_SITE_USES, HZ_PARTIES, HZ_LOCATIONS, HZ_CONTACT_POINTS, and HZ_PARTY_SITES. Item data is drawn from MTL_SYSTEM_ITEMS_B and related MTL tables. Flexfield metadata is accessed via FND_DESCR_FLEX_COLUMN_USAGES and FND_TERRITORIES_TL.

Usage Notes

The package is typically invoked from a Receivables concurrent program, from the Transactions workbench, or from custom PL/SQL that calls the export procedures. Standard practice is for a concurrent request to call IMPORT_INVOICES or the EXPORT_* routines, with FND_FILE used for output and logging. Administrators troubleshooting import or export errors should inspect AR_GTA_IMPORT_REP_TEMP and AR_GTA_IMPORT_REP_TEMP_S, which hold the reporting rows produced during processing.