Search Results sys_il0000084358c00003

Overview

JTF.JTF_HEADER_DTD is a seed-data table in the Oracle E-Business Suite Customer Relationship Management (CRM) foundation schema (JTF). Its documented purpose is to store common header Document Type Definitions (DTDs), the XML schema artifacts used by the CRM Technology Foundation (JTF) infrastructure to describe, validate, and parse XML documents exchanged between EBS components such as Oracle Marketing, Oracle TeleSales, Oracle Scripting, and Oracle iStore. The table resides in the APPS_TS_SEED tablespace, confirming its role as a seeded configuration repository rather than a high-volume transactional table. The object is reported VALID in both Oracle EBS 12.1.1 and 12.2.2.

From a Data Vault modeling perspective, the metadata's heuristic classification is standalone (no foreign-key dependents and no outbound references are documented). If this table were to be modeled dimensionally, the classification would most closely resemble a hub-and-satellite pattern: HEADER_DTD_ID acts as the hub business key, while DTD_NAME, HEADER_DTD, and ACTIVE_FLAG function as descriptive satellite attributes. The absence of link-table relationships reinforces that this is a reference/definition entity rather than a transactional intersection.

Key Information Stored

The most significant columns documented in the ETRM schema are:

• HEADER_DTD_ID (NUMBER) — the surrogate primary key, enforced by the unique index JTF_HEADER_DTD_PK. This is the column referenced by downstream XML processing code.
• DTD_NAME (VARCHAR2, 50) — the logical name of the DTD, used by runtime framework code to select the correct header template for a given document type.
• HEADER_DTD (CLOB, 4000) — the actual DTD content. Because it is a CLOB, the table carries a LOB index (SYS_IL0000084358C00003$$), which the ETRM metadata lists as the unique index just below the primary key; the empty column list in that index definition is a documentation artifact of the LOB segment.
• ACTIVE_FLAG (VARCHAR2) — the Y/N flag that determines which DTD version is currently in use.
• Standard WHO columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — audit fields capturing the FND_USER.USER_ID and FND_LOGINS.LOGIN_ID of the creating and last-updating user sessions.
• ATTRIBUTE1 through ATTRIBUTE5 (VARCHAR2, 50) — descriptive flexfield (DFF) segments, providing an extension point for customer-specific DTD metadata.
• ZD_EDITION_NAME — the editioning column present in the 12.2.2 schema, supporting Online Patching (adop) edition-based redefinition.

Only HEADER_DTD_ID is enforced as a unique business key (via the PK); DTD_NAME is a strong candidate for a natural business key but is not documented as uniquely indexed.

Common Use Cases and Queries

Typical use cases include auditing which DTDs are active, troubleshooting XML parsing failures in CRM document exchange, and extracting the raw DTD text for comparison across environments. A representative query is:

• Retrieve active DTDs: SELECT HEADER_DTD_ID, DTD_NAME FROM JTF.JTF_HEADER_DTD WHERE ACTIVE_FLAG = 'Y';
• Read a specific DTD body: SELECT DTD_NAME, HEADER_DTD FROM JTF.JTF_HEADER_DTD WHERE DTD_NAME = :name;
• Audit recent changes: SELECT DTD_NAME, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM JTF.JTF_HEADER_DTD;
• Detect customised rows via DFF: SELECT * FROM JTF.JTF_HEADER_DTD WHERE ATTRIBUTE1 IS NOT NULL;
• Confirm edition visibility (12.2.2): SELECT HEADER_DTD_ID, ZD_EDITION_NAME FROM JTF.JTF_HEADER_DTD;

The query text documented in ETRM selects the full column list from JTF.JTF_HEADER_DTD; because HEADER_DTD is a CLOB, reports should avoid selecting it in bulk and should instead apply DBMS_LOB.SUBSTR where only a preview is needed.

Related Objects

The documented relationship data classifies this object as standalone; no FK constraints from JTF_HEADER_DTD to other tables are listed, and no inbound FK references are documented. The object is, however, referenced by the APPS synonym JTF_HEADER_DTD, which is the runtime access path used by forms, concurrent programs, and PL/SQL packages. Logical associations (not enforced by FK) that are significant in practice include:

• JTF.JTF_HEADER_DTD (APPS synonym) — the runtime entry point exposing the same physical table.
• FND_USER — joined on CREATED_BY / LAST_UPDATED_BY / LAST_UPDATED_BY to resolve user names.
• FND_LOGINS — joined on LAST_UPDATE_LOGIN to identify the session.
• The LOB segment SYS_IL0000084358C00003$$ (APPS_TS_SEED) — the index supporting the HEADER_DTD CLOB.
• JTF_HEADER_DTD_PK — the primary key constraint on HEADER_DTD_ID.

Where the metadata is silent on additional dependencies, the documented fact remains that JTF_HEADER_DTD does not reference any database object and is referenced only through its APPS synonym within the JTF schema family.