Search Results oe_payment_types_tl_pk

Overview

OE_PAYMENT_TYPES_TL is the translation table for payment types within the Oracle Order Management (ONT) module. It resides in the ONT schema and stores the language-specific name and description for each payment type defined in Oracle E-Business Suite. In a multilingual implementation, the base table OE_PAYMENT_TYPES_B holds the language-independent attributes of a payment type, while OE_PAYMENT_TYPES_TL supplies the translated text values keyed by LANGUAGE. This separation allows a single payment type to carry distinct display names and descriptions across every installed language without duplicating operational data.

From a heuristic Data Vault modeling perspective, the mined relationship data classifies this object as standalone, meaning no foreign key dependencies were detected in the documented FK structure. In Data Vault terms, this table would most naturally be modeled as a satellite attached to a payment-type hub, since it carries descriptive, language-qualified attributes (NAME, DESCRIPTION) that are dependent on the payment type business key rather than representing an independent business entity or an associative link.

Key Information Stored

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

• PAYMENT_TYPE_CODE — the business identifier for the payment type; part of the composite primary key.
• ORG_ID — the operating unit (organization) context; part of the primary key, enabling payment types to be defined per organization.
• LANGUAGE — the ISO language code identifying which translation row applies; part of the primary key.
• NAME — the translated display name shown to users for the payment type.
• DESCRIPTION — the translated descriptive text for the payment type.
• SOURCE_LANG — the language from which the translation was derived, used by the translation framework.
• ZD_EDITION_NAME — the editioning column introduced in EBS 12.2 for online patching; it participates in the unique index OE_PAYMENT_TYPES_TL_U1.

The surrogate primary key is defined by constraint OE_PAYMENT_TYPES_TL_PK over (PAYMENT_TYPE_CODE, ORG_ID, LANGUAGE). A second unique index, OE_PAYMENT_TYPES_TL_U1, covers (PAYMENT_TYPE_CODE, ORG_ID, LANGUAGE, ZD_EDITION_NAME) and serves as the business-key candidate under editioning. The remaining documented columns are standard WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and concurrent-program context columns (PROGRAM_APPLICATION_ID, PROGRAM_ID, REQUEST_ID, PROGRAM_UPDATE_DATE).

Common Use Cases and Queries

Typical usage involves resolving the translated label for a payment type in a given operating unit and language, and joining translations back to the base table for reporting.

SELECT t.payment_type_code,
       t.name,
       t.description
FROM   ont.oe_payment_types_tl t
WHERE  t.org_id   = :org_id
AND    t.language = USERENV('LANG');

Reporting scenarios include listing all payment types with their localized names for a specific operating unit, auditing which languages have been translated for a given code, and reconciling translations against the base table. A common join pattern is:

SELECT b.payment_type_code,
       t.name
FROM   ont.oe_payment_types_b b,
       ont.oe_payment_types_tl t
WHERE  b.payment_type_code = t.payment_type_code
AND    b.org_id            = t.org_id
AND    t.language          = 'US';

Related Objects

• OE_PAYMENT_TYPES_B — the base (language-independent) payment type table; joins on PAYMENT_TYPE_CODE and ORG_ID.
• OE_PAYMENT_TYPES_VL — the translation view exposing base and translated columns together.
• OE_PAYMENT_TYPES_TL — related to order headers and payment schedules that reference payment types at the order level (e.g., OE_ORDER_HEADERS_ALL).
• FND_LANGUAGES — reference for valid LANGUAGE values.
• HR_OPERATING_UNITS / FND_ORG — reference for ORG_ID resolution.

Rows are maintained through Order Management setup and the standard translation framework rather than direct DML, and any query should filter by LANGUAGE and ORG_ID to return meaningful results.