Search Results cn_ledger_je_batches_all




Overview
Explore in AI Chat

Overview

The CN_LEDGER_JE_BATCHES_ALL table is a core data object within the Oracle E-Business Suite (EBS) Incentive Compensation (CN) module. It serves as the master repository for batches of journal entries generated by the system. These journal entry batches are a critical component of the financial integration process, where compensation-related transactions, such as calculated commissions and adjustments, are prepared for posting to the Oracle General Ledger. The table's role is to group individual journal entries for efficient processing, control, and audit, ensuring that compensation expenses are accurately reflected in the enterprise's financial records. Its "ALL" suffix indicates it is a multi-organization table capable of storing data for multiple operating units.

Key Information Stored

While the provided metadata does not list specific columns, the primary key and foreign key relationships define its essential structure. The central column is BATCH_ID, which uniquely identifies each journal entry batch. Typical attributes for such a batch table in EBS would include control information such as the batch name, description, creation date, status (e.g., 'New', 'Posted', 'In Error'), the associated ledger or set of books, and identifiers for the request that created it. The table likely contains audit columns like CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE, which are standard in EBS.

Common Use Cases and Queries

This table is primarily accessed for troubleshooting, reconciliation, and reporting on the financial integration between Incentive Compensation and General Ledger. A common scenario involves identifying batches that failed to transfer to GL or tracing the source of posted journal entries back to a specific compensation calculation run. A typical query would join to related tables to get batch details and the status of its constituent entries:

  • Batch Status Inquiry: SELECT batch_id, name, status, creation_date FROM cn_ledger_je_batches_all WHERE status = 'ERROR';
  • Reconciliation with Payruns: SELECT pr.payrun_id, b.batch_id, b.status FROM cn_payruns_all pr JOIN cn_ledger_je_batches_all b ON pr.batch_id = b.batch_id WHERE pr.payrun_date = TRUNC(SYSDATE);

Related Objects

The CN_LEDGER_JE_BATCHES_ALL table has documented foreign key relationships with two key tables in the CN schema, forming the backbone of the journal entry creation flow.

  • CN_LEDGER_JOURNAL_ENTRIES_ALL: This table stores the individual journal entry lines. It references CN_LEDGER_JE_BATCHES_ALL via its BATCH_ID column (CN_LEDGER_JOURNAL_ENTRIES_ALL.BATCH_ID). A single batch can contain many journal entries.
  • CN_PAYRUNS_ALL: This table stores compensation calculation runs. It references CN_LEDGER_JE_BATCHES_ALL via its BATCH_ID column (CN_PAYRUNS_ALL.BATCH_ID), linking a specific payrun to the journal entry batch it generated.

The primary key constraint CN_LEDGER_JE_BATCHES_PK on the BATCH_ID column enforces the integrity of these relationships.