Search Results oe_payment_types




Overview
Explore in AI Chat

Overview

APPS.OE_PAYMENT_TYPES_VL is a translated (VL, "view with translations") dictionary view in Oracle E-Business Suite that exposes Order Management payment type definitions together with their language-specific descriptive text. It is built on the intersection of the OE_PAYMENT_TYPES base (non-translated) table and the OE_PAYMENT_TYPES_TL translation table. The view is owned by the APPS schema and is available in both Oracle EBS 12.1.1 and 12.2.2. Its primary role is to present payment type setup data — code, effective dates, enabled status, credit check and deferral flags, and associated receipt method — alongside the current session's translated NAME and DESCRIPTION, so that forms, concurrent programs, and integration layers read a single, language-aware record rather than joining the base and translation tables manually.

Underlying Base Objects

Per the ETRM view definition, the view is a SELECT over two synonyms referenced by the APPS schema:

  • OE_PAYMENT_TYPES (synonym to the base table) — supplies operational columns such as PAYMENT_TYPE_CODE, ORG_ID, date and flag attributes, and Who columns. This is the physical source of the payment type setup records.
  • OE_PAYMENT_TYPES_TL (synonym to the translation table) — supplies NAME and DESCRIPTION per language, keyed by payment type code and organization.

The join predicate is B.PAYMENT_TYPE_CODE = T.PAYMENT_TYPE_CODE AND B.ORG_ID = T.ORG_ID AND T.LANGUAGE = USERENV('LANG'). The USERENV('LANG') condition restricts output to the language of the current session, which is the defining behavior of a _VL view: it materializes a single-language row per base record. Because the base table is secured by Org ID, the view is typically accessed through Multi-Org or MOAC (Multi-Org Access Control) security in R12.

Key Columns

Common Use Cases and Queries

Typical uses include validating payment type setup, populating LOVs in Order Management forms, and driving integrations/lookups that require the translated name. Because of the language restriction, USERENV('LANG') must resolve correctly for the expected translation to appear.

To list enabled payment types for the current operating unit:

  • SELECT payment_type_code, name, description, enabled_flag, credit_check_flag FROM apps.oe_payment_types_vl WHERE org_id = :p_org_id AND enabled_flag = 'Y' AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE + 1);

To link a payment type to its receipt method:

  • SELECT v.payment_type_code, v.name, v.receipt_method_id FROM apps.oe_payment_types_vl v WHERE v.org_id = :p_org_id ORDER BY v.payment_type_code;

To surface flexfield attributes for extending setup reporting:

  • SELECT payment_type_code, name, context, attribute1, attribute2 FROM apps.oe_payment_types_vl WHERE org_id = :p_org_id;

Queries should always be constrained by ORG_ID (or run under MOAC) to respect operating-unit security and to avoid cross-organization duplication.