Search Results icx_por_failed_line_messages




Overview
Explore in AI Chat

Overview

The ICX_POR_FAILED_LINE_MESSAGES table is a critical diagnostic and error-logging table within the Oracle iProcurement (ICX) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. Its primary role is to maintain a detailed record of specific line-level failures that occur during the execution of a bulk data load job for requisition data. When the iProcurement loader processes items, prices, or schema elements from an external source and encounters validation or processing errors, it logs granular error messages for each failed element into this table. This provides administrators and functional users with a precise audit trail to identify, troubleshoot, and correct data issues that prevent successful requisition import, facilitating efficient data reconciliation and job re-submission.

Key Information Stored

The table's structure is designed to uniquely identify each error message in the context of a specific load job and line item. Its primary key is a composite of four columns, ensuring precise error location. Key columns include:

  • JOB_NUMBER: References the specific batch load job (from ICX_POR_BATCH_JOBS) during which the error occurred.
  • LINE_NUMBER: Identifies the specific line number within the source data file or interface that failed.
  • DESCRIPTOR_KEY: Provides an additional key, often used to identify a specific schema element or attribute within the line that caused the failure.
  • MESSAGE_NAME: Stores the internal name of the error message (typically corresponding to a message in the FND_NEW_MESSAGES table) that describes the reason for rejection.

Common Use Cases and Queries

The primary use case is troubleshooting failed iProcurement load jobs. A system administrator would query this table to obtain a detailed error report after a job completes with errors. A typical diagnostic query joins to the batch jobs table and the messages table for readable text:

SELECT flm.job_number,
       flm.line_number,
       flm.descriptor_key,
       flm.message_name,
       fnd.meaning AS message_text
  FROM icx.icx_por_failed_line_messages flm,
       icx.icx_por_batch_jobs          job,
       fnd_new_messages                fnd
 WHERE flm.job_number = :job_number
   AND flm.job_number = job.job_number
   AND flm.message_name = fnd.message_name(+)
   AND fnd.language = USERENV('LANG')
 ORDER BY flm.line_number;

This data is essential for generating corrective action reports, cleansing source data, and re-submitting corrected lines. It is also referenced by standard iProcurement error review interfaces.

Related Objects

The table has a direct and fundamental relationship with the ICX_POR_BATCH_JOBS table via a foreign key constraint on the JOB_NUMBER column. ICX_POR_BATCH_JOBS serves as the parent table, storing the header-level information for each load job, while ICX_POR_FAILED_LINE_MESSAGES stores the child error details. For obtaining user-friendly error text, the MESSAGE_NAME column typically relates to the MESSAGE_NAME column in the application message repository, FND_NEW_MESSAGES. This table is central to the iProcurement open interface (POR) loading process and is accessed by internal APIs and standard error review forms within the iProcurement responsibility.