Search Results lg_id

Overview

JA_CN_CFSBSV_V is an APPS-owned database view in Oracle E-Business Suite, defined for the Oracle Financials for China (JA) localization. The name reflects its purpose: it resolves the balancing segment values (BSV) associated with a given ledger, and where applicable the corresponding legal entity, producing a compact mapping used by Chinese statutory reporting and subledger consolidation logic. In ETRM 12.2.2 the object is documented under owner APPS and is exposed to reporting and integration layers as a read-only synonym-based view. It is particularly relevant to the China Cash Flow Statement / statutory balance sheet reporting (CFSBS) where each ledger's balancing segment must be tied to a legal entity identifier.

The view is commonly interrogated with a filter on the lg_id column, which returns the ledger identifier. Users searching "lg_id" are typically joining this view back to GL_LEDGERS to enumerate reportable balancing segment values for one ledger or a set of ledgers.

Underlying Base Objects

The view is defined as a UNION of two branches over four documented base objects (all synonyms):

• GL_LEDGERS — the ledger definition table; supplies LEDGER_ID, BAL_SEG_VALUE_OPTION_CODE, and BAL_SEG_VALUE_SET_ID.
• GL_LEDGER_RELATIONSHIPS — defines relationships between primary and secondary ledgers, including relationship type and category codes.
• GL_LEDGER_NORM_SEG_VALS — normalized segment value assignments, supplying the balancing segment value and legal entity identifier.
• FND_FLEX_VALUES — the flexfield value table, supplying the balancing segment value when the accounting setup references an explicit value set.

The first branch handles ledgers where BAL_SEG_VALUE_OPTION_CODE = 'I' (balancing segment is represented by a specific identifier / relationship-driven value). It joins LEDGER relationships via APPLICATION_ID = 101 (General Ledger) and admits either the 'NONE' relationship type targeting the same ledger, or an 'ALC' (accounting ledger configuration) target category with 'SUBLEDGER' or 'JOURNAL' relationship types. It excludes segment values with STATUS_CODE 'D' and requires SEGMENT_TYPE_CODE = 'B'. The second branch handles ledgers where BAL_SEG_VALUE_OPTION_CODE = 'A' (all values from a value set), pulling non-summary values (SUMMARY_FLAG = 'N') from the ledger's balancing segment value set.

Key Columns

• LG_ID — the GL ledger identifier. This is the principal join key and the column most frequently referenced by consumers of this view.
• LE_ID — the legal entity identifier, populated only in the first branch; NULL in the second branch because value-set based ledgers do not carry a normalized legal entity assignment here.
• BSV — the balancing segment value applicable to the ledger, taken from GL_LEDGER_NORM_SEG_VALS.SEGMENT_VALUE or FND_FLEX_VALUES.FLEX_VALUE respectively.

Common Use Cases and Queries

The view is typically used to enumerate valid balancing segment values (and their legal entity linkage) per ledger for reporting, reconciliation, and validations in the China localization.

• Retrieving all balancing segment values for a specified ledger:
• SELECT lg_id, le_id, bsv FROM apps.ja_cn_cfsbsv_v WHERE lg_id = :p_ledger_id ORDER BY bsv;
• Joining to GL_LEDGERS to obtain ledger name and currency alongside each balancing segment value.
• Restricting to entries with a legal entity for statutory submissions: WHERE le_id IS NOT NULL.
• Feeding subledger/consolidation extracts that must map accounting entries to balancing segment and legal entity.

Because the view resolves both relationship-driven and value-set-driven ledgers through a UNION, consumers must account for the fact that LE_ID may be NULL and that each ledger can return multiple BSV rows.