Search Results icx_por_upload_it_dump




Overview
Explore in AI Chat

Overview

The ICX_POR_UPLOAD_IT_DUMP table is a core technical object within Oracle iProcurement (module ICX) in E-Business Suite releases 12.1.1 and 12.2.2. As documented, it functions as an internal staging table, providing temporary storage for data during the execution of bulk item and price load jobs. Its primary role is to facilitate the processing of large data sets uploaded via the iProcurement catalog administration interfaces, acting as a transient repository where raw upload data is held, validated, and transformed before being committed to permanent application tables. The table's status as an internal object indicates it is primarily managed by application code rather than accessed directly for transactional purposes.

Key Information Stored

The table's structure is designed to correlate individual data lines with a specific bulk upload job. Its two-column primary key, ICX_POR_UPLOAD_IT_DUMP_PK, consists of JOB_NUMBER and LINE_NUMBER. The JOB_NUMBER column is a foreign key that links each record to a master control record in the ICX_POR_BATCH_JOBS table, identifying the specific upload session. The LINE_NUMBER uniquely sequences each record within that job. While the specific data columns for item and price attributes are not detailed in the provided metadata, typical content would include raw upload fields such as item number, description, category, supplier, unit price, and effective dates, along with processing flags for validation errors and status.

Common Use Cases and Queries

The primary use case is supporting the backend process for the "Upload Items and Prices from a Spreadsheet" or similar bulk load functionality in iProcurement Catalog Administration. Data is inserted into this table during the initial upload phase. Common operational queries involve monitoring and troubleshooting active or failed load jobs. For instance, administrators may run a query to identify all records from a stalled job that encountered parsing or validation errors, which would typically involve joining to ICX_POR_BATCH_JOBS to get job metadata like creation date and status. A sample diagnostic SQL pattern is:

  • SELECT dump.* FROM icx_por_upload_it_dump dump, icx_por_batch_jobs job WHERE dump.job_number = job.job_number AND job.job_status = 'ERROR' AND job.creation_date > SYSDATE - 1;

Direct reporting or manipulation of this table is uncommon, as it is a temporary technical artifact. Data is purged or archived by the application upon job completion.

Related Objects

The table maintains a direct, documented foreign key relationship with the ICX_POR_BATCH_JOBS table, which serves as the parent control table for bulk upload operations. The relationship is defined as:

  • Foreign Key from ICX_POR_UPLOAD_IT_DUMP to ICX_POR_BATCH_JOBS: The column ICX_POR_UPLOAD_IT_DUMP.JOB_NUMBER references the ICX_POR_BATCH_JOBS table. This ensures every record in the dump table is associated with a valid batch job instance, maintaining referential integrity for the upload process.

This relationship is critical for joining transactional line data to job-level metadata such as the requester, submission time, and overall job status when performing process audits or diagnostics.