Results for “intrcmp_tx_evnt_cls_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

ZX_EVNT_CLS_MAPPINGS is a core configuration table within the Oracle E-Business Tax (ZX) module. Its documented purpose is to store mappings of tax event classes to event classes of Oracle Applications. In practical terms, the table defines how a calling application's business event (such as an invoice validation event or a purchase order event) is translated into the tax event classes that E-Business Tax uses to drive tax determination, calculation, and recording. It is the authoritative bridge that aligns application-specific event semantics with the ZX tax event model.

The table resides in the ZX schema and is owned by the E-Business Tax product. In releases 12.1.1 and 12.2.2 it exists as a valid, populated configuration object with 84 documented columns in the 12.2.2 physical schema. The primary key is ZX_EVNT_CLS_MAPPINGS_PK, defined on EVENT_CLASS_MAPPING_ID. A heuristic Data Vault classification of this object is satellite-leaning: the table carries substantial descriptive and behavioral attributes, and it is referenced by multiple downstream fact-oriented tables. In a Data Vault model, this would suggest treating ZX_EVNT_CLS_MAPPINGS as a satellite attached to an event class mapping hub, with the mapping identifier acting as the hub key.

Key Information Stored

Although the table exposes 84 columns, a relatively small subset carries the functional identity and behavioral rules that make this mapping meaningful.

• EVENT_CLASS_MAPPING_ID — the surrogate primary key and the value propagated to all dependent tables.
• EVENT_CLASS_CODE and APPLICATION_ID — together with ENTITY_CODE, these form the second unique business key, ZX_EVNT_CLS_MAPPINGS_U2, identifying the calling application's event class.
• ENTITY_CODE — the application entity (for example, a transaction type grouping) to which the mapping applies.
• TAX_EVENT_CLASS_CODE — the tax event class the application event maps to; foreign keyed to ZX_EVENT_CLASSES_B.
• INTRCMP_TX_EVNT_CLS_CODE — the tax event class used for intercompany transactions, also referencing ZX_EVENT_CLASSES_B; supported by INTRCMP_SRC_ENTITY_CODE, INTRCMP_SRC_EVNT_CLS_CODE, and INTRCMP_SRC_APPLN_ID.
• DET_FACTOR_TEMPL_CODE — the determinant factor template controlling which factors drive tax determination; foreign keyed to ZX_DET_FACTOR_TEMPL_B.
• REFERENCE_APPLICATION_ID — the reference application for the mapping, foreign keyed to FND_APPLICATION.
• ALLOW_OVERRIDE_FLAG, ALLOW_MANUAL_LINES_FLAG, and ALLOW_MANUAL_LIN_RECALC_FLAG — control whether users may override tax or manually recalculate lines.
• TAX_REPORTING_FLAG and RECORD_FLAG — govern whether the mapped event is recorded for tax reporting.
• PROCESSING_PRECEDENCE — orders mapped events when multiple mappings apply.
• DEFAULT_ROUNDING_LEVEL_CODE and the ROUNDING_LEVEL_HIER_1 through _4 codes — define rounding behavior for calculated tax.
• ZD_EDITION_NAME — the editioning column used in 12.2 online patching; it participates in both unique indexes.

Standard audit columns such as CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN are also present. The first unique index, ZX_EVNT_CLS_MAPPINGS_U1, is defined on EVENT_CLASS_MAPPING_ID and ZD_EDITION_NAME; the second, ZX_EVNT_CLS_MAPPINGS_U2, is defined on EVENT_CLASS_CODE, APPLICATION_ID, ENTITY_CODE, and ZD_EDITION_NAME.

Common Use Cases and Queries

Because the table controls event translation and tax behavior, it is frequently queried during configuration review, troubleshooting, and reporting. Typical patterns include:

• Confirming which tax event class a specific application event maps to, for example by filtering on APPLICATION_ID, ENTITY_CODE, and EVENT_CLASS_CODE.
• Auditing behavioral flags such as ALLOW_OVERRIDE_FLAG or TAX_REPORTING_FLAG to determine whether users can alter calculated tax or whether the event is recorded for reporting.
• Reviewing the determinant factor template assigned to a mapping, joining DET_FACTOR_TEMPL_CODE to ZX_DET_FACTOR_TEMPL_B.
• Identifying the reference application through a join to FND_APPLICATION using REFERENCE_APPLICATION_ID.
• Examining intercompany mappings via INTRCMP_TX_EVNT_CLS_CODE and the associated INTRCMP_SRC_* columns.

A representative query retrieves the mapping and its descriptive context:

SELECT m.EVENT_CLASS_MAPPING_ID,
       m.APPLICATION_ID,
       m.ENTITY_CODE,
       m.EVENT_CLASS_CODE,
       m.TAX_EVENT_CLASS_CODE,
       m.DET_FACTOR_TEMPL_CODE,
       m.ALLOW_OVERRIDE_FLAG,
       m.TAX_REPORTING_FLAG
FROM   ZX.ZX_EVNT_CLS_MAPPINGS m
WHERE  m.APPLICATION_ID = :app_id
AND    m.ENTITY_CODE    = :entity_code;

For upgrade and reporting work, join on ZD_EDITION_NAME to scope results to the active edition when querying in a 12.2 environment.

Related Objects

ZX_EVNT_CLS_MAPPINGS participates in a broad relationship network. The most significant foreign key references held by this table are:

• ZX_EVENT_CLASSES_B — via TAX_EVENT_CLASS_CODE and INTRCMP_TX_EVNT_CLS_CODE.
• ZX_DET_FACTOR_TEMPL_B — via DET_FACTOR_TEMPL_CODE.
• FND_APPLICATION — via REFERENCE_APPLICATION_ID.

Tables that depend on this object through EVENT_CLASS_MAPPING_ID include:

• ZX_EVNT_TYP_MAPPINGS — maps event types within the mapped event class.
• ZX_LINES_DET_FACTORS — stores line-level determinant factors resolved through the mapping.
• ZX_PRODUCT_OPTIONS_ALL — holds product-level tax options tied to the mapping.
• ZX_RULES_B — the tax rule definitions applied to the mapped event class.
• ZX_REP_TRX_DETAIL_T and ZX_PTNR_NEG_LINE_GT — reporting and partner negotiation line structures referencing the mapping.

Because six tables carry EVENT_CLASS_MAPPING_ID as a foreign key, this object is a central junction in the E-Business Tax configuration model and should be treated as a critical reference when analyzing tax determination, rules, and reporting flows.