Search Results ams_met_tpl_headers_pk

Overview

The AMS_MET_TPL_HEADERS table is an obsolete data object within the Oracle E-Business Suite (EBS) Marketing (AMS) module. It was historically responsible for storing header-level information for metric templates. These templates are foundational structures used to define and standardize the measurement of marketing campaign performance, lead generation, and other key performance indicators (KPIs). In releases 12.1.1 and 12.2.2, this standalone table has been superseded by a more robust, multi-language-capable architecture. Its role has been entirely assumed by the replacement tables AMS_MET_TPL_HEADERS_B (for base transactional data) and AMS_MET_TPL_HEADERS_TL (for translated descriptive data), in line with Oracle's standard application development practices for internationalization.

Key Information Stored

While the specific column list for this obsolete table is not detailed in the provided metadata, its primary key and relationship to child objects indicate the core data it once held. The central identifier was the METRIC_TPL_HEADER_ID, a unique sequence number serving as the primary key for each template header record. Typical columns in such a header table would have included creation dates, last update dates, created-by and last-updated-by user IDs, a template name, a description, a status code (such as 'ACTIVE' or 'INACTIVE'), and potentially a version number. The table's purpose was to define the template entity itself, while its associated details table stored the specific metrics comprising the template.

Common Use Cases and Queries

Direct interaction with the AMS_MET_TPL_HEADERS table is strongly discouraged in EBS 12.1.1 and 12.2.2, as it is obsolete. All application logic and reporting should reference the replacement _B and _TL tables. For historical data migration or audit purposes only, a query to identify any residual data might be used. However, in a standard upgraded environment, this table should be empty.

-- Example diagnostic query (for historical context only)
SELECT METRIC_TPL_HEADER_ID, COUNT(*)
FROM AMS.AMS_MET_TPL_HEADERS
GROUP BY METRIC_TPL_HEADER_ID;

The practical use case is the migration and subsequent operation using the new table structure, which supports multiple languages and follows Oracle's Application Development Framework (ADF) standards.

Related Objects

• Primary Replacement Tables: AMS_MET_TPL_HEADERS_B and AMS_MET_TPL_HEADERS_TL are the direct successors.
• Child Table (Relationship): The AMS_MET_TPL_DETAILS table holds the line items for each template and historically held a foreign key constraint (AMS_MET_TPL_DETAILS.METRIC_TPL_HEADER_ID) referencing the AMS_MET_TPL_HEADERS table's primary key. This relationship now points to the new _B table.
• Primary Key Constraint: AMS_MET_TPL_HEADERS_PK was the constraint on the METRIC_TPL_HEADER_ID column.