Search Results gl_ledger_norm_seg_vals

Overview

The JA_CN_CFSBSV_V view is a localization object owned by the APPS schema within the JA (Asia/Pacific Localizations) product family, specifically supporting the China (CN) localizations. Its status is VALID, and it is documented as a reporting and integration component of Oracle E-Business Suite 12.1.1 and 12.2.2. The view's name, combining "CF" (likely Consolidated Financial Statements), "SB" (Balance Segment), and "SV" (Segment Value), indicates its purpose: surfacing the valid balance segment values that are applicable to a given ledger for use in statutory reporting and consolidation processes mandated by Chinese regulatory requirements.

The view reconciles two distinct methods by which Oracle EBS can determine balancing segment values for a ledger. Ledgers configured with a "Specific" balancing segment option (BAL_SEG_VALUE_OPTION_CODE = 'I') inherit balance segment values through ledger relationships, while ledgers configured with an "All" option ('A') derive values directly from the balancing segment value set. The view unifies these two sources through a UNION, producing a consistent set of ledger/segment value pairs.

Underlying Base Objects

The view is defined over four documented base objects:

• GL_LEDGERS — referenced twice within the first UNION branch (aliased LG and LGR_C), supplying ledger identity and the BAL_SEG_VALUE_OPTION_CODE and COMPLETE_FLAG attributes.
• GL_LEDGER_RELATIONSHIPS — supplies the mapping between source and target ledgers, filtered to APPLICATION_ID = 101 (General Ledger).
• GL_LEDGER_NORM_SEG_VALS — the normalization table that stores the balance segment values (SEGMENT_TYPE_CODE = 'B') associated with a ledger, excluding deleted rows.
• FND_FLEX_VALUES — the standard flexfield values table, joined on the ledger's BAL_SEG_VALUE_SET_ID for the "All" option branch, restricted to non-summary values.

The relationship logic is precise: for the "I" branch, the query accepts either a direct NONE relationship or an ALC (Accounting Localization Configuration) target category with SUBLEDGER or JOURNAL relationship types, provided the source ledger matches the specified ledger.

Key Columns

• LG_ID — The ledger identifier (LEDGER_ID) from GL_LEDGERS, identifying the ledger to which the balance segment value applies.
• LE_ID — The legal entity identifier (LEGAL_ENTITY_ID) sourced from GL_LEDGER_NORM_SEG_VALS. This column is populated only in the first UNION branch and returns NULL for ledgers using the "All" balancing segment option.
• BSV — The balance segment value itself, drawn either from GL_LEDGER_NORM_SEG_VALS.SEGMENT_VALUE or from FND_FLEX_VALUES.FLEX_VALUE depending on the branch.

Common Use Cases and Queries

Because the underlying search term gl_ledger_norm_seg_vals points directly at one of the four base tables, the most frequent access pattern is resolving balance segment values for a specific ledger in China localization reporting.

SELECT lg_id, le_id, bsv
FROM   apps.ja_cn_cfsbsv_v
WHERE  lg_id = :p_ledger_id;

To correlate legal entities with their associated balance segment values:

SELECT le_id, bsv
FROM   apps.ja_cn_cfsbsv_v
WHERE  le_id IS NOT NULL
ORDER  BY le_id, bsv;

To cross-reference the normalization table directly, DBAs may join the view back to source tables when troubleshooting:

SELECT v.lg_id, v.le_id, v.bsv, n.segment_type_code, n.status_code
FROM   apps.ja_cn_cfsbsv_v v,
       apps.gl_ledger_norm_seg_vals n
WHERE  v.lg_id = n.ledger_id
AND    v.bsv   = n.segment_value;

These queries support financial statement generation, consolidation mapping, and validation of Chinese statutory filings, and should always be executed against the APPS schema or through a synonym granted appropriate privileges.