Results for “css_def_def_languages”

12 results




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

Overview

CSS_DEF_DEF_LANGUAGES is an obsolete child table within the Oracle E-Business Suite CSS (Support) module. Its purpose is to associate one or more languages with a defect or enhancement record. Per the ETRM metadata definition, a defect or enhancement may carry multiple associated languages but only one of them may be flagged as the primary language. In practice the table functions as an associative detail entity beneath the parent defect/enhancement master, carrying both the foreign key to the parent record and the language reference.

Under the heuristic Data Vault classification derived from the foreign key structure, this table is modelled as a link — it resolves a many-to-many style relationship between defect/enhancement records and language definitions, and adds an attribute (the primary language indicator) on that relationship. This classification reflects the FK-to-hub topology rather than an assertion of any physical Data Vault implementation.

The ETRM record explicitly states "Not implemented in this database." This is a critical operational fact: CSS_DEF_DEF_LANGUAGES is a legacy object from earlier Support (CSS) schemas and is not present in the standard 12.1.1 / 12.2.2 database. Customization or interfaces targeting this table will fail unless the object has been separately created.

Key Information Stored

The documented metadata identifies a small, focused column set. The principal columns are:

  • DEF_LANGUAGE_ID — the surrogate primary key of the table, sourced from the CSS_DEF_DEF_LANGUAGES_PK constraint. No natural business key is documented, so this column is the sole unique identifier.
  • DEFECT_ID — foreign key to CSS_DEF_DEFECTS_B, identifying the parent defect or enhancement to which the language association belongs.
  • LANGUAGE_ID — foreign key to CSS_DEF_LANGUAGES_B, identifying the language definition being associated.
  • Primary language indicator — implied by the description ("may only have one primary language"); the physical column name is not enumerated in the supplied metadata, and its enforcement, if present, would normally be a check or application-level rule rather than a table constraint.

No unique business index beyond the surrogate primary key is documented. A candidate composite business key of (DEFECT_ID, LANGUAGE_ID) is a reasonable modelling expectation given the semantics, but it is not confirmed by the ETRM record.

Common Use Cases and Queries

When present, this table is used to drive multilingual defect reporting, support escalation routing based on the reporter's language, and translation-coverage analysis across open defects. Typical query patterns join the parent and language dimension tables:

  • Languages per defect: SELECT DEFECT_ID, COUNT(*) FROM CSS_DEF_DEF_LANGUAGES GROUP BY DEFECT_ID — supports coverage and duplication checks.
  • Parent join: SELECT d.*, l.* FROM CSS_DEF_DEFECTS_B d JOIN CSS_DEF_DEF_LANGUAGES dl ON dl.DEFECT_ID = d.DEFECT_ID JOIN CSS_DEF_LANGUAGES_B l ON l.LANGUAGE_ID = dl.LANGUAGE_ID.
  • Primary-language filtering: filtering on the primary indicator to produce one authoritative row per defect for reporting.
  • Integrity validation: detecting orphans through outer joins against CSS_DEF_DEFECTS_B and CSS_DEF_LANGUAGES_B.

Because the object is obsolete and not present, all such queries should be preceded by an existence check against ALL_TABLES before deployment.

Related Objects

The FK metadata documents two direct dependencies:

  • CSS_DEF_DEFECTS_B — parent defect/enhancement table, joined on DEFECT_ID.
  • CSS_DEF_LANGUAGES_B — language definition table, joined on LANGUAGE_ID.
  • CSS_DEF_DEF_LANGUAGES_PK — the primary key constraint on DEF_LANGUAGE_ID, which underpins the surrogate identity of every row.

Adjacent CSS objects (defect types, statuses, and translation variants) are commonly analysed alongside this table, but they are not documented as direct foreign-key dependencies here and should be treated as contextual only.