Results for “ledger_category_code”

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

Overview

JA_CN_LEDGER_LE_BSV_GT is a global temporary table (GTT) owned by the JA schema within the Asia/Pacific Localizations product family of Oracle E-Business Suite. Its defined purpose is to hold, at runtime, the balance segment values that apply to the current legal entity and ledger combination, restricted to those segment values assigned both to the active legal entity and to the ledger with respect to the accounting setup. The table functions as an in-session staging or scratch structure rather than a persistent accounting store: rows are populated by the localization program during execution and are scoped to the session or transaction that created them, consistent with standard Oracle GTT behavior (ON COMMIT DELETE ROWS or ON COMMIT PRESERVE ROWS semantics as defined by the object's DDL).

Because the object is populated transiently, it carries no durable transactional history and is not a candidate for archival or reconciliation. From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone. That classification reflects the absence of incoming foreign-key dependencies: no other table references this GTT, and the two documented outbound relationships are informational lookups rather than a hub-and-link topology. This is expected for a runtime work table, and the classification should be treated as a modeling suggestion rather than a claim that the table participates in a warehouse-style integration layer.

Key Information Stored

The documented schema comprises nine columns, which together describe a ledger-aware, legal-entity-aware set of balance segment values:

• LEDGER_ID — identifies the ledger for which the segment values were resolved; the primary filter for runtime population.
• LEDGER_CATEGORY_CODE — the ledger category (for example, primary or secondary), used to disambiguate ledgers sharing a chart of accounts.
• CHART_OF_ACCOUNTS_ID — the chart of accounts in scope; foreign-key relationship documented to GL_MGT_SEG_UPGRADE_H.
• LEGAL_ENTITY_ID — the legal entity owning the accounting setup; foreign-key relationship documented to FV_LEGAL_ENTITIES.
• BAL_SEG_VALUE_SET_ID — the value set that governs the balance segment.
• BAL_SEG_VALUE — the individual balance segment value returned for the combination.
• BAL_SEG_VALUE_OPTION_CODE — indicates how the balance segment value was determined or which option applies.
• START_DATE and END_DATE — the effective date range during which the segment value assignment is valid.

The metadata does not document a surrogate primary key or a unique index on this object, which is typical of a GTT populated in bulk. In practice, the business key is the composite of LEDGER_ID, CHART_OF_ACCOUNTS_ID, LEGAL_ENTITY_ID, BAL_SEG_VALUE_SET_ID, and BAL_SEG_VALUE, qualified by the effective dates.

Common Use Cases and Queries

The principal use case is supplying the China localization accounting programs with the correct balance segment values when generating or validating ledger and legal entity accounting combinations. Typical SQL patterns join the GTT back to the ledger and legal entity definitions to resolve descriptions or to filter reporting output:

• Listing segment values for a ledger: SELECT BAL_SEG_VALUE FROM JA_CN_LEDGER_LE_BSV_GT WHERE LEDGER_ID = :ledger_id AND LEGAL_ENTITY_ID = :le_id;
• Resolving legal entity descriptions: join LEGAL_ENTITY_ID to FV_LEGAL_ENTITIES.
• Effective-date filtering: constrain SYSDATE BETWEEN START_DATE AND END_DATE to return only currently active assignments.
• Diagnostics: inspecting GTT contents during a concurrent program run to confirm which values were staged for the session.

Related Objects

• FV_LEGAL_ENTITIES — joined via LEGAL_ENTITY_ID to resolve legal entity attributes.
• GL_MGT_SEG_UPGRADE_H — joined via CHART_OF_ACCOUNTS_ID for chart of accounts history context.
• GL_LEDGERS — supplies ledger name and category for LEDGER_ID and LEDGER_CATEGORY_CODE.
• FND_FLEX_VALUE_SETS and FND_FLEX_VALUES — define and describe BAL_SEG_VALUE_SET_ID and BAL_SEG_VALUE.
• GL_LEDGER_LE_BSV_ASSIGNMENTS (and equivalent JA localization setup tables) — the persistent source from which runtime values are derived.