Search Results cn_ledger_journal_entries_all




Overview
Explore in AI Chat

Overview

The CN_LEDGER_JOURNAL_ENTRIES_ALL table is a core transactional data object within the Oracle E-Business Suite Incentive Compensation module (CN). It stores the individual line items that constitute journal entries in the compensation ledger. This table functions as the detailed line-level repository for all accounting entries generated from incentive compensation calculations and adjustments. Its role is critical for maintaining the financial integrity of the compensation process, enabling the tracking of accruals, expenses, and payments at a granular level for reporting, reconciliation, and audit purposes. As an "ALL" table, it is partitioned by operating unit (ORG_ID) to support multi-organization architectures in both EBS 12.1.1 and 12.2.2.

Key Information Stored

Each record represents a single debit or credit line within a journal entry batch. The primary identifier is the LEDGER_JE_ID. Essential columns include BATCH_ID, which links the line to its parent journal batch header in CN_LEDGER_JE_BATCHES_ALL, and SRP_PERIOD_ID, which associates the entry with a specific compensation period defined in CN_SRP_PERIODS_ALL. The BALANCE_ID column references the type of balance (e.g., accrued liability, expense) from CN_LEDGER_BAL_TYPES_ALL_B. Other critical data points stored are the monetary AMOUNT, the accounting CODE_COMBINATION_ID for the general ledger account, and the ORG_ID for multi-org partitioning. The table also typically includes standard EBS audit columns like CREATION_DATE and LAST_UPDATE_DATE.

Common Use Cases and Queries

This table is central to financial reporting and audit trails for incentive compensation. Common use cases include reconciling the compensation ledger to the general ledger, analyzing compensation expenses by period or balance type, and investigating the detailed composition of journal batches. A typical query involves joining to related header and reference tables to produce a readable journal entry report. For example:

  • Period-to-Date Expense Analysis: Querying sum(AMOUNT) grouped by BALANCE_ID and SRP_PERIOD_ID for a given ORG_ID.
  • Journal Entry Drill-Down: Selecting all lines for a specific BATCH_ID to review the full accounting impact of a compensation run.
  • GL Reconciliation: Joining on CODE_COMBINATION_ID to match CN ledger lines with GL journal import data.

Sample SQL pattern:
SELECT clje.amount, clje.code_combination_id, csrp.period_name, clbt.name balance_type
FROM cn_ledger_journal_entries_all clje,
cn_srp_periods_all csrp,
cn_ledger_bal_types_all_b clbt
WHERE clje.srp_period_id = csrp.srp_period_id
AND clje.balance_id = clbt.balance_id
AND clje.org_id = 123;

Related Objects

The CN_LEDGER_JOURNAL_ENTRIES_ALL table maintains defined foreign key relationships with several key CN module tables, forming the backbone of the compensation ledger structure.

  • CN_SRP_PERIODS_ALL: Joined via CN_LEDGER_JOURNAL_ENTRIES_ALL.SRP_PERIOD_ID. This links each journal line to the compensation calendar period.
  • CN_LEDGER_JE_BATCHES_ALL: Joined via CN_LEDGER_JOURNAL_ENTRIES_ALL.BATCH_ID. This provides the header-level batch information and control totals.
  • CN_LEDGER_BAL_TYPES_ALL_B: Joined via CN_LEDGER_JOURNAL_ENTRIES_ALL.BALANCE_ID. This references the type of financial balance (e.g., Accrual, Expense) being recorded.

These relationships are essential for constructing complete ledger reports and ensuring referential integrity for all compensation journal entries.