Search Results ja_cn_sub_acc_mapping

Overview

The JA_CN_SUB_ACC_MAPPING table is a validation table owned by the JA schema within the Oracle E-Business Suite Asia/Pacific Localizations product family. It stores the configuration defined through the Subsidiary Account Source form, which captures the legacy settings used by the Data Export process for Chinese subsidiary accounting. In practical terms, the table functions as a mapping repository that links a chart of accounts to the subsidiary segment code and the account source and context codes that drive how subsidiary account information is exported and reconciled.

From a Data Vault modeling perspective, the mined relationship metadata classifies this object as standalone. This is a heuristic classification rather than an authoritative declaration, and it suggests the table may be modeled as a standalone reference or lookup structure rather than as a hub, link, or satellite. Because it holds configuration rather than transactional events, a reference-table treatment is the most natural fit.

The table is documented as VALID at the 12.2.2 release level and contains nine physical columns. It is notable that the table has a foreign key reference to GL_MGT_SEG_UPGRADE_H rather than to a core General Ledger table, which reflects its role in supporting segment upgrade and localization-related configuration.

Key Information Stored

The nine documented columns divide into business-key configuration attributes and standard Oracle audit columns:

• CHART_OF_ACCOUNTS_ID — Identifies the chart of accounts to which the subsidiary account mapping applies. This column carries a foreign key reference to GL_MGT_SEG_UPGRADE_H and is the primary business-key candidate for joining to ledger and accounting configuration.
• SUBSIDIARY_SEGMENT_CODE — Holds the subsidiary segment value used to identify the reporting entity within the account structure.
• SOURCES_CODE — Specifies the account source code that determines how the subsidiary account value is derived during Data Export.
• CONTEXT_CODE — Provides the context under which the source-to-account mapping is applied, allowing multiple configurations to coexist for different processing scenarios.
• CREATED_BY, CREATION_DATE — Standard audit columns recording the user and timestamp of initial row creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns capturing the most recent modification and the login session associated with it.

No explicit surrogate primary key column is documented in the available metadata; the combination of CHART_OF_ACCOUNTS_ID, SUBSIDIARY_SEGMENT_CODE, SOURCES_CODE, and CONTEXT_CODE functions as the composite business key. The audit columns follow the conventional EBS WHO column pattern maintained by database triggers or the OAF framework.

Common Use Cases and Queries

The most common scenario is auditing or reproducing the subsidiary account source configuration that existed at the time of a prior Data Export run. Because this table preserves the previous setting, it is frequently consulted when reconciling historical exports or troubleshooting changes to subsidiary segment derivation.

A typical query retrieves the full mapping for a specific chart of accounts:

• SELECT chart_of_accounts_id, subsidiary_segment_code, sources_code, context_code FROM ja.ja_cn_sub_acc_mapping WHERE chart_of_accounts_id = :coa_id;

Change-audit reporting uses the LAST_UPDATE_DATE and LAST_UPDATED_BY columns to identify who modified a mapping and when, which is valuable during localization support engagements. A further use case joins to GL_MGT_SEG_UPGRADE_H to correlate subsidiary account source settings with segment upgrade history:

• SELECT m.subsidiary_segment_code, m.sources_code, h.* FROM ja.ja_cn_sub_acc_mapping m, gl.gl_mgt_seg_upgrade_h h WHERE m.chart_of_accounts_id = h.chart_of_accounts_id;

Reporting extracts also compare SOURCES_CODE values across contexts to verify that subsidiary accounts resolve consistently before running Data Export.

Related Objects

• GL_MGT_SEG_UPGRADE_H — Referenced directly by JA_CN_SUB_ACC_MAPPING.CHART_OF_ACCOUNTS_ID; the segment upgrade history table links mapping configuration to upgrade events.
• GL_CODE_COMBINATIONS — Provides the chart of accounts and segment value context underlying CHART_OF_ACCOUNTS_ID and SUBSIDIARY_SEGMENT_CODE.
• GL_LEDGERS / GL_LEDGER_CONFIGURATIONS — Supply the ledger context associated with the chart of accounts referenced in the mapping.
• JA_CN_DATA_EXPORT (and related Data Export concurrent programs) — Consume the mapping configuration stored here when generating subsidiary account output.
• FND_FLEX_VALUES / FND_FLEX_VALUE_SETS — Define the segment values used by SUBSIDIARY_SEGMENT_CODE and validate the account source and context codes.

Because the Data Vault classification is standalone, no downstream link tables are documented as dependent on this object; referencing relationships are configuration-driven rather than referential-integrity enforced.