Search Results ar_gta_trximp_tmp_u1

Overview

AR.AR_GTA_TRXIMP_TMP is a transient staging table in the Oracle E-Business Suite Receivables (AR) module, designed to hold value-added tax (VAT) invoice text loaded from external flat files. Its role is strictly intermediate: records are inserted by SQL*Loader, consumed by the VAT invoice import concurrent program, and then deleted once that program completes successfully. In Oracle EBS 12.1.1 and 12.2.2 the object resides in the APPS_TS_TX_DATA tablespace and is registered in FND Design Data as AR.AR_GTA_TRXIMP_TMP with a VALID status.

The table follows a generic, position-based layout rather than a normalized business model. It exposes a primary key, AR_GTA_TRXIMP_TMP_PK, defined on IMPORT_SEQ, and a single unique index, AR_GTA_TRXIMP_TMP_U1, also on IMPORT_SEQ. Because the metadata records no foreign key dependencies, ETRM classifies the object heuristically as a standalone data vault structure. In modeling terms it is best treated as a staging satellite rather than a durable hub or link; it carries descriptive import payload keyed by a load sequence and is not intended for long-term retention or downstream referential integrity.

Key Information Stored

The documented physical schema contains 35 columns. The most operationally significant are:

• IMPORT_SEQ — NUMBER; the primary key and sole component of the unique index AR_GTA_TRXIMP_TMP_U1. It is the surrogate sequence that identifies each imported record and serves as the business-key candidate for the staging load.
• COL1 through COL25 — twenty-five VARCHAR2(200) fields, each documented as "FIELD FROM FLAT FILE." These hold the positional values parsed from each input line and represent the actual VAT invoice text payload.
• LAST_UPDATE_DATE, CREATION_DATE — standard date columns recording creation and last modification timestamps.
• LAST_UPDATED_BY, CREATED_BY, LAST_UPDATE_LOGIN — standard Who columns identifying the user or process responsible for the row.
• PROGRAM_ID — concurrent program identifier of the request that last updated the row.
• PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — additional concurrent processing columns that tie the staging row to the specific import request.

Notably, the flat-file columns are unnamed in domain terms; meaning is derived entirely from the position and format of the source file, so interpretation requires the corresponding import definition rather than the table definition alone.

Common Use Cases and Queries

Because rows are deleted after import, the principal use cases are load validation, error diagnosis, and reconciliation of a specific concurrent request:

• Counting staged rows for a request before deletion: SELECT COUNT(*) FROM AR.AR_GTA_TRXIMP_TMP WHERE REQUEST_ID = :request_id;
• Inspecting raw positional fields: SELECT IMPORT_SEQ, COL1, COL2, COL3 FROM AR.AR_GTA_TRXIMP_TMP WHERE REQUEST_ID = :request_id ORDER BY IMPORT_SEQ;
• Auditing who loaded or last touched a batch using CREATED_BY, LAST_UPDATED_BY, CREATION_DATE, and LAST_UPDATE_DATE.
• Verifying sequence continuity on IMPORT_SEQ to detect gaps caused by failed SQL*Loader runs.
• Correlating the staging load with the import program through PROGRAM_ID, PROGRAM_APPLICATION_ID, and REQUEST_ID for concurrent manager troubleshooting.

Related Objects

The provided metadata documents no foreign keys, so relationships are functional rather than referential. The significant associated objects are:

• AR_GTA_TRXIMP_TMP_PK — the primary key constraint on IMPORT_SEQ.
• AR_GTA_TRXIMP_TMP_U1 — the unique index on IMPORT_SEQ, enforcing staging-row uniqueness.
• The VAT invoice import concurrent program that reads and subsequently deletes rows from this table.
• The SQL*Loader control file that populates COL1 through COL25 from the flat file.
• FND concurrent request tables, joined via REQUEST_ID, PROGRAM_ID, and PROGRAM_APPLICATION_ID, for load traceability.

All join relationships involving this object should be treated as operational correlates, not enforced foreign keys, consistent with its standalone classification and ephemeral lifecycle.