Search Results aso_sup_tmpl_instance_u1

Overview

ASO.ASO_SUP_TMPL_INSTANCE is a transactional table in the Oracle E-Business Suite ASO (Order Capture / Sales) schema that stores the runtime instance of a supplemental template. When a user associates a supplemental template with a quote, order, or other owning entity, a template instance row is created and linked to that entity through the OWNER_TABLE_NAME and OWNER_TABLE_ID columns. The table therefore answers the question "which supplemental template is tied to which owning document," providing the persistence layer behind the supplementary information (sup) template feature used across Oracle Quoting, Order Management, and related modules.

The table resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10 and is a valid, documented object in both Oracle EBS 12.1.1 and 12.2.2. Under the heuristic Data Vault classification mined from the foreign key structure, the table is treated as standalone, meaning it does not fit cleanly into a hub, link, or satellite pattern; it is better modeled as a transactional record that carries both a surrogate key and a polymorphic owner reference. This classification is a modeling suggestion rather than a schema constraint.

Key Information Stored

The table has 32 documented columns. The most important are:

• TEMPLATE_INSTANCE_ID — NUMBER; the surrogate primary key (ASO_SUP_TMPL_INSTANCE_PK) and the column behind the unique index ASO_SUP_TMPL_INSTANCE_U1. Every dependent child row references this value.
• TEMPLATE_ID — NUMBER; identifies the underlying supplemental template definition that was instantiated.
• OWNER_TABLE_NAME — VARCHAR2(30); the name of the entity type the instance is attached to (for example, the quote or order table).
• OWNER_TABLE_ID — NUMBER; the primary key of the owning entity. Together with OWNER_TABLE_NAME this forms the non-unique business lookup indexed by ASO_SUP_TMPL_INSTANCE_N1.
• SECURITY_GROUP_ID — NUMBER; references FND_SECURITY_GROUPS and enforces multi-org / data-security partitioning.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — standard WHO columns recording creation and change audit information, with the _BY columns foreign-keying to FND_USER and FND_LOGINS.
• OBJECT_VERSION_NUMBER — NUMBER; used for optimistic locking during concurrent updates through the OAF/BC4J middle tier.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE20 — VARCHAR2(240) descriptive flexfield segments reserved for customer-specific extensions.

The business-key candidate documented for this table is TEMPLATE_INSTANCE_ID, exposed through the unique index ASO_SUP_TMPL_INSTANCE_U1. Note that TEMPLATE_ID itself is not unique, since one template may be instantiated against many owners.

Common Use Cases and Queries

The primary reporting use case is determining which template is applied to a given quote or order. A typical query joins the instance to its owning document by way of the polymorphic owner columns:

• SELECT template_instance_id, template_id, owner_table_id FROM aso.aso_sup_tmpl_instance WHERE owner_table_name = :p_table AND owner_table_id = :p_id;
• To enumerate all supplemental answers captured for an instance, join to ASO_SUP_INSTANCE_VALUE on TEMPLATE_INSTANCE_ID.
• For template re-use analysis, aggregate on TEMPLATE_ID to count how many owners share the same template.
• For security-filtered extracts, join SECURITY_GROUP_ID to FND_SECURITY_GROUPS and restrict by the operating unit's security profile.
• For integration and audit, filter on LAST_UPDATE_DATE and CREATED_BY to report recently created or modified instances.

Because the child tables AMS_QUERY_TEMPLATE_INSTANCE and AMS_QUERY_TEMP_INST_COND_ASSOC also carry TEMPLATE_INSTANCE_ID, analysts frequently traverse from those marketing/query tables back into this table to resolve template context. Purge and reconciliation scripts should treat TEMPLATE_INSTANCE_ID as the stable join key rather than the owner columns, since the owner pair is non-unique.

Related Objects

• ASO.ASO_SUP_INSTANCE_VALUE — child table; joins on TEMPLATE_INSTANCE_ID. Stores captured values for each template instance field.
• AMS.AMS_QUERY_TEMPLATE_INSTANCE — references TEMPLATE_INSTANCE_ID; links query definitions to the template instance.
• AMS.AMS_QUERY_TEMP_INST_COND_ASSOC — references TEMPLATE_INSTANCE_ID; stores condition associations for the instance.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID; drives data security partitioning.
• FND_USER — source of CREATED_BY and LAST_UPDATED_BY values.
• ASO.ASO_SUP_TMPL_INSTANCE_PK / _U1 / _N1 — the primary key constraint and indexes that support lookups by instance ID and by owner.