Search Results zx_evnt_typ_mappings




Overview
Explore in AI Chat

Overview

The ZX_EVNT_TYP_MAPPINGS table is a core repository within the Oracle E-Business Tax (E-Business Tax) module of Oracle E-Business Suite (EBS) releases 12.1.1 and 12.2.2. It functions as the definitive mapping layer between transactional business events occurring in subledger applications (like Order Management, Payables, Receivables) and the standardized tax event types required for accurate tax determination and calculation. This table contains seeded, or pre-defined, data only, meaning it is populated and maintained by Oracle. Its primary role is to ensure that when a business document (e.g., an invoice line) is processed, the E-Business Tax engine can correctly identify the corresponding tax event type (e.g., 'STANDARD', 'EXEMPT') based on the application's internal event type code, entity, and class.

Key Information Stored

The table's structure is defined by a composite primary key and several critical foreign keys that enforce data integrity within the tax engine. The primary key uniquely identifies a mapping record and consists of APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, and EVENT_TYPE_CODE. These columns collectively identify the source transaction from the originating Oracle EBS application. The table then maps this source to the standardized tax event framework via the TAX_EVENT_CLASS_CODE and TAX_EVENT_TYPE_CODE columns. A crucial linking column is EVENT_CLASS_MAPPING_ID, which references the ZX_EVNT_CLS_MAPPINGS table, ensuring the event type mapping is valid only for an already-mapped event class. This design creates a hierarchical mapping: event class to tax event class, then event type to tax event type.

Common Use Cases and Queries

The primary use case is during real-time tax calculation, where the E-Business Tax engine queries this table to resolve the correct tax event type for a given transaction line. It is also critical for troubleshooting tax determination issues, reporting on tax event mappings, and understanding the tax implications of different business processes. A common diagnostic query would join this table to its parent and child tables to trace the mapping for a specific application event.

  • Sample Query to View Mappings for an Application:
    SELECT a.application_id, a.entity_code, a.event_class_code, a.event_type_code,
    a.tax_event_class_code, a.tax_event_type_code, b.application_name
    FROM zx_evnt_typ_mappings a, fnd_application b
    WHERE a.application_id = b.application_id
    AND a.entity_code = 'AP_INVOICES'
    ORDER BY 1,2,3,4;
  • Use Case: Identifying why a particular transaction line is being treated with a specific tax event type, such as 'EXEMPT', by verifying the seeded mapping from the source module's event type.

Related Objects

ZX_EVNT_TYP_MAPPINGS is centrally connected within the E-Business Tax schema, acting as a reference point for both higher-level mapping definitions and lower-level transactional tax records.

  • Parent/Referenced Tables (Foreign Key Constraints):
    • ZX_EVNT_CLS_MAPPINGS: Linked via EVENT_CLASS_MAPPING_ID. This is the immediate parent, providing the event class mapping context.
    • ZX_EVNT_CLS_TYPS: Linked via TAX_EVENT_CLASS_CODE and TAX_EVENT_TYPE_CODE. This validates the mapped tax event codes.
  • Child/Referencing Tables (Foreign Key Constraints):
    • ZX_LINES: The main tax lines table references this mapping via (APPLICATION_ID, ENTITY_CODE, EVENT_CLASS_CODE, EVENT_TYPE_CODE) to record the tax event for each calculated line.
    • ZX_LINES_DET_FACTORS: References the same composite key to store detailed tax determinants associated with a specific event type mapping.
    • ZX_REC_NREC_DIST: References the mapping to associate recoverable/non-recoverable tax distributions with the correct transactional event.