Results for “css_def_templates_b”

10 results




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

Overview

CSS_DEF_TEMPLATES_B is a base table within the Oracle E-Business Suite (EBS) schema associated with the CSS – Support product module. Its documented purpose is to hold information about templates, functioning as the parent container that defines the top-level template records consumed by dependent detail and matrix structures. In Oracle EBS 12.1.1 and 12.2.2, this table is classified as an obsolete object and is documented as "Not implemented in this database," meaning it is not physically created or populated in a standard installation of either release. It is retained in the ETRM reference material primarily for completeness and historical lineage rather than active runtime use.

From a data modeling perspective, the heuristic Data Vault classification assigned to this object is hub-leaning. This reflects the table's structural profile: it carries a single surrogate primary key, TEMPLATE_ID, and is referenced by multiple child tables through foreign keys, without itself pointing outward to other parent tables. Such a pattern is characteristic of a hub entity that anchors a cluster of dependent satellites and link structures.

Key Information Stored

Because the object is documented as not implemented, its column inventory is limited to the attributes attested in the metadata rather than a full field listing. The essential columns are:

  • TEMPLATE_ID — The surrogate primary key of the table, defined by the constraint CSS_DEF_TEMPLATES_B_PK. It uniquely identifies each template record and serves as the anchor point for the foreign key relationships described below.
  • Template descriptor attributes — The table's stated purpose is to hold information about templates; the descriptive and business-facing columns that would normally accompany the surrogate key (such as template name, code, type, or status) are not individually enumerated in the available metadata.

No unique business-key indexes beyond the primary key constraint are documented for this table. Accordingly, TEMPLATE_ID is the only confirmed identifier column, and any candidate business keys that might have existed in the original design are not distinguishable from the metadata alone.

Common Use Cases and Queries

Because CSS_DEF_TEMPLATES_B is not implemented in Oracle EBS 12.1.1 or 12.2.2, direct querying in a production environment is not expected. Practical usage arises in three contexts: legacy analysis of pre-12.x CSS migrations, data lineage and impact documentation, and schema comparison during upgrades or cloning exercises where an ETRM-driven inventory is being reconciled against the physical data dictionary.

A representative validation pattern, useful when confirming the table's absence in a target database, is:

  • SELECT table_name, status FROM dba_tables WHERE table_name = 'CSS_DEF_TEMPLATES_B'; — returns no rows when the obsolete object is absent, consistent with the ETRM note.
  • SELECT * FROM css_def_templates_b WHERE template_id = :template_id; — the canonical key-driven lookup by surrogate key, applicable only if the object has been restored or exists in a historical schema.
  • Join-based extraction against child structures, using template_id as the correlated column, to reconstruct template definitions where legacy data is available.

For reporting, the table would serve as the header source in a template-definition report, with detail rows sourced from the CSS_DEF_TEMPL_DETAILS_B and CSS_DEF_TEMPL_MATRIX child tables keyed by the same identifier.

Related Objects

The metadata documents two foreign key relationships in which CSS_DEF_TEMPLATES_B is the parent (referenced) table. Both child tables link through the TEMPLATE_ID column:

  • CSS_DEF_TEMPL_DETAILS_B — references CSS_DEF_TEMPLATES_B via CSS_DEF_TEMPL_DETAILS_B.TEMPLATE_ID.
  • CSS_DEF_TEMPL_MATRIX — references CSS_DEF_TEMPLATES_B via CSS_DEF_TEMPL_MATRIX.TEMPLATE_ID.

These relationships confirm the hub-leaning classification: CSS_DEF_TEMPLATES_B acts as the referenced anchor, while the detail and matrix tables function as dependent structures whose lifecycles are tied to the parent template record. No other dependent views, APIs, or additional foreign key relationships are documented in the available ETRM metadata.