Results for “balance_id”

50+ results




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

Overview

CN_LEDGER_JOURNAL_ENTRIES_ALL is the base table in the Oracle Incentive Compensation (CN) module that stores the individual debit and credit lines comprising incentive compensation journal entries. Each row represents a single posting line within a compensation ledger journal entry, capturing the accounting effect (debit or credit amount), the reason code, and the business context under which the entry was generated. In Oracle EBS 12.1.1 and 12.2.2, this table serves as the transactional store of compensation-related accounting distributions that feed downstream general ledger integration and compensation reconciliation reporting.

From a dimensional modeling perspective, the ETRM heuristic classifies this table as a link structure. It sits at the intersection of several reference entities — the SRP period, the journal entry batch, the ledger balance type, and the operating unit — and its primary role is to associate those dimensions with a quantified debit or credit measure. Modelers should treat it as an associative link rather than a hub or satellite.

Key Information Stored

The most significant columns can be grouped into identifiers, financial measures, and audit attributes.

Common Use Cases and Queries

Typical applications include reconciling compensation postings to the general ledger, analyzing debit and credit balances by period, and auditing adjustment activity.

A common reporting pattern aggregates debits and credits by compensation period and balance type:

SELECT j.SRP_PERIOD_ID,
       j.BALANCE_ID,
       SUM(j.DEBIT)  AS total_debit,
       SUM(j.CREDIT) AS total_credit
  FROM CN.CN_LEDGER_JOURNAL_ENTRIES_ALL j
 WHERE j.ORG_ID = :p_org_id
 GROUP BY j.SRP_PERIOD_ID, j.BALANCE_ID;

To trace all lines belonging to a specific journal batch, developers join to the batch header on BATCH_ID, and to resolve the period name they join CN_SRP_PERIODS_ALL on SRP_PERIOD_ID. Because ORG_ID drives Multi-Org access, queries should always restrict on the operating unit to avoid cross-entity data leakage. Feeder queries for GL interface programs typically filter rows by JE_DATE range and batch status.

Related Objects

  • CN_LEDGER_JE_BATCHES_ALL — Parent batch table; join on CN_LEDGER_JOURNAL_ENTRIES_ALL.BATCH_ID = CN_LEDGER_JE_BATCHES_ALL.BATCH_ID.
  • CN_SRP_PERIODS_ALL — Compensation period definition; join on SRP_PERIOD_ID.
  • CN_LEDGER_BAL_TYPES_ALL_B — Balance type reference; join on BALANCE_ID.
  • FND_SECURITY_GROUPS — Secures row visibility; join on SECURITY_GROUP_ID.
  • CN_LEDGER_JOURNAL_ENTRIES_PK — Primary key constraint enforcing LEDGER_JE_ID uniqueness.

These relationships define the core access path for both concurrent-program integration and ad hoc compensation reporting.