Results for “okc_deliverable_types_tl”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OKC_DELIVERABLE_TYPES_TL is the translation table for Deliverable Types in the Oracle Contracts Core (OKC) module. It stores the language-specific, translatable attributes of a Deliverable Type — principally the display name and description — keyed by the deliverable type code and the language in which the text is expressed. Deliverable Types define the categories of deliverables that can be tracked against a contract or contract line, such as documents, services, goods, or milestone artifacts. Because contract terminology must be presented to users in their selected language, the base definition lives in OKC_DELIVERABLE_TYPES_B and the descriptive text lives in this _TL table.
From a Data Vault modeling perspective, the ETRM metadata classifies this object heuristically as standalone, with no foreign keys mined from its physical structure. This suggests that OKC_DELIVERABLE_TYPES_TL behaves as a self-contained reference or lookup object rather than a link connecting other hubs. In a Data Vault design, the columns NAME and DESCRIPTION are the language-dependent descriptive attributes, which map naturally to satellite semantics, while DELIVERABLE_TYPE_CODE functions as the business key inherited from the underlying base entity.
Key Information Stored
The table contains eleven documented columns. The most significant are:
- DELIVERABLE_TYPE_CODE — The business identifier of the deliverable type. Together with LANGUAGE and ZD_EDITION_NAME it forms the business-key candidate exposed by unique index OKC_DELIVERABLE_TYPES_TL_U1.
- LANGUAGE — The language code (for example, US or FR) governing the NAME and DESCRIPTION values in that row.
- NAME — The translated display name of the deliverable type shown to users in the corresponding language.
- DESCRIPTION — The translated longer description providing the meaning or usage of the deliverable type.
- SOURCE_LANG — Identifies the source language from which the translation originated, useful for translation tracking and completeness reporting.
- ZD_EDITION_NAME — The edition identifier supporting Oracle's edition-based redefinition capability, included in the unique business-key index.
- CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns recording who created and last modified each row, when, and through which login session.
The physical primary key OKC_DELIVERABLE_TYPES_TL_PK is a composite surrogate key over DELIVERABLE_TYPE_CODE and LANGUAGE, distinguishing one translated row per code and language. The unique index OKC_DELIVERABLE_TYPES_TL_U1 extends that combination with ZD_EDITION_NAME, and represents the strongest business-key candidate.
Common Use Cases and Queries
Typical usage centers on resolving human-readable labels for deliverable types in a specific language. A common reporting query joins this table to the base definition and filters by language:
- Retrieving all translations for a type:
SELECT deliverable_type_code, language, name, description FROM okc_deliverable_types_tl WHERE deliverable_type_code = :code ORDER BY language; - Resolving a single label for a given session language:
SELECT name, description FROM okc_deliverable_types_tl WHERE deliverable_type_code = :code AND language = USERENV('LANG'); - Auditing translation coverage by identifying types missing rows for a target language, excluding SOURCE_LANG, to find gaps before a localization release.
- Driving value-set or LOV displays in contract authoring, where the translated NAME supplies the list entry and DESCRIPTION supplies the tooltip.
- Feeding downstream data warehouse dimension loads, treating DELIVERABLE_TYPE_CODE and LANGUAGE as the composite natural key.
Related Objects
The following objects are the most significant counterparts and dependencies for OKC_DELIVERABLE_TYPES_TL:
- OKC_DELIVERABLE_TYPES_B — The base (non-translated) table holding language-independent deliverable type attributes; join on DELIVERABLE_TYPE_CODE to combine base data with translated text.
- OKC_DELIVERABLE_TYPES_VL — The MLS view that merges base and translation rows, typically the object referenced by forms and APIs rather than the _TL table directly.
- OKC_DELIVERABLES — Instances of deliverables associated with a contract that reference their deliverable type.
- OKC_DELIVERABLE_TYPE_USES — Where documented, defines how deliverable types apply to contract categories or templates.
- OKC_CONTRACTS / OKC_K_LINES — The contract header and line entities whose deliverable tracking ultimately consumes these types.
- FND_LANGUAGES — Provides validation and descriptive names for the LANGUAGE and SOURCE_LANG columns.
-
Stores translatable information for a Deliverable Type
-
Stores translatable information for a Deliverable Type
-
View based on OKC_DELIVERABLE_TYPES_B and OKC_DELIVERABLE_TYPES_TL
APPS.OKC_DELIVERABLE_TYPES_VL·↳ OKC_DELIVERABLE_TYPES_B·↳ OKC_DELIVERABLE_TYPES_TL·Explore OKC module →
-
View based on OKC_DELIVERABLE_TYPES_B and OKC_DELIVERABLE_TYPES_TL
APPS.OKC_DELIVERABLE_TYPES_VL·↳ OKC_DELIVERABLE_TYPES_B·↳ OKC_DELIVERABLE_TYPES_TL·Explore OKC module →
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
eTRM - OKC Tables and Views 12.1.1
Intersection entity between templates and rules.
-
eTRM - OKC Tables and Views 12.2.2
Intersection entity between rules and templates