Search Results cn_ledger_bal_types_all_b




Overview
Explore in AI Chat

Overview

The CN_LEDGER_BAL_TYPES_ALL_B table is a core lookup table within the Oracle E-Business Suite Incentive Compensation (CN) module. It serves as the master repository for defining and managing the distinct types of ledger balances used in the compensation calculation and accounting processes. Its primary role is to provide a validated list of account names, ensuring data integrity and consistency across financial postings generated by the Incentive Compensation engine. As a multi-organization table (indicated by the "_ALL_B" suffix and the ORG_ID column), it supports the definition of balance types that can be specific to individual operating units, enabling flexible and secure implementations across complex enterprise structures in both releases 12.1.1 and 12.2.2.

Key Information Stored

The table's structure centers on uniquely identifying each valid balance type within a given organizational context. The primary key is a composite of the BALANCE_ID and ORG_ID columns, which together enforce uniqueness. While the provided metadata specifies the table's purpose and key structure, typical columns in such a lookup table would include BALANCE_ID (the unique identifier for the balance type), ORG_ID (the operating unit identifier), a code or name column for the balance type (e.g., BALANCE_NAME or BALANCE_CODE), and descriptive columns like DESCRIPTION. The table acts as a reference point, storing the canonical definitions that other transactional tables must adhere to when recording financial data.

Common Use Cases and Queries

This table is fundamental for any process involving the generation or inquiry of incentive-related journal entries. Common use cases include validating balance types during journal entry creation, building reports that categorize financial activity by balance type, and administering the list of available accounts for a specific operating unit. A typical query would join this table to transactional data to retrieve meaningful balance names. For example:

  • Retrieving all defined balance types for a specific organization: SELECT balance_id, balance_name FROM cn_ledger_bal_types_all_b WHERE org_id = :p_org_id ORDER BY balance_name;
  • Joining to journal entries to report detailed postings: SELECT j.entered_amount, b.balance_name FROM cn_ledger_journal_entries_all j, cn_ledger_bal_types_all_b b WHERE j.balance_id = b.balance_id AND j.org_id = b.org_id;

Related Objects

The CN_LEDGER_BAL_TYPES_ALL_B table has a direct, documented relationship with the CN_LEDGER_JOURNAL_ENTRIES_ALL table, which holds the actual journal entry transactions. The relationship is enforced by a foreign key constraint where the BALANCE_ID and ORG_ID columns in CN_LEDGER_JOURNAL_ENTRIES_ALL reference the primary key columns (BALANCE_ID, ORG_ID) in CN_LEDGER_BAL_TYPES_ALL_B. This ensures that every journal entry is associated with a valid, pre-defined balance type from the lookup table. The primary key constraint CN_LEDGER_BAL_TYPES_ALL_B_PK maintains the integrity of the lookup data itself.