Search Results dpp_xla_event_map




Overview
Explore in AI Chat

Overview

The DPP_XLA_EVENT_MAP table resides in the DPP schema and belongs to the Oracle Price Protection (DPP) product within Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as a configuration lookup table consumed by the Price Protection Subledger Accounting (SLA) process. During routine accounting generation, the Price Protection engine queries this table to resolve which Subledger Accounting event class and event type must be created for two distinct business activities: cost update transactions and claim settlement transactions.

Because the table maps a transaction type to its corresponding accounting event definitions rather than storing transactional balances or journal entries, it acts as reference data that drives the integration between the Price Protection module and the XLA (Subledger Accounting) engine. From a Data Vault modeling perspective, the heuristic classification of this object is standalone, with no mined foreign key relationships to other tables. A modeler could reasonably treat it as a small reference or lookup hub keyed on the transaction type, though no parent or child links are documented.

Key Information Stored

The table contains ten documented columns. The most significant ones relate to the mapping itself:

  • PP_TRANSACTION_TYPE — The business discriminator identifying the Price Protection transaction being processed (for example, cost update versus claim settlement). It is the sole component of the primary key DPP_XLA_EVENT_MAP_PK and the leading column of the unique index DPP_XLA_EVENT_MAP_U1.
  • ENTITY_CODE — The Subledger Accounting entity code that scopes the accounting event to the correct application entity.
  • EVENT_CLASS_CODE — The XLA event class into which generated accounting events are categorized.
  • EVENT_TYPE_CODE — The specific XLA event type created for the given transaction type and entity combination.
  • ZD_EDITION_NAME — The editioning column used by Oracle's online patching architecture in 12.2.x. It participates in the unique index DPP_XLA_EVENT_MAP_U1 alongside PP_TRANSACTION_TYPE.

The remaining columns are standard audit and concurrency attributes: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. The surrogate primary key DPP_XLA_EVENT_MAP_PK is defined on PP_TRANSACTION_TYPE, while the business-key candidate is the composite (PP_TRANSACTION_TYPE, ZD_EDITION_NAME) enforced by DPP_XLA_EVENT_MAP_U1 — a combination that guarantees a single active mapping record per transaction type in each edition.

Common Use Cases and Queries

Implementation and support teams consult this table when diagnosing why a Price Protection cost update or claim settlement did not create the expected Subledger Accounting entries. A typical diagnostic query resolves the event class and type for a given transaction:

SELECT pp_transaction_type, entity_code,
       event_class_code, event_type_code
FROM   dpp.dpp_xla_event_map
WHERE  pp_transaction_type = :p_txn_type;

Reporting use cases include auditing the completeness of SLA configuration prior to go-live, verifying that every Price Protection transaction type has a corresponding mapping, and comparing mappings across environments. Because the table is small and static in nature, it is also useful as a reference join when reconciling XLA events back to their originating Price Protection transactions:

SELECT e.event_id, m.event_class_code, m.event_type_code
FROM   xla_events e, dpp.dpp_xla_event_map m
WHERE  e.event_type_code = m.event_type_code;

Related Objects

The documented metadata classifies DPP_XLA_EVENT_MAP as standalone, so no foreign keys are mined. Functionally, however, it interacts with the following objects through its mapping values:

  • XLA_EVENTS — joined on EVENT_TYPE_CODE and EVENT_CLASS_CODE to locate generated accounting events.
  • XLA_EVENT_TYPES / XLA_EVENT_CLASSES — the XLA definition tables whose codes are referenced by EVENT_TYPE_CODE and EVENT_CLASS_CODE.
  • XLA_ENTITY_MAP — relates ENTITY_CODE to the Subledger Accounting entity configuration.
  • DPP primary transaction tables — the Price Protection cost update and claim settlement entities whose PP_TRANSACTION_TYPE values key this lookup.
  • XLA_AE_HEADERS / XLA_AE_LINES — the accounting entry tables downstream of events generated using this mapping.

Together these objects form the chain from Price Protection transaction through event generation to final subledger journal entries.