Search Results jty_dea_values_idx_header_n3




Overview

JTF.JTY_DEA_VALUES_IDX_HEADER is a transactional table in the Oracle E-Business Suite Applications Technology (JTF) schema. It stores index definitions that support date effectivity assignment (DEA) processing. In practical terms, the table records which database or logical index should be associated with a given source record, relation product, and qualification usage combination, and it tracks whether that index requires building. The table resides in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10, reflecting a write-intensive transactional profile typical of concurrent DEA index maintenance.

Under the heuristic Data Vault classification derived from the foreign-key structure, this table is best modeled as a standalone hub-like entity. It does not act as a pure link between two business entities, and it carries its own descriptive attributes (the index name and build flags) that would behave as satellite content in a Data Vault design. The classification is offered as a modeling suggestion rather than a documented property.

Key Information Stored

The table contains 14 documented columns. The surrogate primary key is DEA_VALUES_IDX_HEADER_ID, a NUMBER column that also serves as the business-key candidate through the unique index JTY_DEA_VALUES_IDX_HEADER_U1. Because the unique index covers the same column as the primary key, there is no separate natural business key exposed in the documented metadata.

Common Use Cases and Queries

Typical usage centers on diagnosing DEA index build failures, auditing which indexes remain unbuilt, and reporting index definitions per source or qualification usage. A common pattern filters on the build flag to find pending work:

  • SELECT SOURCE_ID, INDEX_NAME, BUILD_INDEX_FLAG FROM JTF.JTY_DEA_VALUES_IDX_HEADER WHERE BUILD_INDEX_FLAG = 'Y';
  • Joining to JTF_QUAL_USGS_ALL on QUAL_USG_ID to resolve usage names for reporting.
  • Querying by INDEX_NAME (N3) to locate all headers referencing a given index.
  • Excluding logically deleted rows with WHERE DELETE_FLAG IS NULL OR DELETE_FLAG = 'N'.
  • Tracking modification activity through LAST_UPDATE_DATE and LAST_UPDATED_BY.

Related Objects

The documented FK relationships and dependencies identify the following significant related objects:

  • JTF_QUAL_USGS_ALL — referenced through QUAL_USG_ID.
  • FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID for hosted environments.
  • JTY_DEA_VALUES_IDX_HEADER# — the underlying table type object that references this table.
  • JTF.JTY_DEA_VALUES_IDX_HEADER — the base table itself, queryable through the standard SELECT template documented in ETRM.

The table does not reference additional database objects beyond the two foreign keys noted, and the metadata does not document PL/SQL APIs or views that consume it. Any integration work should therefore be driven from the documented column list and the three nonunique indexes, all of which reside in the APPS_TS_TX_IDX tablespace.