Results for “aso_i_gl_conv_types_v”

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

Overview

ASO_I_GL_CONV_TYPES_V is an APPS-owned database view in the Oracle E-Business Suite Order Capture (ASO) product family. Its documented purpose is to retrieve the valid currency conversion types defined in General Ledger, exposing them to the Order Capture module for use during order import, pricing, and multi-currency processing. The view is registered as a VALID object in both EBS 12.1.1 and 12.2.2 and is classified as a read-only reporting and integration view.

The view does not store data. It is a thin projection over the General Ledger conversion type master, which makes it a lightweight, low-overhead access point for ASO components and for external integrations that need to enumerate or validate conversion types without querying the GL schema directly. Because it belongs to the APPS schema and carries no filtering predicate, it returns every conversion type row present in GL, which means the row count is governed entirely by the configuration of the underlying GL table.

Underlying Base Objects

Per the ETRM documentation, the view is defined over a single referenced base object: GL_DAILY_CONVERSION_TYPES, accessed through a SYNONYM. GL_DAILY_CONVERSION_TYPES is the General Ledger master table for daily conversion rates, holding one row per conversion rate type such as Spot, Corporate, User, and any custom types defined by the implementation.

The view text is documented as:

• SELECT CONVERSION_TYPE, USER_CONVERSION_TYPE FROM GL_DAILY_CONVERSION_TYPES

There are no joins, WHERE clauses, or inline functions in the definition. The relationship between the view and its base object is therefore strictly one-to-one and column-projected: every row and every value returned by the view originates from GL_DAILY_CONVERSION_TYPES without transformation. Any change to the GL conversion type setup is immediately visible through the view, since no materialization or caching layer intervenes.

Key Columns

• CONVERSION_TYPE — The internal, language-independent identifier for the conversion rate type. This is the value typically stored on transactional and setup records, and it is the column normally used in joins and equality predicates.
• USER_CONVERSION_TYPE — The user-facing, translatable name of the conversion type as displayed in the application. This is the value a user would recognize from the GL setup form.

Both columns are copied directly from GL_DAILY_CONVERSION_TYPES. The pairing supports the common EBS pattern of separating a stable internal code from a display label, and it allows reporting queries to return a friendly description while filtering or joining on the internal code.

Common Use Cases and Queries

The view is most frequently used when an Order Capture inquiry or an integration needs to present or validate the set of available conversion types. Typical scenarios include populating a conversion type list of values in a custom order entry screen, validating a conversion type value supplied through an interface table during order import, and joining conversion types to order or pricing records to produce readable reports.

To retrieve all available conversion types:

• SELECT CONVERSION_TYPE, USER_CONVERSION_TYPE FROM APPS.ASO_I_GL_CONV_TYPES_V ORDER BY USER_CONVERSION_TYPE;

To resolve the display name for a specific conversion type code:

• SELECT USER_CONVERSION_TYPE FROM APPS.ASO_I_GL_CONV_TYPES_V WHERE CONVERSION_TYPE = :p_conversion_type;

To verify that a value coming from an inbound interface is a valid GL conversion type before processing:

• SELECT COUNT(*) FROM APPS.ASO_I_GL_CONV_TYPES_V WHERE CONVERSION_TYPE = :p_interface_value;

Because the view is a direct projection with no filters, it should not be expected to return only conversion types relevant to a specific operating unit or order capture context. Callers requiring such restriction must apply their own predicates or join to the appropriate setup tables.