Results for “account_code”

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

Overview

JL_CO_GL_TRX is a Latin America Localizations (JL) table that stores third-party transaction records representing General Ledger entries posted from multiple source systems, specifically for accounts that require NIT (tax identification number) tracking. The table functions as a staging and audit repository that links posted GL journal activity to the Colombian and broader Latin American statutory reporting requirements built into Oracle E-Business Suite. It is populated by concurrent programs registered under the JL_CO_GL_CONC_CTRL control table and is essential for generating fiscal reports that must reconcile GL balances with third-party documentation.

From a dimensional modeling perspective, the metadata's heuristic Data Vault classification for this object is link. This is consistent with its structure: it resolves relationships between several reference entities—NIT records, GL code combinations, sets of books, and JE batch/line identifiers—rather than acting as a standalone hub of a single business concept or as a descriptive satellite. Modelers should treat JL_CO_GL_TRX as a transaction-level link table that captures the association between GL journal lines and third-party NIT identities within a defined reporting period.

Key Information Stored

The table is documented with 26 columns in ETRM 12.2.2. The surrogate primary key is TRANSACTION_ID, defined by the JL_CO_GL_TRX_PK constraint. Business-key candidates include the combination of JE_HEADER_ID and JE_LINE_NUM, which uniquely identifies the source GL journal line, and the pairing of PERIOD_NAME with JE_BATCH_ID for batch-level grouping.

• TRANSACTION_ID – Surrogate primary key for each third-party transaction record.
• NIT_ID – Foreign key to JL_CO_GL_NITS, identifying the third party associated with the account.
• PROCESS_ID – Foreign key to JL_CO_GL_CONC_CTRL, tracking the concurrent process that generated the record.
• SET_OF_BOOKS_ID – Foreign key to GL_SETS_OF_BOOKS_11I, identifying the ledger.
• CODE_COMBINATION_ID – Foreign key to GL_CODE_COMBINATIONS, identifying the accounting flexfield.
• JE_BATCH_ID – Foreign key to GL_JE_BATCHES, identifying the source journal batch.
• JE_HEADER_ID and JE_LINE_NUM – Foreign reference to GL_JE_LINES, pinpointing the original journal line.
• PERIOD_YEAR, PERIOD_NUM, and PERIOD_NAME – Accounting period identifiers used for reporting segmentation.
• ACCOUNTING_DATE – The GL accounting date of the source transaction.
• CURRENCY_CODE – Currency of the entered amounts.
• ENTERED_DR / ENTERED_CR and ACCOUNTED_DR / ACCOUNTED_CR – Entered and accounted debit/credit amounts.
• CATEGORY, DOCUMENT_NUMBER, and SUBLEDGER_DOC_NUMBER – Journal category and source document references for traceability.

Common Use Cases and Queries

The primary use case is statutory third-party reporting for NIT-required accounts. A typical reconciliation query joins to GL_CODE_COMBINATIONS and JL_CO_GL_NITS to produce NIT-level transaction listings per period:

• Reconciling GL journal activity against third-party NIT records for tax and fiscal reporting.
• Auditing which concurrent process (PROCESS_ID) loaded a given set of transactions.
• Extracting period-level debit/credit balances by NIT and account for regulatory submissions.
• Drill-back queries from JL-CO-GL-TRX to the originating JE batch, header, and line records.

A representative query pattern selects TRANSACTION_ID, NIT_ID, ACCOUNT_CODE, PERIOD_NAME, ACCOUNTED_DR, and ACCOUNTED_CR, joining to JL_CO_GL_NITS on NIT_ID and filtering by SET_OF_BOOKS_ID and PERIOD_NAME.

Related Objects

• JL_CO_GL_NITS – joined on NIT_ID; holds third-party NIT master data.
• JL_CO_GL_CONC_CTRL – joined on PROCESS_ID; concurrent program control records.
• GL_CODE_COMBINATIONS – joined on CODE_COMBINATION_ID; accounting flexfield definitions.
• GL_SETS_OF_BOOKS_11I – joined on SET_OF_BOOKS_ID; ledger definitions.
• GL_JE_BATCHES – joined on JE_BATCH_ID; source journal batches.
• GL_JE_LINES – joined on JE_HEADER_ID and JE_LINE_NUM; source journal lines.

These relationships make JL_CO_GL_TRX a central link for tracing Latin American localization GL data from third-party identity through to the originating journal entry.