Search Results jl_co_gl_conc_ctrl




Overview
Explore in AI Chat

Overview

JL_CO_GL_CONC_CTRL is a control and audit table in the JL (Latin America Localizations) product family of Oracle E-Business Suite. It stores one log row for every submission of the Generate Third Party Balances concurrent program. Because that program builds withholding and third-party balance records that feed General Ledger, the table provides the run-level bookkeeping required to trace individual submissions, correlate the transactions and errors they produced, and link a reversal run back to the submission it reversed.

The table is owned by the JL schema and resides in the APPS-enabled database tier; it carries no end-user maintenance responsibility and is populated exclusively by concurrent processing. Its documented structure is eleven columns, with a single unique index on PROCESS_ID and a primary key constraint JL_CO_GL_CONC_CTRL_PK over the same column. From an analytical modeling perspective, the foreign-key topology (a self-referencing reversal link plus a reference to GL_SETS_OF_BOOKS_11I, and inbound references from JL_CO_GL_TRX and JL_CO_GL_ERRS) suggests a hub-leaning classification: PROCESS_ID behaves as the durable business key around which transaction and error detail — effectively satellite content — is clustered.

Key Information Stored

  • PROCESS_ID — surrogate primary key and the unique business-key candidate documented through JL_CO_GL_CONC_CTRL_U1. It identifies a single submission of the Generate Third Party Balances program and is the join key to all dependent detail tables.
  • SET_OF_BOOKS_ID — the ledger for which balances were generated; foreign key to GL_SETS_OF_BOOKS_11I.
  • PERIOD_NAME — the accounting period covered by the submission.
  • STATUS — run outcome indicator, used to distinguish successful, failed, or incomplete processing.
  • BALANCE_CALCULATED — flag indicating whether third-party balances were actually computed for the run.
  • REVERSED_PROCESS_ID — self-referencing foreign key pointing to the PROCESS_ID of the run that this submission reverses, enabling reversal chain tracing.
  • CREATED_BY, CREATION_DATE — standard WHO columns recording the submitting user and submission timestamp.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — audit columns capturing the most recent modification to the control row.

Common Use Cases and Queries

Support and period-close teams query this table to determine whether third-party balances were generated for a given ledger and period, to identify failed or incomplete runs, and to establish which transactions belong to which submission.

  • Run history by ledger and period: select PROCESS_ID, PERIOD_NAME, STATUS, BALANCE_CALCULATED from JL_CO_GL_CONC_CTRL where SET_OF_BOOKS_ID = :ledger and PERIOD_NAME = :period order by CREATION_DATE desc.
  • Failure triage: join JL_CO_GL_ERRS on PROCESS_ID to list the error messages emitted by each non-successful submission.
  • Detail reconstruction: join JL_CO_GL_TRX on PROCESS_ID to return every third-party transaction generated by a specific run.
  • Reversal analysis: self-join the table on REVERSED_PROCESS_ID = PROCESS_ID to map original submissions to their reversing runs, or use a hierarchical query (CONNECT BY PRIOR PROCESS_ID = REVERSED_PROCESS_ID) to walk multi-step reversal chains.

Related Objects

  • JL_CO_GL_CONC_CTRL — self-reference via REVERSED_PROCESS_ID to PROCESS_ID; models reversal relationships between submissions.
  • GL_SETS_OF_BOOKS_11I — referenced through SET_OF_BOOKS_ID; supplies ledger context.
  • JL_CO_GL_TRX — references this table on PROCESS_ID; holds the third-party transactions produced by each run.
  • JL_CO_GL_ERRS — references this table on PROCESS_ID; holds error rows logged during processing.
  • Generate Third Party Balances concurrent program — the JL program that inserts and updates the control rows in this table.