Results for “conversion_type_code”

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

Overview

OE_AK_CONVERSION_TYPES_V is a lightweight reporting view owned by the APPS schema in Oracle E-Business Suite, registered under the Order Management (ONT) product family. Its purpose is to expose the list of daily conversion type definitions maintained for Oracle General Ledger so that Order Management components, Oracle Application Framework (OAF) pages, and external integrations can present a user-friendly currency conversion type picklist without querying GL tables directly. The view has a status of VALID in both Oracle EBS 12.1.1 and 12.2.2.

The "AK" prefix in the name follows the Oracle Application Object Library naming convention used for attribute and key-flexfield style objects that typically supply lookup values to descriptive flexfields and OAF regions. This view is a common target when developers or functional users search for the term "user_conversion_type," since that string is the column most frequently referenced in custom queries, reports, and personalizations.

Underlying Base Objects

The view is defined over a single documented base object: GL_DAILY_CONVERSION_TYPES, accessed through its APPS.SYNONYM in the ETRM 12.2.2 metadata. GL_DAILY_CONVERSION_TYPES is the General Ledger table that stores every conversion type available to the ledger, such as "Spot," "Corporate," "User," and any custom conversion types defined by the implementation.

Because the view only references public columns from GL and performs no joins, it inherits the base table's row count (one row per enabled conversion type) and is fully dependent on GL setup. When a conversion type is added, renamed, or disabled in General Ledger, the view reflects that change immediately on the next query. No materialized or cached copy exists.

Key Columns

• CONVERSION_TYPE — although the view text selects the underlying column as CONVERSION_TYPE, the documented column list for the view exposes it as CONVERSION_TYPE_CODE. This is the internal, unique code for the conversion type and is the value normally stored on transactional records such as SO_HEADERS or GL journal lines.
• USER_CONVERSION_TYPE — the descriptive, user-facing name shown in list of values windows, OAF pages, and reports. This is the column callers most often filter or display when building a "conversion type" selection list.

In practice, CONVERSION_TYPE_CODE is the join key back to transactional tables, while USER_CONVERSION_TYPE is the value presented to end users. The pairing allows a single view to satisfy both stored-value lookups and display requirements.

Common Use Cases and Queries

Typical scenarios include populating a conversion type LOV in an OAF page or concurrent program, joining order or AR data to display a friendly conversion type name, and validating custom import files so that only valid, enabled conversion types are loaded.

-- List all available conversion types
SELECT conversion_type_code,
       user_conversion_type
  FROM   oe_ak_conversion_types_v
 ORDER BY user_conversion_type;

-- Resolve a stored code to its user name
SELECT user_conversion_type
  FROM   oe_ak_conversion_types_v
 WHERE  conversion_type_code = :p_conversion_type;

Because the view is read-only and defined entirely on GL_DAILY_CONVERSION_TYPES, it is suitable for reporting and validation work only; inserts, updates, and deletes must be performed against the base GL table or through the General Ledger setup forms. This keeps Order Management customizations aligned with the single source of truth for conversion types and avoids duplicate or inconsistent definitions.