Results for “css_def_templ_details_b”

8 results




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

Overview

CSS_DEF_TEMPL_DETAILS_B is a legacy Oracle EBS table belonging to the CSS – Support product family, which Oracle has classified as obsolete. The table stored the individual prompts that together compose a template, where each prompt is bound exclusively to a single parent template. In the ETRM documentation for this object, the implementation status is explicitly recorded as "Not implemented in this database," meaning the table is not present or populated in current releases and should be treated as a historical artifact rather than a live transactional object.

Based on the heuristic Data Vault classification mined from its foreign key structure, the table is a satellite-leaning entity. This is consistent with its design: the table hangs off CSS_DEF_TEMPLATES_B through a foreign key and carries descriptive attributes (the prompt definitions) rather than acting as an independent hub of business identity or a many-to-many link. Administrators encountering this table in older 11i-derived or early 12.1.x environments should recognize it as a dependent detail table tied to the template header.

Key Information Stored

The documented metadata identifies only a limited set of columns, but these define the table's purpose:

  • TEMPLATE_DETAIL_ID — the surrogate primary key, backed by the constraint CSS_DEF_TEMPL_DETAILS_B_PK. This is the unique identifier for each prompt row.
  • TEMPLATE_ID — foreign key column referencing CSS_DEF_TEMPLATES_B. This establishes the parent-child relationship between a template header and its individual prompt definitions, and is the primary business-key candidate used for grouping and joining.

Because the documentation excerpt only names these two columns, additional attribute columns (such as prompt text, sequence, or display order) are not confirmed in the ETRM metadata and should be verified against the physical schema in any legacy instance before being referenced in code or reports. The template ID combined with detail ID effectively differentiates each prompt, and the FK constraint enforces referential integrity back to the template header.

Common Use Cases and Queries

In environments where this table still exists, its principal use cases center on template definition reporting and migration analysis:

  • Listing all prompts belonging to a given template, joining detail rows to the header via TEMPLATE_ID.
  • Auditing templates for completeness by counting detail rows per template.
  • Reconstructing legacy template definitions prior to an upgrade, since Oracle marks the CSS product as obsolete.

A representative query pattern joins the detail table to its parent:

  • SELECT d.TEMPLATE_DETAIL_ID, d.TEMPLATE_ID FROM CSS_DEF_TEMPL_DETAILS_B d, CSS_DEF_TEMPLATES_B t WHERE d.TEMPLATE_ID = t.TEMPLATE_ID;

Reporting should account for the possibility that the table is absent, so existence checks or conditional logic are advisable before deployment.

Related Objects

The following objects are the most significant in relation to this table, based on the documented foreign key and primary key relationships:

  • CSS_DEF_TEMPLATES_B — the parent header table; joined through CSS_DEF_TEMPL_DETAILS_B.TEMPLATE_ID.
  • CSS_DEF_TEMPL_DETAILS_B_PK — the primary key constraint on TEMPLATE_DETAIL_ID that uniquely identifies each prompt row.
  • CSS – Support module — the obsolete product context governing the table and related template definitions.

Any dependent views, concurrent programs, or APIs from the original CSS module should be treated with caution, as Oracle no longer supports them in 12.1.1 or 12.2.2. The join column TEMPLATE_ID remains the single documented bridge between this detail table and its template header.