Results for “iex_query_temp_xref_u2”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IEX_QUERY_TEMP_XREF is a cross-reference table in the Oracle E-Business Suite IEX schema (the Interaction/Collections component of Oracle Advanced Collections and iReceivables). Its documented purpose is to hold the association between XDO (XML Publisher / BI Publisher) templates and the SQL queries defined in the Collections module. In practical terms, it maps a stored query defined in IEX_XML_QUERIES to the template stored in XDO_TEMPLATES_VL, allowing the Collections engine to determine which XML Publisher template should render the output of a given query.

The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and is indexed in APPS_TS_TX_IDX. It is a small, low-volume configuration-style object rather than a transactional fact table.

From a Data Vault modeling perspective, the heuristic classification for this object is standalone. It is not strongly modelled as a hub, link, or satellite, because the documented FK structure shows it is referenced by other tables rather than itself serving as a central integration point. A modeler could nonetheless treat QUERY_TEMP_ID as a hub key, with QUERY_ID and TEMPLATE_ID acting as business-key components that form a natural link between the query and template domains.

Key Information Stored

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

• QUERY_TEMP_ID — the surrogate primary key (documented constraint IQTX_PK). It is the mandatory identifier for each cross-reference row and is the column referenced by dependent tables.
• QUERY_ID — foreign key to IEX_XML_QUERIES, identifying the Collections SQL query. It participates in the unique business-key index.
• TEMPLATE_ID — foreign key to XDO_TEMPLATES_VL, identifying the XML Publisher template bound to the query. It also participates in the unique business key.
• CREATED_BY, CREATION_DATE — standard who-column audit attributes capturing the creating user and timestamp.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit attributes tracking the most recent modification and the login under which it occurred.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle Application Framework (OAF) / Forms layer to detect concurrent updates.

The unique index IEX_QUERY_TEMP_XREF_U2 on (QUERY_ID, TEMPLATE_ID) is the documented business-key candidate, enforcing that a given query-template pairing is registered only once. The non-unique index IEX_QUERY_TEMP_XREF_U1 on QUERY_TEMP_ID supports lookups by primary key.

Common Use Cases and Queries

Typical scenarios include diagnosing why a Collections correspondence, dunning letter, or statement renders with the wrong layout, and auditing which templates are bound to which queries before a patch or template migration.

A basic listing of all bindings:

• SELECT QUERY_TEMP_ID, QUERY_ID, TEMPLATE_ID FROM IEX.IEX_QUERY_TEMP_XREF;

Resolving a template for a specific query joins to XDO_TEMPLATES_VL on TEMPLATE_ID. Reverse lookups from a template use IEX_QUERY_TEMP_XREF_U2. Because the table is configuration data with a small row count, reporting queries rarely need additional hints or partitioning strategies. Audit reporting can compare CREATION_DATE and LAST_UPDATE_DATE to detect recently altered bindings.

Related Objects

The following objects are significant in relation to this table:

• IEX_XML_REQUEST_HISTORIES — references IEX_QUERY_TEMP_XREF via QUERY_TEMP_ID, recording historical XML request executions against a given cross-reference.
• IEX_XML_QUERIES — source of QUERY_ID; defines the SQL query bound to a template.
• XDO_TEMPLATES_VL — source of TEMPLATE_ID; the XML Publisher template definition.
• IEX_QUERY_TEMP_XREF (APPS synonym) — the APPS-layer synonym through which application code and concurrent programs access the table.

Together these objects support the template-query binding configuration that underpins Collections correspondence generation in Oracle EBS 12.1.1 and 12.2.2.