Search Results icx_por_failed_lines




Overview
Explore in AI Chat

Overview

The ICX_POR_FAILED_LINES table is a critical data object within the Oracle iProcurement (ICX) module of Oracle E-Business Suite (EBS) releases 12.1.1 and 12.2.2. It functions as a diagnostic and error-logging repository for the iProcurement loader processes. Specifically, it maintains detailed records of individual items, prices, or schema elements that were rejected during a bulk load job, such as those initiated through the Catalog Bulk Loader or other data import interfaces. Its primary role is to provide a persistent audit trail of load failures, enabling administrators and functional users to investigate, correct, and resubmit problematic data, thereby ensuring the integrity and completeness of the procurement catalog and related master data.

Key Information Stored

The table stores granular details for each failed record within a load job. Its structure is defined by a composite primary key consisting of JOB_NUMBER, LINE_NUMBER, and DESCRIPTOR_KEY. The JOB_NUMBER associates the failure with a specific parent batch job recorded in the ICX_POR_BATCH_JOBS table. The LINE_NUMBER typically identifies the sequence of the failed record within the source data file. The DESCRIPTOR_KEY is a crucial field that categorizes the type of failure or the specific attribute that caused the rejection, such as an invalid item, category, supplier, or price. While the provided ETRM metadata does not list all columns, standard complementary columns would include error messages, the rejected data values, and timestamps, forming a complete log for troubleshooting.

Common Use Cases and Queries

The primary use case is troubleshooting failed catalog or master data loads. A procurement administrator would query this table to generate a failure report after a load job completes with errors. A common SQL pattern involves joining to the ICX_POR_BATCH_JOBS table to get job context (e.g., filename, submitter, date).

  • Sample Query for Job Errors: SELECT f.job_number, f.line_number, f.descriptor_key, b.file_name, b.creation_date FROM icx_por_failed_lines f, icx_por_batch_jobs b WHERE f.job_number = b.job_number AND b.job_number = :p_job_no ORDER BY f.line_number;
  • Reporting Use Case: Operational reports can aggregate failure types (DESCRIPTOR_KEY) to identify systemic data quality issues, such as frequent invalid supplier site assignments or category mapping errors, guiding corrective master data maintenance.

Related Objects

The table has a defined, documented dependency on the ICX_POR_BATCH_JOBS table, which serves as the parent entity for all load jobs. The relationship is enforced via a foreign key constraint where ICX_POR_FAILED_LINES.JOB_NUMBER references ICX_POR_BATCH_JOBS. This is the primary relationship for contextualizing error lines. For a complete diagnostic workflow, one may also need to reference the loader interface tables (e.g., ICX_POR_ITEM_REQUESTS_INTERFACE) or the target master tables (e.g., MTL_SYSTEM_ITEMS_B, PO_AGENTS) to understand the valid values for the data element that caused the failure indicated by the DESCRIPTOR_KEY.