Results for “standard_notes_id”

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

Overview

OKE_K_STANDARD_NOTES_TL is the translation (multi-lingual) table for contract standard notes within the OKE – Project Contracts module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. Standard notes are reusable, predefined text blocks that project contract authors insert into contract documents, terms, and clauses, allowing organizations to enforce consistent contractual language across engagements. Because Oracle EBS is deployed in multi-language environments, the descriptive and textual content of these notes is segregated into a "_TL" table that stores one row per language, while language-independent attributes reside in the base table.

From a Data Vault modeling perspective, the mined FK structure classifies this object as satellite-leaning. It behaves as a descriptive satellite attached to the base entity OKE_K_STANDARD_NOTES_B: the base table holds the durable business key and non-translatable attributes, while this table carries the language-dependent descriptive payload keyed by both the parent identifier and the language code.

Key Information Stored

The table is owned by the OKE schema and comprises twelve documented columns. The essential columns are:

• STANDARD_NOTES_ID – Surrogate identifier of the parent standard note; part of the primary key and the FK to OKE_K_STANDARD_NOTES_B.
• LANGUAGE – Language code of the translated row; the second component of the primary key and of the unique index.
• NAME – The translatable short name/label of the standard note as presented to users in the selected language.
• DESCRIPTION – The translatable description used to identify the note in list-of-values and inquiry screens.
• TEXT – The actual contract-standard-note body text that is copied into contract documents for this language.
• SOURCE_LANG – The source language from which the row was originally created or translated.
• SFWT_FLAG – The standard "Seed/Forward/Whatever Translation" flag used by Oracle's translation tooling.
• CREATION_DATE, CREATED_BY – Standard audit columns recording row creation.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – Standard audit columns recording the most recent change.

The primary key OKE_K_STD_NOTES_TL_PK is defined on (STANDARD_NOTES_ID, LANGUAGE). A unique index, OKE_K_STD_NOTES_TL_U1, covers the same column pair and serves as the business-key candidate for modelers refining the Data Vault design.

Common Use Cases and Queries

Typical uses include retrieving standard-note text in a user's session language for contract authoring, auditing which languages a note has been translated into, and validating translation completeness. A representative join retrieves both base and translated attributes:

SELECT b.standard_notes_id, t.language, t.name, t.description, t.text
FROM oke.oke_k_standard_notes_b b, oke.oke_k_standard_notes_tl t
WHERE b.standard_notes_id = t.standard_notes_id
AND t.language = USERENV('LANG');

Reporting patterns often filter on SOURCE_LANG or SFWT_FLAG to isolate untranslated or seeded rows, and use LAST_UPDATE_DATE to identify recently modified clauses. Because the table is a "_TL" object, always constrain by LANGUAGE in queries to avoid returning multiple rows per note.

Related Objects

• OKE_K_STANDARD_NOTES_B – The base table holding language-independent standard-note attributes; joined via STANDARD_NOTES_ID.
• OKE_K_STD_NOTES_TL_PK / OKE_K_STD_NOTES_TL_U1 – Primary key and unique index on (STANDARD_NOTES_ID, LANGUAGE).
• OKE_K_STANDARD_NOTES_TL – Self-referenced FK structure defining the parent relationship to the base table.
• Contract standard note assignment tables in the OKE schema, which consume STANDARD_NOTES_ID to attach notes to contracts and contract templates.
• OKE contract authoring/API components that read translated note text at document generation time.