Results for “css_def_templ_matrix”

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

Overview

CSS_DEF_TEMPL_MATRIX is a configuration table within the Oracle E-Business Suite CSS (Support) module. Its documented purpose is to store the template mapping for a Problem Category / Problem Type / Item combination, allowing a template to be mapped to any combination of these three identifiers. All three identifiers are optional, but at least one identifier must be supplied for a valid mapping row. This design gives administrators fine-grained control over which response or diagnostic template is applied when a service request or problem is categorized in a particular way.

The ETRM metadata flag the product as "CSS - Support (Obsolete)" and state that the table is "Not implemented in this database" for the documented EBS releases, meaning it is a legacy or dormant configuration object that may not be present in every environment. Its heuristic Data Vault classification is link, mined from its foreign key structure. In Data Vault modeling terms, this table functions as a link table resolving associations between three business entities: problem types, problem categories, and templates. It should therefore be modeled as a relationship/link construct rather than as a standalone hub or satellite.

Key Information Stored

The table's primary key is defined by the constraint CSS_DEF_TEMPL_MATRIX_PK on the surrogate column TEMPLATE_MATRIX_ID, which is a system-generated identifier uniquely tagging each mapping row. The remaining significant columns are the business keys that form the association itself:

• TEMPLATE_MATRIX_ID — surrogate primary key; system-generated unique row identifier.
• TEMPLATE_ID — foreign key to CSS_DEF_TEMPLATES_B; identifies the template being mapped.
• PROBLEM_TYPE_ID — foreign key to CSS_DEF_PROB_TYPES_B; identifies the problem type for the mapping.
• PROBLEM_CATEGORY_ID — foreign key to CSS_DEF_PROB_CATEGORIES_B; identifies the problem category for the mapping.

The composite of TEMPLATE_ID, PROBLEM_TYPE_ID, and PROBLEM_CATEGORY_ID represents the candidate business key for this mapping; the exact unique index definition is not documented in the supplied metadata. Note that because all three identifiers are optional but at least one is mandatory, multiple rows may exist with only TEMPLATE_ID populated (a default template), while others narrow the match by including one or both of the classification identifiers. Given the limited column set documented, the table does not appear to carry descriptive attributes beyond the mapping itself, which is consistent with its link classification.

Common Use Cases and Queries

The principal use case is deterministic template resolution: given a problem category, problem type, and item, determine which template should be presented. Reporting and validation queries typically join this matrix to the three referenced tables to render human-readable names. A representative pattern is:

• Resolve a template by category and type: SELECT tm.template_matrix_id, t.template_name FROM css_def_templ_matrix tm, css_def_templates_b t WHERE tm.template_id = t.template_id AND tm.problem_category_id = :category_id AND tm.problem_type_id = :type_id;
• Find default (unqualified) mappings: SELECT * FROM css_def_templ_matrix WHERE problem_type_id IS NULL AND problem_category_id IS NULL;
• Audit coverage: left-join CSS_DEF_PROB_CATEGORIES_B and CSS_DEF_PROB_TYPES_B to list which categories or types have no template mapping, surfacing configuration gaps.
• Data-quality checks: identify rows where all three identifiers except TEMPLATE_ID are null, or conversely rows violating the "at least one identifier" rule if data was loaded by non-standard means.

Because the table is flagged obsolete and "not implemented" in the documented environments, any investigative query should first verify object existence in ALL_TABLES before assuming rows are available.

Related Objects

The FK relationships documented above define the immediate dependency set:

• CSS_DEF_TEMPLATES_B — joined on TEMPLATE_ID; the parent holding template definitions referenced by the matrix.
• CSS_DEF_PROB_TYPES_B — joined on PROBLEM_TYPE_ID; supplies problem type classification.
• CSS_DEF_PROB_CATEGORIES_B — joined on PROBLEM_CATEGORY_ID; supplies problem category classification.
• CSS_DEF_TEMPL_MATRIX_PK — the primary key constraint enforcing row uniqueness on TEMPLATE_MATRIX_ID.

Related translation, item, and service-request objects in the CSS/Support schema may also participate in template resolution at runtime, but the three parent tables above are the only ones formally documented as foreign key targets.