Results for “cac_sr_exceptions_tl”

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

Overview

The table JTF.CAC_SR_EXCEPTIONS_TL is the translation table for the Service Request exception definitions maintained by the CRM Foundation (JTF) module in Oracle E-Business Suite 12.1.1 and 12.2.2. Interacting with the base table CAC_SR_EXCEPTIONS_B, it stores the language-specific or translated text attributes for each exception record — name and description — enabling multi-language support for exception records used in Service Request workflows and related CRM Foundation processing.

The object resides in the JTF schema and is documented as VALID with a physical schema comprising 10 columns. Its primary key is CAC_SR_EXCEPTIONS_TL_PK, defined over (EXCEPTION_ID, LANGUAGE), and a matching unique index CAC_SR_EXCEPTIONS_TL_U1 exists over the same column pair, representing the business-key candidate. The single documented foreign key, CAC_SR_EXCEPTIONS_TL.EXCEPTION_ID → CAC_SR_EXCEPTIONS_B, ties every translation row back to its base exception definition. Under a heuristic Data Vault classification mined from the FK structure, this table is satellite-leaning: it is a descriptive, dependent table that records context and attributes around a parent business key rather than acting as a hub or link on its own.

Key Information Stored

The columns documented for CAC_SR_EXCEPTIONS_TL are EXCEPTION_ID, LANGUAGE, SOURCE_LANG, EXCEPTION_NAME, EXCEPTION_DESC, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN. The most significant of these are:

• EXCEPTION_ID — the surrogate identifier inherited from the base table; part of the composite primary key and the FK to CAC_SR_EXCEPTIONS_B.
• LANGUAGE — the language code for the translation row; with EXCEPTION_ID it forms the primary key and the unique business-key index CAC_SR_EXCEPTIONS_TL_U1.
• SOURCE_LANG — the language of the source (base) record from which the translated text is derived.
• EXCEPTION_NAME — the translated display name of the exception, used in user-facing CRM Foundation screens and lists.
• EXCEPTION_DESC — the translated descriptive text for the exception, used in detail views and reporting.
• CREATED_BY, CREATION_DATE — audit columns capturing who inserted the row and when.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — audit columns capturing the last change and the login context of the modifier.

Common Use Cases and Queries

Typical usage retrieves translated exception text for a target language and joins it to the base definition. A representative pattern is:

• Translating a code: SELECT tl.exception_name, tl.exception_desc FROM jtf.cac_sr_exceptions_tl tl WHERE tl.exception_id = :p_id AND tl.language = USERENV('LANG');
• Listing all languages for one exception: SELECT language, exception_name FROM jtf.cac_sr_exceptions_tl WHERE exception_id = :p_id;
• Join to the base table for combined business and translated attributes: SELECT b.*, tl.exception_name, tl.exception_desc FROM jtf.cac_sr_exceptions_b b, jtf.cac_sr_exceptions_tl tl WHERE b.exception_id = tl.exception_id AND tl.language = :lang;
• Audit and translation-completeness reporting comparing SOURCE_LANG against LANGUAGE to identify missing translations.

Reports commonly filter by LANGUAGE to present localized labels, and by CREATION_DATE/LAST_UPDATE_DATE to audit when translations were maintained.

Related Objects

The most significant related objects include:

• CAC_SR_EXCEPTIONS_B — the base table; joined via CAC_SR_EXCEPTIONS_B.EXCEPTION_ID = CAC_SR_EXCEPTIONS_TL.EXCEPTION_ID. This is the sole documented foreign-key relationship.
• CAC_SR_EXCEPTIONS_TL_PK — the primary-key constraint over (EXCEPTION_ID, LANGUAGE).
• CAC_SR_EXCEPTIONS_TL_U1 — the unique index over (EXCEPTION_ID, LANGUAGE), the documented business-key candidate.
• CRM Foundation Service Request processing code and concurrent programs that read translated exception definitions at runtime.
• Related CAC_SR_* TL/B table pairs (e.g., other CAC_SR_EXCEPTIONS-family definitions) that follow the same base-plus-translation pattern.

Together these objects form the exception-definition layer within the JTF CRM Foundation data model.