Search Results account_segment

Overview

JA_CN_CODE_COMBINATION_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, filed under the FND – Application Object Library product. Its documented status is VALID in both 12.1.1 and 12.2.2, with the view text and object metadata recorded in the ETRM repository. The view presents a localized, China-specific projection of the Oracle General Ledger accounting flexfield, redeploying the standard GL_CODE_COMBINATIONS segments under business-friendly aliases. Rather than exposing the generic SEGMENT1 through SEGMENT5 naming convention, the view maps each segment to a functional label, notably exposing SEGMENT3 as ACCOUNT_SEGMENT.

This naming convention is the principal reason the view is surfaced when users or developers search for the term "account_segment." In a standard Oracle EBS chart of accounts, the account segment is a user-defined flexfield qualifier rather than a fixed physical column, so a search on the literal string "account_segment" typically returns localized views such as this one that rename segments for reporting purposes. The view therefore functions as a semantic bridge: it allows reports, interfaces, and extracts to reference meaningful segment names while reading the same underlying accounting key.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through APPS synonyms:

• GL_CODE_COMBINATIONS — the base table storing every valid accounting flexfield combination, keyed by CODE_COMBINATION_ID and linked to a chart of accounts through CHART_OF_ACCOUNTS_ID.
• GL_LEDGERS — the ledger definition table, providing LEDGER_ID and the CHART_OF_ACCOUNTS_ID used to join each ledger to its corresponding set of code combinations.

The two tables are joined on LED.LEDGER_ID = GCC.CHART_OF_ACCOUNTS_ID as documented. This restricts the result set so that each code combination row is returned once per ledger sharing the same chart of accounts, which is the intended behavior for ledger-aware reporting. Because the join uses the chart of accounts as the common key, the view naturally reports the combinations that are valid for the ledger context in which it is queried.

Key Columns

• CODE_COMBINATION_ID — the surrogate primary key of the accounting combination, carried directly from GL_CODE_COMBINATIONS, and the standard join key to subledger and GL fact tables.
• LEDGER_ID — the ledger identifier from GL_LEDGERS, enabling ledger-scoped filtering.
• COMPANY_SEGMENT — alias for SEGMENT1, typically the balancing or company entity.
• ACCOUNT_SEGMENT — alias for SEGMENT3, the natural account segment. This is the defining column for searches on "account_segment."
• COST_SEGMENT — alias for SEGMENT2, usually the cost centre or department.
• PROJECT_NUMBER — alias for SEGMENT4, holding the project value where the chart of accounts reserves a segment for projects.
• OTHER_COLUMNS — a concatenation of SEGMENT4 and SEGMENT5 separated by a period, providing a combined project-plus-additional segment string.
• SECOND_TRACKING_COL and PROJECT_ID — placeholders returned as NULL (PROJECT_ID cast via TO_NUMBER(NULL)) to keep a stable column shape for downstream consumers.

Common Use Cases and Queries

The view is principally used for localized reporting and extract generation where segment names must be presented semantically. Typical usages include account validation, ledger-to-combination mapping, and feeds into Chinese statutory or management reporting. Because the view is a straightforward non-joined projection, it performs well for equality and range filters on the segment columns.

• Locating a natural account across ledgers: SELECT ledger_id, code_combination_id FROM apps.ja_cn_code_combination_v WHERE account_segment = '1000';
• Resolving the full segment picture for a given combination: SELECT company_segment, cost_segment, account_segment, project_number, other_columns FROM apps.ja_cn_code_combination_v WHERE code_combination_id = :ccid;
• Feeding downstream extracts with concatenated project tracking: SELECT code_combination_id, ledger_id, other_columns FROM apps.ja_cn_code_combination_v ORDER BY ledger_id, code_combination_id;

Note that ACCOUNT_SEGMENT maps to SEGMENT3 by definition, so implementations whose account qualifier is assigned to a different segment must not rely on this view for account identification. The view assumes the fixed mapping described above and is intended for charts of accounts structured accordingly.