Results for “problem_category_id”

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

Overview

CSS_DEF_PROB_CATEGORIES_TL is the translatable (language-dependent) child table for problem category definitions within the Oracle E-Business Suite CSS — Support module. The "_TL" suffix follows the standard Oracle Applications convention: for every base entity table there is a companion "_TL" table that stores the same descriptive attributes once per installed language, keyed by the entity's primary key plus a LANGUAGE column. Its stated purpose in the ETRM metadata is simply "Translatable table for problem category," and the module itself is flagged as obsolete, meaning it is retained for historical compatibility rather than active functional use.

The metadata records the object as "Not implemented in this database," and the only keys documented are the composite primary key CSS_DEF_PROB_CATEGORIES_TL_PK over (PROBLEM_CATEGORY_ID, LANGUAGE). Taken as a modelling suggestion, the heuristic Data Vault classification for this object is standalone: no foreign-key relationships were mined from the FK structure, so it is not a link table and no dependent satellites were identified around it. In Data Vault terms it behaves as an independent, self-contained descriptive set rather than a hub-and-satellite construct with radiating relationships.

Key Information Stored

The documented column inventory for this table is intentionally narrow, and only the following columns are confirmed in the ETRM metadata:

• PROBLEM_CATEGORY_ID — the surrogate identifier for the problem category. It is the leading component of the composite primary key and is the column most commonly referenced by consumers searching for "problem_category_id."
• LANGUAGE — the language code of the row, the second component of CSS_DEF_PROB_CATEGORIES_TL_PK. Together with PROBLEM_CATEGORY_ID it guarantees one description row per category per installed language.

The surrogate primary key is therefore the pair (PROBLEM_CATEGORY_ID, LANGUAGE), not a single-column key. No separate unique index or alternate business key is documented in the supplied metadata; the translatable text attributes that would normally accompany a "_TL" table are not enumerated in the ETRM excerpt, so they should be confirmed against the actual dictionary views in a given instance before being relied upon in code or reports.

Common Use Cases and Queries

Because the moduule is obsolete and the object is reported as not implemented in the source database, practical usage centres on validation, migration, and legacy reporting rather than active transaction processing. Typical patterns include checking whether the object exists in a given environment, resolving a category identifier to its descriptive text, and enumerating translations for a multi-language deployment.

• Existence and definition checks: query FND_TABLES or ALL_TAB_COLUMNS where TABLE_NAME = 'CSS_DEF_PROB_CATEGORIES_TL' to confirm implementation status.
• Single-language lookup: SELECT * FROM CSS_DEF_PROB_CATEGORIES_TL WHERE PROBLEM_CATEGORY_ID = :id AND LANGUAGE = USERENV('LANG').
• All translations for one category: SELECT LANGUAGE FROM CSS_DEF_PROB_CATEGORIES_TL WHERE PROBLEM_CATEGORY_ID = :id ORDER BY LANGUAGE.
• Orphan detection: outer-join the translatable rows to the base problem category table on PROBLEM_CATEGORY_ID to find categories lacking a translation row.
• Legacy reporting: reconcile problem category identifiers captured in historical support records against the current definition set before archival.

Related Objects

The ETRM relationship data classifies this table as standalone, so no foreign-key relationships to other objects were mined. The most significant related objects are therefore inferred from conventions and from the shared PROBLEM_CATEGORY_ID column:

• CSS_DEF_PROB_CATEGORIES_B — the presumed base (non-translatable) table holding the language-independent category attributes; join on PROBLEM_CATEGORY_ID.
• CSS_DEF_PROB_CATEGORIES_VL — the presumed multi-language view that unions the base and _TL rows.
• FND_LANGUAGES — reference object validating the LANGUAGE column.
• FND_TABLES / ALL_TAB_COLUMNS — dictionary sources used to verify whether the obsolete object is implemented.

All statements above rest on the documented primary key, the standalone classification, and the obsolete-module flag; column-level detail beyond PROBLEM_CATEGORY_ID and LANGUAGE was not present in the supplied metadata.