Search Results dpp_execution_processes_u1

Overview

DPP.DPP_EXECUTION_PROCESSES is a seed-level configuration table in the Oracle E-Business Suite DPP (Distributed Process Planning) schema. Its documented purpose is to store the list of all DPP processes that have been associated with a Payroll Process (PP) transaction header. Each row represents a single process-to-transaction association, identified by a process code bound to a specific transaction header identifier. The table resides in the APPS_TS_SEED tablespace, indicating that its contents are treated as setup or reference data that is seeded or maintained across environments rather than transactional volume data.

From a heuristic Data Vault modeling perspective, the metadata classifies this object as standalone. Because the documented schema exposes composite key columns rather than foreign keys to other tables, it can be modeled as a hub-like structure keyed on the process/transaction combination, with the WHO audit columns belonging to a conventional satellite treatment. This is a modeling suggestion only; the physical implementation is a standard EBS relational table with a single unique index.

Key Information Stored

The table contains seven documented columns. The two most significant are the business key columns that form the composite primary key and the unique index DPP_EXECUTION_PROCESSES_U1:

• PROCESS_CODE (VARCHAR2, 30) — Identifier for the DPP process. Mandatory in the key structure.
• TRANSACTION_HEADER_ID (NUMBER) — Unique identifier for the PP Transaction. Serves as the surrogate transaction reference within the DPP schema.
• CREATION_DATE (DATE) — Standard WHO column recording row creation.
• CREATED_BY (NUMBER) — Standard WHO column identifying the creating user.
• LAST_UPDATE_DATE (DATE) — Standard WHO column recording the most recent modification.
• LAST_UPDATED_BY (NUMBER) — Standard WHO column identifying the user who last updated the row.
• LAST_UPDATE_LOGIN (NUMBER, 15) — Standard WHO column capturing the login context of the last update.

The composite primary key is DPP_EXECUTION_PROCESSES (TRANSACTION_HEADER_ID, PROCESS_CODE). The single unique index, DPP_EXECUTION_PROCESSES_U1, is a NORMAL UNIQUE index in APPS_TS_SEED over the same two columns, confirming that no duplicate process may be registered against the same transaction header. The absence of any other documented indexes suggests the access path is driven exclusively by the composite key.

Common Use Cases and Queries

Typical scenarios include validating which DPP processes are attached to a given PP transaction, reconciling seeded process definitions across instances, and auditing the WHO columns to determine when a process mapping was introduced or changed.

The documented query pattern returns the full column set:

• Retrieve all processes for a transaction: SELECT PROCESS_CODE, TRANSACTION_HEADER_ID FROM DPP.DPP_EXECUTION_PROCESSES WHERE TRANSACTION_HEADER_ID = :transaction_header_id;
• Check a specific mapping: SELECT COUNT(*) FROM DPP.DPP_EXECUTION_PROCESSES WHERE TRANSACTION_HEADER_ID = :id AND PROCESS_CODE = :code;
• Audit recent additions: filter on CREATION_DATE or LAST_UPDATE_DATE to identify newly seeded process mappings.

Because the table is seed data with a narrow unique index, reporting is normally limited to lookup joins against transaction-level tables using TRANSACTION_HEADER_ID.

Related Objects

The ETRM metadata records that DPP.DPP_EXECUTION_PROCESSES does not reference any database object, and that it is referenced by the APPS synonym DPP_EXECUTION_PROCESSES. Practically, the DPP_EXECUTION_PROCESSES_U1 unique index enforces the business key at the database level. The APPS synonym exposes the table to application and reporting sessions that connect as the APPS schema, and the TRANSACTION_HEADER_ID column is the principal join column to PP transaction header data. No foreign-key relationships are documented, so join behavior must be inferred from the shared transaction header identifier rather than enforced referential integrity.