Search Results okc_condition_lines_tl_u1
Overview
OKC.OKC_CONDITION_LINES_TL is a translation (TL) table belonging to the Oracle Contract Core (OKC) schema, the module underpinning Oracle Contracts and its integration with Order Management, Service Contracts, and Procurement. The table stores language-specific, translatable attribute values for condition lines defined in the base table OKC_CONDITION_LINES_B, conforming to the Oracle Multi-Lingual Support (MLS) standard. In Oracle EBS 12.1.1 and 12.2.2 it appears in the APPS schema as the synonym APPS.OKC_CONDITION_LINES_TL and resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10.
Condition lines represent the individual pricing, discount, and term constructs attached to a contract or contract template. The base table captures language-independent structure and numeric values, while this TL table holds the human-readable text associated with each condition line, resolved at runtime according to the session's LANGUAGE and the translation coverage recorded in SOURCE_LANG.
Using the heuristic Data Vault classification supplied in the metadata, this object is modelled as a standalone satellite. It is neither a hub nor a link: it carries no independent business key of its own and no foreign-key relationships to other hubs beyond the security group reference. Its purpose is purely descriptive — holding translated attribute values that qualify the parent condition-line entity identified by ID in OKC_CONDITION_LINES_B.
Key Information Stored
The table contains twelve documented columns. The most significant are:
- ID (NUMBER, mandatory) — System-generated unique identifier for the condition line. It is the join key back to
OKC_CONDITION_LINES_B.IDand forms part of the primary key. - LANGUAGE (VARCHAR2(12), mandatory) — Standard MLS column identifying the language of the row. Combined with ID it forms the composite primary key
OKC_CONDITION_LINES_TL_PK. - DESCRIPTION (VARCHAR2(1995)) — The condition-line description. This is the principal translatable payload of the table.
- SOURCE_LANG (VARCHAR2(12)) — Standard MLS column recording the language in which the base record was originally created, used to determine whether a translation is required.
- SFWT_FLAG (VARCHAR2) — Indicates that a value was changed in another language. Documented as not used in the current release.
- CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Who columns providing audit lineage.
- SECURITY_GROUP_ID (NUMBER) — Used in hosted (multi-tenant) environments to partition data by security group; it carries a foreign key to
FND_SECURITY_GROUPS. - ZD_EDITION_NAME — Editioning column present in the 12.2.2 physical schema, supporting online patching via Edition-Based Redefinition.
The surrogate primary key is the composite (ID, LANGUAGE). The unique index OKC_CONDITION_LINES_TL_U1 is documented on (ID, LANGUAGE) in the 12.1.1 storage metadata, and on (ID, LANGUAGE, ZD_EDITION_NAME) in the 12.2.2 physical schema — the additional column reflecting editioning rather than a change in business meaning.
Common Use Cases and Queries
Reporting and extraction queries nearly always join this table to OKC_CONDITION_LINES_B and constrain by language to avoid duplicate rows across enabled languages. A typical single-language extract:
SELECT cl.id, cl.description FROM okc_condition_lines_tl cl WHERE cl.language = USERENV('LANG') AND cl.id = :condition_line_id;
Multi-language comparison or translation-completeness reporting uses SOURCE_LANG to detect rows awaiting translation:
- Left-join the base table to the TL table on
b.id = t.id AND t.language = 'US'and flag records wheret.id IS NULL. - Group by
languageto profile the distribution of translated condition-line descriptions across configured languages.
Because DESCRIPTION is the only free-text translatable column, full-text or pattern searches (for example, conditions containing specific discount or surcharge wording) are performed here rather than in the base table. In 12.2.2 online-patching environments, queries should tolerate the ZD_EDITION_NAME column when using edition-aware views.
Related Objects
OKC.OKC_CONDITION_LINES_B— the base table holding language-independent condition-line data; join onID. Its columns share the primary key with this table.APPS.OKC_CONDITION_LINES_TL— the APPS-schema synonym through which the table is normally queried.FND_SECURITY_GROUPS— referenced bySECURITY_GROUP_IDin hosted deployments.OKC_CONDITION_LINES_TL_U1— the unique index enforcing the (ID,LANGUAGE[,ZD_EDITION_NAME]) key.OKC_CONDITION_LINES_TL_PK— the primary-key constraint on (ID,LANGUAGE).FND_LANGUAGES— provides the installed and enabled language list that governs validLANGUAGEandSOURCE_LANGvalues.
The metadata records no additional tables, views, or APIs referencing this object beyond the APPS synonym; functional dependencies on condition headers are resolved through OKC_CONDITION_LINES_B rather than directly against the TL table.
-
INDEX: OKC.OKC_CONDITION_LINES_TL_U1
12.1.1
owner:OKC, object_type:INDEX, object_name:OKC_CONDITION_LINES_TL_U1, status:VALID,
-
INDEX: OKC.OKC_CONDITION_LINES_TL_U1
12.2.2
owner:OKC, object_type:INDEX, object_name:OKC_CONDITION_LINES_TL_U1, status:VALID,
-
TABLE: OKC.OKC_CONDITION_LINES_TL
12.1.1
owner:OKC, object_type:TABLE, fnd_design_data:OKC.OKC_CONDITION_LINES_TL, object_name:OKC_CONDITION_LINES_TL, status:VALID,
-
TABLE: OKC.OKC_CONDITION_LINES_TL
12.2.2
owner:OKC, object_type:TABLE, fnd_design_data:OKC.OKC_CONDITION_LINES_TL, object_name:OKC_CONDITION_LINES_TL, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
eTRM - OKC Tables and Views
12.1.1
description: Intersection entity between templates and rules. ,
-
eTRM - OKC Tables and Views
12.2.2
description: Intersection entity between rules and templates ,