Search Results hxc_seeddata_by_level




Overview
Explore in AI Chat

Overview

HXC_SEEDDATA_BY_LEVEL is a seed data configuration table owned by the HXC schema, the repository for the Oracle Time and Labor Engine. It records which seed data objects are essential at each level of the application architecture, allowing the Time and Labor Engine and related modules to distinguish between mandatory and optional seed data across registered applications. The table belongs to the HXC - Time and Labor Engine product family and carries a VALID status in both Oracle EBS 12.1.1 and 12.2.2.

From a heuristic Data Vault modeling perspective, the mined FK structure classifies HXC_SEEDDATA_BY_LEVEL as a standalone object, which suggests it behaves as a hub or reference table rather than a link or satellite. It anchors seed data identity through a composite key and does not appear to depend on parent entities through enforced foreign keys, reinforcing its role as an independent reference point for configuration metadata.

Key Information Stored

The table contains ten documented columns. The most significant are:

  • OBJECT_ID — the numeric identifier of the seed data object being classified; part of the composite primary key.
  • OBJECT_TYPE — a discriminator indicating the category of the seed data object; the second component of the composite primary key.
  • HXC_REQUIRED — a flag indicating whether the referenced seed data is required at the given level, driving validation and setup completeness checks.
  • OWNER_APPLICATION_ID — the application that owns the seed data record, enabling multi-application scoping.
  • ZD_EDITION_NAME — the edition identifier supporting Oracle's edition-based redefinition (EBR), critical in 12.2.x multitenant and online patching scenarios.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO columns providing audit lineage.

The surrogate/business key is defined by HXC_SEEDDATA_BY_LEVEL_PK on (OBJECT_ID, OBJECT_TYPE). In the 12.2.2 physical schema, the unique index extends this to (OBJECT_ID, OBJECT_TYPE, ZD_EDITION_NAME), reflecting edition-awareness requirements introduced with EBR.

Common Use Cases and Queries

Typical usage centers on verifying seed data configuration before or after patching, and on reporting which objects demand attention. A simple query to find required seed data for an application:

  • SELECT OBJECT_ID, OBJECT_TYPE, OWNER_APPLICATION_ID FROM HXC_SEEDDATA_BY_LEVEL WHERE HXC_REQUIRED = 'Y'
  • Joining to FND_APPLICATION to resolve OWNER_APPLICATION_ID into an application short name is common in reporting.
  • Filtering on ZD_EDITION_NAME is required in 12.2.x to isolate the active edition when running diagnostic or comparison reports.
  • Comparing required versus optional seed data supports upgrade readiness assessments and setup validation scripts.

Related Objects

While the mined relationship data classifies the table as standalone, its columns reference the broader HXC and FND ecosystem:

  • FND_APPLICATION — joined via OWNER_APPLICATION_ID to resolve application names.
  • HXC_SEEDDATA — conceptually related through OBJECT_ID and OBJECT_TYPE for seed data lookups.
  • FND_SEED_DATA — the FND-level seed data repository frequently cross-referenced during diagnostics.
  • HXC_TIME_ATTRIBUTE / HXC_TEMPLATE — Time and Labor configuration tables that depend on seed data levels.
  • FND_ZD_EDITION — resolves ZD_EDITION_NAME to edition metadata in 12.2.x.
  • HXC_SEEDDATA_BY_LEVEL_PK — the primary key constraint enforcing uniqueness.