Search Results dpp_xla_event_map_u1

Overview

DPP.DPP_XLA_EVENT_MAP is a reference (seed) table owned by the DPP schema in Oracle E-Business Suite, residing in the APPS_TS_SEED tablespace. Its documented purpose is to serve as a lookup table consumed during the regular Price Protection Subledger Accounting (SLA) process. When Price Protection transactions are processed, the SLA engine must determine which XLA (Subledger Accounting) event class and event type should be generated for a given business transaction. This table provides that mapping, translating a Price Protection transaction type into the corresponding SLA entity, event class, and event type codes.

Because the table holds relatively static configuration data rather than transactional activity, the ETRM metadata classifies it heuristically as a standalone object within a Data Vault modeling suggestion. In practical terms, it behaves as a reference or lookup dimension: it does not reference any other database object via foreign key, and it is independently maintained as seed data. The table carries the standard WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and, in the 12.2.2 documented schema, an additional ZD_EDITION_NAME column associated with edition-based redefinition support.

Key Information Stored

The table is compact, containing ten documented columns. The most significant are:

• PP_TRANSACTION_TYPE (VARCHAR2(30), mandatory) — The business transaction type for which mapping is required. Documented possible values include COST_UPDATE, SUPP_DSTR_CL, SUPP_CUST_CL, and CUST_CL. This column is the physical primary key of DPP_XLA_EVENT_MAP_PK.
• ENTITY_CODE (VARCHAR2(30)) — The Subledger Accounting entity code that the transaction maps to.
• EVENT_CLASS_CODE (VARCHAR2(30)) — The SLA event class to be generated.
• EVENT_TYPE_CODE (VARCHAR2(40)) — The specific SLA event type to be generated for the transaction.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns recording insert and update metadata for each mapping row.
• ZD_EDITION_NAME — Edition-based redefinition discriminator present in the 12.2.2 physical schema.

The unique index DPP_XLA_EVENT_MAP_U1 enforces uniqueness across (PP_TRANSACTION_TYPE, ZD_EDITION_NAME), which acts as the business-key candidate. The surrogate primary key DPP_XLA_EVENT_MAP_PK is defined on PP_TRANSACTION_TYPE alone in the documented ETRM view.

Common Use Cases and Queries

Typical use cases center on troubleshooting and validating Price Protection SLA accounting. Practitioners query this table to confirm that a given transaction type resolves to the expected entity, event class, and event type before the accounting engine creates XLA events. A common diagnostic query retrieves the full mapping for one or all transaction types:

• Listing all mappings: SELECT PP_TRANSACTION_TYPE, ENTITY_CODE, EVENT_CLASS_CODE, EVENT_TYPE_CODE FROM DPP.DPP_XLA_EVENT_MAP ORDER BY PP_TRANSACTION_TYPE;
• Resolving a single transaction type: SELECT ENTITY_CODE, EVENT_CLASS_CODE, EVENT_TYPE_CODE FROM DPP.DPP_XLA_EVENT_MAP WHERE PP_TRANSACTION_TYPE = :p_type;

Reporting scenarios include auditing seed data after upgrades or patches to verify that Price Protection event mappings remain intact, and comparing the mapped EVENT_CLASS_CODE/EVENT_TYPE_CODE against runtime SLA event data to detect gaps. Because the table is seed data, changes should normally be introduced by Oracle-provided seed scripts rather than ad-hoc DML.

Related Objects

The documented dependencies indicate that DPP.DPP_XLA_EVENT_MAP does not reference any database object through foreign keys, confirming its standalone reference role. It is referenced by the APPS synonym DPP_XLA_EVENT_MAP, which allows application code running in the APPS schema to query the table without schema qualification. The principal consumers are the Price Protection SLA accounting programs that read the mapping to derive XLA entity, event class, and event type values for COST_UPDATE, SUPP_DSTR_CL, SUPP_CUST_CL, and CUST_CL transactions. Related functional objects include the XLA event and accounting tables (such as the XLA_EVENTS and XLA_AE_HEADERS families) that receive the generated events, and the Price Protection transaction tables that supply PP_TRANSACTION_TYPE values at runtime. Administrators validating the configuration should join this table with runtime XLA event data on ENTITY_CODE, EVENT_CLASS_CODE, and EVENT_TYPE_CODE.