Search Results ad_te_level_history




Overview
Explore in AI Chat

Overview

AD_TE_LEVEL_HISTORY is a table owned by the APPLSYS schema in Oracle E-Business Suite (12.1.1 and 12.2.2), belonging to the AD - Applications DBA product. Its purpose is to store historical information about trackable entity codelevels. Specifically, whenever a row in AD_TRACKABLE_ENTITIES is updated, the pre-update version of that row is copied into AD_TE_LEVEL_HISTORY before the change is applied, providing an audit trail of codelevel evolution.

Under a heuristic Data Vault classification, this object is best modeled as a satellite. It captures descriptive, time-variant attributes (name, codelevel, baseline) that describe an entity tracked elsewhere, recording change history rather than defining a standalone hub or a many-to-many link.

Key Information Stored

The documented physical schema contains five columns: ABBREVIATION, NAME, CODELEVEL, BASELINE, and PATCH_RUN_ID.

  • ABBREVIATION — the short identifier of the trackable entity; part of the composite primary key (AD_TE_LEVEL_HISTORY_U1).
  • CODELEVEL — the codelevel value of the entity at the point of history capture; the second component of the composite primary key.
  • NAME — the descriptive name of the trackable entity.
  • BASELINE — the baseline indicator associated with the entity record.
  • PATCH_RUN_ID — the foreign key referencing AD_PATCH_RUNS, linking this history record to the patch run that drove the update.

The composite primary key AD_TE_LEVEL_HISTORY_U1 (ABBREVIATION, CODELEVEL) forms the business key; no separate surrogate column is defined in the documented schema.

Common Use Cases and Queries

Primary uses include auditing codelevel changes, reconciling patch activity with trackable entity states, and reporting on the historical baseline of a given entity. A typical query retrieving the change history for one entity follows the pattern below:

  • SELECT abbreviation, codelevel, name, baseline, patch_run_id FROM applsys.ad_te_level_history WHERE abbreviation = :abbrev ORDER BY patch_run_id;
  • Joining to AD_PATCH_RUNS on PATCH_RUN_ID to correlate each history row with the originating patch run.
  • Comparing the current AD_TRACKABLE_ENTITIES row against its historical rows to detect drift or unexpected codelevel regression.
  • Fed into patch impact and migration audits to confirm which patch introduced a specific codelevel.

Related Objects

  • AD_TRACKABLE_ENTITIES — the source table whose updates populate this history table.
  • AD_PATCH_RUNS — referenced via the foreign key AD_TE_LEVEL_HISTORY.PATCH_RUN_ID; provides patching context.
  • AD_PATCH_DRIVER — associated with patch execution tracking.
  • AD_PATCH_RUN_BUGS — companion patching history object enabling per-bug analysis.
  • AD_TE_LEVEL_HISTORY primary key index AD_TE_LEVEL_HISTORY_U1 — supports lookups by ABBREVIATION and CODELEVEL.