Search Results clear_imp_temp_table




Overview
Explore in AI Chat

Overview

AR_GTA_TXT_OPERATOR_PROC is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It supports the Global Tax Analyzer (GTA) subsystem within Oracle Receivables, providing the transactional engine responsible for the text-based import and export of invoice, customer, and item data. The package bridges external flat-file or delimited data with the Receivables transaction tables, enabling bulk load and extraction operations that would otherwise require manual entry through the Receivables forms. It carries an API classification of OTHER, indicating it is an internal utility package rather than a formally published public API. The package status is VALID in the documented environment.

Key Procedures and Functions

The ETRM metadata documents eleven procedures and functions. Their names indicate the following responsibilities:

  • PUT_LINE / PUT_LOG — Output and logging utilities used throughout the import and export routines to record progress, diagnostics, and error messages.
  • IMPORT_INVOICES — The primary inbound routine that loads invoice data from the staging construct into the Receivables interface structures.
  • CLEAR_IMP_TEMP_TABLE — Housekeeping routine that purges residual rows from the temporary import table between runs.
  • EXPORT_INVOICES_FROM_CONC / EXPORT_INVOICES_FROM_WORKBENCH — Outbound routines that generate invoice export data, invoked respectively from a concurrent program context and from the Receivables Workbench.
  • GET_TRX_CLASS — Resolves the transaction class associated with a given transaction, used to drive validation and routing logic.
  • CHECK_HEADER / CHECK_LINE_LENGTH — Validation functions that verify structural integrity of header records and enforce maximum line-length constraints before data is committed.
  • EXPORT_CUSTOMERS / EXPORT_ITEMS — Extraction routines that emit customer and item master data in the format required by the GTA text interface.

Tables Accessed

The package operates against a well-defined set of APPS synonyms. Transaction storage centers on AR_GTA_TRX_HEADERS, AR_GTA_TRX_HEADERS_ALL and their sequence (AR_GTA_TRX_HEADERS_ALL_S), together with AR_GTA_TRX_LINES, AR_GTA_TRX_LINES_ALL and AR_GTA_TRX_LINES_ALL_S. Staging and reporting data are handled through AR_GTA_IMPORT_REP_TEMP, AR_GTA_IMPORT_REP_TEMP_S and AR_GTA_TRXIMP_TMP. Configuration and runtime parameters are read from AR_GTA_SYSTEM_PARAMETERS and AR_GTA_SYSTEM_PARAMETERS_ALL. Descriptive flexfield metadata is obtained from FND_DESCR_FLEX_COLUMN_USAGES, territory names from FND_TERRITORIES_TL, contact point data from HZ_CONTACT_POINTS, and customer account data from HZ_CUST_ACCOUNTS. Item information is sourced from MTL_SYSTEM_ITEMS_B_KFV. The package also depends on the helper package AR_GTA_TRX_UTIL.

Usage Notes

AR_GTA_TXT_OPERATOR_PROC is referenced by the concurrent program package AR_GTA_CONC_PROG and by itself, confirming that it is invoked primarily through GTA concurrent programs rather than directly from a form. Export routines additionally support invocation from the Receivables Workbench for user-initiated extractions. Because the package is classified as OTHER and is not a documented public API, customizations should treat it as internal: supported integration points are the GTA concurrent programs that call it, and direct calls from custom code carry upgrade risk. Sites implementing GTA should ensure the referenced staging and header tables are properly sized and that CLEAR_IMP_TEMP_TABLE is executed between cycles to prevent stale data from contaminating subsequent imports.