Search Results cost_segment

Overview

APPS.JA_CN_CODE_COMBINATION_V is a reporting and integration view in Oracle E-Business Suite, documented in the ETRM repository for releases 12.1.1 and 12.2.2. It presents a localized, denormalized projection of accounting flexfield combinations intended for the China (JA_CN) localization layer of Oracle Financials. The view joins the global accounting flexfield definition to the ledger definition, exposing the segment values of a chart of accounts in a form aligned to Chinese statutory reporting requirements.

The view is owned by the APPS schema and is defined as a simple two-table join without aggregation, filtering, or unions. It therefore behaves as a lightweight, low-cost query source for concurrent programs, XML Publisher reports, and inbound/outbound interface logic that must map EBS accounting flexfield segments to Chinese reporting attributes such as company code, account code, cost center, project number, and secondary tracking information.

Underlying Base Objects

The ETRM metadata lists two referenced base objects, both exposed as SYNONYMs within the APPS schema:

• GL_CODE_COMBINATIONS — the base table storing each valid accounting flexfield combination, including CODE_COMBINATION_ID, CHART_OF_ACCOUNTS_ID, and the SEGMENT1 through SEGMENTn columns.
• GL_LEDGERS — the ledger definition table, supplying LEDGER_ID and its associated CHART_OF_ACCOUNTS_ID.

The join condition is LED.CHART_OF_ACCOUNTS_ID = GCC.CHART_OF_ACCOUNTS_ID. Because this is an equi-join on chart of accounts rather than on ledger, a single code combination is returned once for every ledger sharing the same chart of accounts. Consumers must therefore constrain by LEDGER_ID when querying in a multi-ledger environment to avoid row multiplication.

Key Columns

• CODE_COMBINATION_ID — primary key of the accounting flexfield combination; the natural join key back to GL_CODE_COMBINATIONS and to subledger distribution tables.
• LEDGER_ID — identifier of the ledger whose chart of accounts matches the combination.
• COMPANY_SEGMENT — alias for SEGMENT1, representing the company or entity code.
• ACCOUNT_SEGMENT — alias for SEGMENT3, representing the natural account.
• COST_SEGMENT — alias for SEGMENT2, representing the cost center or department.
• PROJECT_NUMBER — alias for SEGMENT4, carrying the project identifier used in Chinese statutory and project accounting.
• SECOND_TRACKING_COL — defined as a literal NULL placeholder, reserved for secondary tracking configuration but not populated by this view.
• OTHER_COLUMNS — a derived concatenation of SEGMENT4 and SEGMENT5 separated by a period (SEGMENT4||'.'||SEGMENT5). This is the column most commonly referenced when users search for "other_columns," and it serves as a composite key for multi-part tracking segments.
• PROJECT_ID — defined as TO_NUMBER(NULL), an unpopulated numeric placeholder for project identification.

Common Use Cases and Queries

Typical scenarios include mapping code combinations into Chinese localization reports, validating that a combination belongs to a given ledger's chart of accounts, and extracting the composite tracking string for reconciliation with statutory filings. A representative query is:

• SELECT code_combination_id, ledger_id, company_segment, account_segment, cost_segment, project_number, other_columns FROM apps.ja_cn_code_combination_v WHERE ledger_id = :p_ledger_id;
• SELECT code_combination_id, other_columns FROM apps.ja_cn_code_combination_v WHERE company_segment = :p_company AND account_segment = :p_account;
• SELECT v.code_combination_id, v.other_columns, g.segment5 FROM apps.ja_cn_code_combination_v v, gl_code_combinations g WHERE v.code_combination_id = g.code_combination_id;

Because SECOND_TRACKING_COL and PROJECT_ID are NULL placeholders, reports requiring those attributes must source them from other localization views or tables. All queries should filter on LEDGER_ID to respect the chart-of-accounts join semantics described above.