Search Results jl_co_gl_conc_errs




Overview
Explore in AI Chat

Overview

JL.JL_CO_GL_CONC_ERRS is a transactional error-log table within the Oracle E-Business Suite Latin America Localizations (JL) product family. It records errors produced by the Generate Third Party Balances concurrent program, capturing the specific journal header and journal line combinations that failed validation or processing. Its defining behavioral characteristic is that the table is refreshed on every new submission of that concurrent program: rows therefore represent the state of the most recent run only, not a cumulative audit history. Because the program truncates or replaces prior content, the table should be regarded as an operational diagnostic surface rather than a permanent archive.

Under a heuristic Data Vault classification derived from its foreign-key structure, this object is best modelled as a link: it resolves associations among a concurrent process instance, a journal header, and a journal line, carrying descriptive error text as a non-key attribute. Its grain is one row per erroring journal line within a single process execution. The table is owned by the JL schema, holds status VALID, and is documented with ten physical columns in ETRM 12.2.2; the same definition applies to 12.1.1 installations of the Latin America localizations.

Key Information Stored

The documented structure comprises ten columns, of which the following carry substantive meaning:

  • PROCESS_ID — identifier of the concurrent program submission (process instance) that generated the error set. This is the primary grouping key for a run.
  • JE_HEADER_ID — the GL journal header affected by the error; refers to GL_JE_LINES.JE_HEADER_ID.
  • JE_LINE_NUM — the specific journal line number within that header; combined with JE_HEADER_ID, it identifies the failing line.
  • MESSAGE_TEXT — the human-readable error message describing why the line could not be processed.
  • IDENTIFIER — an additional descriptive identifier associated with the error record.
  • CREATED_BY, CREATION_DATE — standard WHO audit columns recording row insertion and the creating user.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns recording the most recent modification.

The surrogate primary key is JL_CO_GL_CONC_ERRS_PK, defined over the composite of PROCESS_ID, JE_HEADER_ID, and JE_LINE_NUM. Because this composite is both the primary key and the natural business key, no separate unique index is documented. Two foreign keys are declared: JE_HEADER_ID plus JE_LINE_NUM reference GL_JE_LINES, and PROCESS_ID references JL_CO_GL_CONC_CTRL, which holds the controlling record for each program run.

Common Use Cases and Queries

The primary scenario is post-run troubleshooting: an accountant submits Generate Third Party Balances, the program reports exceptions, and the error log is inspected to determine which journal lines failed and why. A typical query joins the log to the journal lines to recover accounting context:

  • SELECT e.process_id, e.je_header_id, e.je_line_num, e.message_text FROM jl.jl_co_gl_conc_errs e WHERE e.process_id = :p_process_id ORDER BY e.je_header_id, e.je_line_num;
  • Joining GL_JE_LINES on JE_HEADER_ID and JE_LINE_NUM to retrieve the entered debit/credit amount, currency, and code combination for each failed line.
  • Joining JL_CO_GL_CONC_CTRL on PROCESS_ID to correlate the error set with its controlling submission record.
  • Aggregating COUNT(*) grouped by MESSAGE_TEXT to identify the dominant failure category in a run.

Because content is replaced on each submission, downstream reporting should extract rows immediately after program completion if an audit trail is required. Never treat the table as historical; re-running the concurrent program destroys the prior error set.

Related Objects

  • JL_CO_GL_CONC_CTRL — controlling table for concurrent submissions; joined via PROCESS_ID.
  • GL_JE_LINES — General Ledger journal lines; joined via JE_HEADER_ID and JE_LINE_NUM.
  • GL_JE_HEADERS — journal header context for the failing lines, reachable through GL_JE_LINES.
  • JL_CO_GL_BALANCES and related JL third-party balance tables — the intended output of the program that this log monitors.
  • Generate Third Party Balances concurrent program — the sole documented writer of this table.
  • FND_CONCURRENT_REQUESTS — request-level metadata that can be correlated to PROCESS_ID for run timing and status.