Search Results oe_payment_types_tl_u1

Overview

The ONT.OE_PAYMENT_TYPES_TL table is a translation (MLS) table within the Oracle Order Management (ONT) schema. It stores the language-specific name and description for each payment type defined in Oracle E-Business Suite Release 12.1.1 and 12.2.2. The base transactional definition of payment types resides in the associated non-translated table (OE_PAYMENT_TYPES_B), while this table holds the translatable attributes required for multi-language support. The _TL suffix and the SOURCE_LANG and LANGUAGE columns confirm its role in the EBS Multi-Lingual Support (MLS) architecture.

Payment types are seeded lookup values that drive sales order payment terms, credit card processing, and receivables integration. Because the values are frequently displayed to end users in different operating languages, the translation table is essential for presenting a consistent localized experience.

From a heuristic Data Vault modeling perspective, this object is classified as standalone. It does not participate in foreign-key relationships to other transactional hubs or links as a dependent satellite; instead it functions as an independent reference/seed table keyed by business identifiers.

Key Information Stored

The table contains 16 documented columns. The most significant are:

• PAYMENT_TYPE_CODE (VARCHAR2, 30) — The lookup code referencing lookup type OE_PAYMENT_TYPE. This is the business key that links the translation to the base payment type definition.
• ORG_ID (NUMBER) — The Operating Unit owning the payment type record, enabling multi-org data segregation.
• LANGUAGE (VARCHAR2) — The language of the MLS columns for this row.
• SOURCE_LANG (VARCHAR2) — The language in which the seed data was originally created.
• NAME (VARCHAR2, 240) — The localized name of the payment type shown to users.
• DESCRIPTION (VARCHAR2, 2000) — The localized description providing additional clarification.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns tracking insert and update attribution.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, REQUEST_ID, PROGRAM_UPDATE_DATE — Concurrent program WHO columns identifying the request and program that last modified the row.
• ZD_EDITION_NAME — The editioning column present in 12.2.2 for Online Patching (EBR) support, documented in the unique index OE_PAYMENT_TYPES_TL_U1.

The documented primary key is OE_PAYMENT_TYPES_TL_PK (PAYMENT_TYPE_CODE, ORG_ID, LANGUAGE). The unique index OE_PAYMENT_TYPES_TL_U1 (the object the user searched for) covers PAYMENT_TYPE_CODE, ORG_ID, LANGUAGE, ZD_EDITION_NAME, reinforcing the business-key composition plus the editioning discriminator introduced in 12.2.2. Unlike a surrogate ID-based primary key, this design uses natural business columns as the key, which is typical of seed and lookup translation tables.

Common Use Cases and Queries

Typical usage involves joining the translation table to the base table to retrieve the localized display name for a given payment type and operating unit:

• Localized lookup validation: Retrieve NAME and DESCRIPTION for a specific payment type in a user's language.
• Reporting: Produce payment-type reference listings used in order-entry and receivables reports.
• Data migration and seeding: Load custom or additional payment types with their translations.
• Troubleshooting untranslated rows: Detect missing translations where a row exists in the base table but not in the desired LANGUAGE.

A representative query pattern joins ONT.OE_PAYMENT_TYPES_TL to the base definition, filtering on ORG_ID, PAYMENT_TYPE_CODE, and LANGUAGE, and optionally constraining ZD_EDITION_NAME or SOURCE_LANG for completeness checks.

Related Objects

• OE_PAYMENT_TYPES_B — The base (non-translated) table; joined on PAYMENT_TYPE_CODE and ORG_ID.
• ONT.OE_PAYMENT_TYPE lookup type — The FND lookup type that governs valid PAYMENT_TYPE_CODE values.
• FND_CONCURRENT_PROGRAMS — Referenced by PROGRAM_ID for last-update attribution.
• FND_CONCURRENT_REQUESTS — Referenced by REQUEST_ID.
• FND_APPLICATION — Referenced by PROGRAM_APPLICATION_ID.
• FND_LANGUAGES — Source of valid LANGUAGE and SOURCE_LANG values for MLS rows.
• OE_ORDER_HEADERS_ALL / OE_ORDER_LINES_ALL — Order entities whose payment terms ultimately reference payment types.

Together these objects position OE_PAYMENT_TYPES_TL as a critical, if narrow, MLS reference table supporting localized payment-type presentation across Order Management and Receivables in EBS 12.1.1 and 12.2.2.