Results for “order_type_desc”

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

Overview

The table GML.OP_ORDR_TYP_TL is the translation table for order type codes and descriptions within the Oracle E-Business Suite Process Manufacturing Logistics (GML) module. It stores language-specific (translated) values for order type attributes, using Oracle's standard multi-language translation table pattern where the _TL suffix denotes a translation-enabled entity. Each row corresponds to a single order type in a single installed language, meaning a given order type can have one row per language seeded in the EBS instance. This table is only relevant in a multi-language environment; single-language implementations store their order type text directly in the corresponding base table.

In heuristic Data Vault terms, mined from the foreign key structure, the object is classified as standalone (neither a hub, link, nor satellite in a strict sense), since it carries no documented outgoing FK relationships to other entities. It is best modeled as a descriptive or reference/translation satellite: the composite key (ORDER_TYPE, LANGUAGE) forms a durable business key, and the descriptive text columns change over time, making the row itself a slow-changing descriptive record. This classification should be treated as a modeling suggestion rather than a prescriptive design.

Key Information Stored

The documented physical schema (ETRM 12.2.2) exposes ten columns. The most significant are grouped below.

• ORDER_TYPE — part of the composite primary key; the order type identifier whose translated content the row carries.
• LANGUAGE — the second component of the composite primary key; identifies the installed language (for example, US for American English) in which the translated fields are rendered.
• ORDER_TYPE_CODE — the short code value for the order type, typically the same across languages or the language-neutral business identifier.
• ORDER_TYPE_DESC — the translated long description of the order type, which varies by LANGUAGE and is the primary text users consume.
• SOURCE_LANG — the source language from which the translation originated, used by Oracle Translation Manager to track the linguistic origin of the row.
• CREATED_BY, CREATION_DATE — standard audit columns recording the user and timestamp of row insertion.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns recording the most recent change, its timestamp, and the login session that performed it.

The surrogate primary key is OP_ORDR_TYP_TL_PK defined on the composite of ORDER_TYPE and LANGUAGE. In this table that composite is simultaneously the business-key candidate, since the unique index is built on the same two columns. There is no separate numeric surrogate identifier documented. The ten-column footprint confirms this is a narrow reference table, not a transaction-bearing entity.

Common Use Cases and Queries

The most frequent use is retrieving the translated description of an order type for display, reporting, or integration payloads. A typical query joins the base order type table to OP_ORDR_TYP_TL and filters on the session or profile language:

• Language lookup: SELECT ORDER_TYPE_CODE, ORDER_TYPE_DESC FROM GML.OP_ORDR_TYP_TL WHERE LANGUAGE = :session_lang.
• Missing-translation detection: compare the set of ORDER_TYPE values in the translation table against the base table, grouped by LANGUAGE, to find untranslated rows.
• Audit reporting: segment LAST_UPDATED_BY and LAST_UPDATE_DATE to identify which translations were maintained and when.
• Multi-language reconciliation: pivot ORDER_TYPE_DESC by LANGUAGE to validate consistent terminology across locales.
• Data migration and extraction: pull all translation rows matching a seed of ORDER_TYPE_CODE values when promoting configurations between environments.

Because the table is standalone with no documented FKs, queries should always constrain on LANGUAGE to avoid returning duplicate-looking rows for the same order type in multiple languages.

Related Objects

The metadata documents no foreign key relationships for this table, so dependencies are largely functional rather than referential. The significant related objects are:

• OP_ORDR_TYP_B or the equivalent base order type table — the language-neutral parent holding authoritative ORDER_TYPE values; join on ORDER_TYPE.
• FND_LANGUAGES — validates and decodes LANGUAGE values into installed language names; join on LANGUAGE or LANGUAGE_CODE.
• FND_APPLICATION — identifies the GML application context for the seeded order type reference data.
• GML Process Manufacturing Logistics order-entry and shipping UI pages and concurrent programs that consume OP_ORDR_TYP_TL for translated drop-downs.
• Oracle Translation Manager and its underlying staging tables, which populate SOURCE_LANG and the translated descriptive columns.