Results for “op_prsl_typ_tl”

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

Overview

OP_PRSL_TYP_TL is a translation (TL) table owned by the GML schema, belonging to the Process Manufacturing Logistics module within Oracle E-Business Suite. Its name identifies it as the language-dependent translation table for presales order types, with the base table being OP_PRSL_TYP_B. In the Oracle EBS multilingual architecture, _TL tables store descriptive, translatable attributes (such as names and descriptions) in each installed language, while language-independent attributes remain in the corresponding _B table. The ETRM metadata records an important caveat: this table is not used in 11i, meaning its usage is confined to Release 12.x environments, specifically the 12.1.1 and 12.2.2 releases referenced in this context. The user search term "presales_ord_type" maps directly to the primary key column PRESALES_ORD_TYPE, confirming that this object stores the translated text associated with presales order type codes for process manufacturing presales transactions.

The metadata's heuristic Data Vault classification lists this object as standalone. In modeling terms, a translation table such as this functions most naturally as a satellite attached to the presales order type hub, since it holds descriptive, language-versioned attributes keyed by the business identifier plus a language discriminator. The standalone classification reflects the absence of foreign key constraints in the documented FK structure rather than an absence of logical relationships.

Key Information Stored

The table is documented with ten columns. The primary key is defined by the OP_PRSL_TYP_TL_PK index, composed of the composite business key PRESALES_ORD_TYPE and LANGUAGE. PRESALES_ORD_TYPE identifies the presales order type, while LANGUAGE is the Oracle language code (for example, US or JA) that discriminates each translated row. Because the PK is a business composite rather than a generated surrogate, there is no separate system-generated identifier column.

• PRESALES_ORD_TYPE — the business key identifying the presales order type; part of the composite primary key.
• LANGUAGE — the language code for the translated row; the second component of the composite primary key.
• PRESALES_ORD_CODE — the coded value or short name of the presales order type.
• PRESALES_ORD_DESC — the translated descriptive text for the presales order type, typically the primary user-facing value.
• SOURCE_LANG — the source language from which the translation was derived, used by the translation framework to track origin language.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS WHO columns capturing audit and concurrency information for the row.

Common Use Cases and Queries

The principal use case is resolving the language-specific description of a presales order type for display in forms, reports, and presales order entry screens. A typical query joins the translation table with the language environment or uses the current session language:

• Lookup by code: SELECT presales_ord_desc FROM op_prsl_typ_tl WHERE presales_ord_type = :type AND language = USERENV('LANG');
• Reporting all translations: SELECT presales_ord_type, language, presales_ord_desc FROM op_prsl_typ_tl ORDER BY presales_ord_type, language;
• Validating completeness: query for order types lacking a translation in a required language, a common data-quality check after implementation or patching.
• Integration extracts: supplying multilingual descriptions to downstream presales or order management reporting.

Related Objects

The following objects are most significant in relation to this table:

• OP_PRSL_TYP_B — the base table holding language-independent presales order type attributes; joined on PRESALES_ORD_TYPE.
• OP_PRSL_TYP_TL_PK — the unique index enforcing the composite business key (PRESALES_ORD_TYPE, LANGUAGE).
• FND_LANGUAGES — the language definition table; joined on LANGUAGE to resolve language names.
• OP_PRSL and related presales transaction tables in GML — reference presales order types as lookup values.
• FND_TERRITORIES and standard EBS WHO audit conventions — provide context for language and audit columns.

Because the FK classification is standalone, joins to these objects are driven by the PRESALES_ORD_TYPE and LANGUAGE business keys rather than enforced referential constraints, and report authors should treat the relationships as logical rather than database-enforced.