Results for “program_login_id”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

ICX_POR_FAILED_LINE_MESSAGES is a transactional table in the ICX (Oracle iProcurement) product schema. It maintains information about items, prices, and schema elements that the loader rejected during a load job. As part of the iProcurement PunchOut and content-loading infrastructure, this table serves as the error-and-rejection register for batch content ingestion, capturing each line-level failure with an associated diagnostic message so that administrators can troubleshoot why a given catalog, price list, or schema element did not load successfully.

In Data Vault modeling terms, the ETRM metadata classifies this object as satellite-leaning, based on a heuristic mined from its foreign-key structure. This suggests modeling the table as a satellite attached to the batch job hub represented by ICX_POR_BATCH_JOBS, with JOB_NUMBER acting as the hub reference key and the remaining descriptive attributes (line number, descriptor key, message name, token list) functioning as the satellite payload.

Key Information Stored

The table exposes nine documented columns in the 12.2.2 physical schema. The most significant are summarized below.

  • JOB_NUMBER — Identifies the batch load job during which the rejection occurred. This is the primary join key back to ICX_POR_BATCH_JOBS and is a component of the primary key.
  • LINE_NUMBER — Identifies the specific line within the load job that failed. Also a component of the composite primary key.
  • DESCRIPTOR_KEY — Identifies the descriptor (item, price, or schema element) associated with the rejected line. Third component of the composite primary key.
  • MESSAGE_NAME — The name of the failure or rejection message applied to the line. Fourth component of the composite primary key.
  • TOKEN_LIST — Holds the tokenized substitution values used to render the message text at runtime.
  • REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_LOGIN_ID — Standard concurrent-program context columns identifying the request and program that produced the record.

The surrogate primary key is defined through ICX_POR_FAILED_LINE_MESSAGE_PK, a composite key over JOB_NUMBER, LINE_NUMBER, DESCRIPTOR_KEY, and MESSAGE_NAME. Because the primary key already combines business-meaningful attributes, no separate unique index is documented; the PK itself serves as the natural business-key candidate for the failed-line message grain.

Common Use Cases and Queries

The primary use case is diagnosing content-load failures. Administrators query the table after a failed or partially successful load job to determine which lines were rejected and why. A typical query lists all messages for a given job:

  • SELECT job_number, line_number, descriptor_key, message_name, token_list FROM icx.icx_por_failed_line_messages WHERE job_number = :job ORDER BY line_number;

A second pattern correlates failures to the batch job header to obtain job context and timing:

  • SELECT f.job_number, f.line_number, f.message_name, b.* FROM icx.icx_por_failed_line_messages f JOIN icx.icx_por_batch_jobs b ON b.job_number = f.job_number;

Reporting scenarios include counting rejection messages per job to gauge load quality, ranking the most frequent MESSAGE_NAME values to spot systemic content or mapping defects, and extracting TOKEN_LIST values to reconstruct human-readable diagnostics for support tickets.

Related Objects

The following objects are most significant in relation to this table, based on the documented foreign-key and primary-key relationships.

  • ICX_POR_BATCH_JOBS — Referenced by ICX_POR_FAILED_LINE_MESSAGES.JOB_NUMBER. The parent job record; join on JOB_NUMBER.
  • ICX_POR_FAILED_LINE_MESSAGE_PK — The primary-key constraint defined over JOB_NUMBER, LINE_NUMBER, DESCRIPTOR_KEY, and MESSAGE_NAME.
  • iProcurement content-loading concurrent programs — Identified through REQUEST_ID, PROGRAM_APPLICATION_ID, and PROGRAM_ID; these programs insert the rejection rows.
  • iProcurement PunchOut and catalog-load processes — The functional consumers that generate failed lines recorded here.

Because the documented metadata is limited, additional dependent views or APIs are not asserted; the relationships above reflect the FK and PK data supplied in the ETRM record.