Search Results xla_event_classes_tl

Overview

The view APPS.JA_CN_CFS_ITEM_MAPPING_HDRS_V is a reporting and integration construct within the Oracle E-Business Suite Application Object Library (FND product). It surfaces header-level configuration data for the China Country-Specific Functionality (CFS) item mapping feature, which is used to align Oracle Subledger Accounting (XLA) analytical criteria with general ledger chart of accounts structures. The view is defined as a VALID object owned by the APPS schema and is available in both 12.1.1 and 12.2.2 environments.

The primary purpose of the view is to denormalize and expose mapping header information alongside descriptive attributes drawn from several XLA dictionary tables. By joining the mapping headers to analytical criterion headers, analytical detail definitions, and application names, the view provides a single source for reporting on how an analytical criterion code selected in a China CFS mapping has been associated with an application, an AMB (accounting methods builder) context, and an analytical criterion type. This supports both inquiry screens and custom reporting against the item mapping configuration.

Underlying Base Objects

The documented base objects referenced by this view, all accessed through synonyms in the APPS schema, are:

• JA_CN_CFS_ITEM_MAPPING_HDRS — the primary mapping header table holding MAPPING_HEADER_ID, CHART_OF_ACCOUNTS_ID, APPLICATION_ID, EVENT_CLASS_CODE, ANALYTICAL_CRITERION_CODE, AMB_CONTEXT_CODE, and ANALYTICAL_CRITERION_TYPE_CODE.
• XLA_ANALYTICAL_SOURCES — used in the correlated subquery to validate that the mapping's analytical criterion code exists as a source definition for the same application, AMB context, and criterion type.
• XLA_ANALYTICAL_HDRS_TL — joined to supply the translated analytical criterion name (ANALYTICAL_CRITERION).
• XLA_ANALYTICAL_DTLS_B and XLA_ANALYTICAL_DTLS_TL — analytical detail base and translation tables, participate in the join path for the criterion definition.
• FND_APPLICATION_TL — joined on APPLICATION_ID to return the translated APPLICATION_NAME.

Notably, several columns that appear in the historical view definition — including KEY_FLEXFIELD_FLAG, FLEX_VALUE_SET_ID, SEGMENT_CODE, FLEXFIELD_APPLICATION_ID, ID_FLEX_CODE, and SOURCE_TYPE_CODE — are commented out in the documented view text. In the current implementation these attributes are not projected by the view.

Key Columns

• MAPPING_HEADER_ID — unique identifier of the mapping header record.
• CHART_OF_ACCOUNTS_ID — chart of accounts for which the mapping applies.
• APPLICATION_ID / APPLICATION_NAME — owning application and its translated name.
• EVENT_CLASS_CODE (also aliased as EVENT_CLASS) — event class associated with the mapping.
• ANALYTICAL_CRITERION_CODE / ANALYTICAL_CRITERION — criterion code and its translated description.
• AMB_CONTEXT_CODE — accounting methods builder context.
• ANALYTICAL_CRITERION_TYPE_CODE — classification of the analytical criterion.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — date-range validity of the mapping header.
• Standard audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include validating CFS item mapping configuration, auditing which analytical criteria are in scope for a given application and AMB context, and building custom inquiries for China CFS support.

List all mappings with descriptive names:

SELECT mapping_header_id, application_name,
       event_class_code, analytical_criterion,
       analytical_criterion_code, amb_context_code,
       analytical_criterion_type_code,
       effective_start_date, effective_end_date
FROM   apps.ja_cn_cfs_item_mapping_hdrs_v
WHERE  TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date;

Filter by application and criterion type:

SELECT mapping_header_id, analytical_criterion_code
FROM   apps.ja_cn_cfs_item_mapping_hdrs_v
WHERE  application_id = 200
AND    analytical_criterion_type_code = :p_type;

Because KEY_FLEXFIELD_FLAG is commented out of the view, users searching for that column should instead query the underlying XLA_SOURCES_B table directly, joining to the header table on application, AMB context, and criterion code.