Results for “okc_report_sql_tl_pk”

6 results




Overview
Explore in AI Chat

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

Overview

OKC_REPORT_SQL_TL is a translation (TL) table within the OKC — Contracts Core module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It supports the Contract Printing framework, specifically the reporting infrastructure that generates contract documents through XML output. The table stores help text describing the XML structure produced by the XSUtility based on an underlying report query; this help text is consumed primarily by XSL writers who author the transformation stylesheets that render contract output.

From a heuristic Data Vault modeling perspective, the metadata classifies this object as standalone. Because it carries the descriptive, language-dependent attributes (NAME, HELP_TEXT) attached to a report SQL identifier, it is best modeled as a satellite rather than a hub or link. The business key (ID, LANGUAGE) is preserved locally, and the table does not participate in a parent-child FK chain of its own beyond the security group reference.

Key Information Stored

The table is defined in the OKC schema with 12 documented columns. The most significant are:

  • ID — Surrogate identifier for the report SQL definition; part of the composite primary key OKC_REPORT_SQL_TL_PK and of the unique index OKC_REPORT_SQL_TL_U1.
  • LANGUAGE — Language code of the translated row; the second component of the primary key and unique index.
  • NAME — The translated display name associated with the report SQL record.
  • HELP_TEXT — The core payload: descriptive guidance about the XML structure generated by XSUtility from the query, used by XSL writers.
  • SOURCE_LANG — The source language from which the translation was derived (standard EBS MLD convention).
  • SFWT_FLAG — The "Seed/Force/Whatever Translation" flag controlling whether the row is treated as a seed translation during language installation and upgrade.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS WHO columns recording audit and concurrency information.
  • SECURITY_GROUP_ID — References FND_SECURITY_GROUPS, supporting multi-organization/multi-tenant security partitioning.

The business-key candidate is the unique index OKC_REPORT_SQL_TL_U1 on (ID, LANGUAGE), which mirrors the primary key and enforces one translated row per report SQL identifier per language. The primary key is therefore both the surrogate and the language-scoped access path. A secondary functional index, SYS_IL0000169931C00004$$, is system-generated, typically associated with a LOB or functional index on the HELP_TEXT column.

Common Use Cases and Queries

Typical usage centers on retrieving help text for contract printing configuration and on auditing translation coverage.

  • Fetching help text for a given report SQL identifier: SELECT name, help_text FROM okc.okc_report_sql_tl WHERE id = :id AND language = USERENV('LANG');
  • Listing available languages for a report: SELECT language FROM okc.okc_report_sql_tl WHERE id = :id;
  • Identifying rows with missing translations: compare against the base (non-TL) report SQL table on ID.
  • Reporting on untranslated or stale seed rows by filtering on SFWT_FLAG.
  • Administering security partitioning via SECURITY_GROUP_ID joins to FND_SECURITY_GROUPS.

These queries are most often embedded in contract printing setup screens, XSL authoring utilities, and translation completeness reports.

Related Objects

  • FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID; join on okc_report_sql_tl.security_group_id = fnd_security_groups.security_group_id.
  • OKC_REPORT_SQL_B / OKC_REPORT_SQL — the base (non-translated) report SQL definition table, joined on ID, providing the query and XML generation metadata.
  • OKC_REPORT_SQL_TL_PK / OKC_REPORT_SQL_TL_U1 — the primary key constraint and unique index enforcing (ID, LANGUAGE) uniqueness.
  • FND_LANGUAGES — join on LANGUAGE to resolve language names for reporting.
  • FND_APPLICATION / FND_PRODUCT_INSTALLATIONS — context for the OKC product ownership.
  • XSUtility / XML Publisher components — consume the HELP_TEXT content indirectly through the contract printing pipeline.

Because the metadata classifies the object as standalone, no dependent child tables inherit its primary key; it functions as a descriptive satellite within the contract printing subsystem.