Search Results pa_conversion_types_v




Overview

PA_CONVERSION_TYPES_V is a public Oracle E-Business Suite view owned by the APPS schema and classified under the Projects (PA) product family. It exposes the set of daily conversion rate types defined in Oracle General Ledger so that they can be referenced from Projects functionality and from custom reporting, extensions, and integrations that require a validated list of conversion rate types. The view is documented in the ETRM repository with a VALID status in the 12.1.1 and 12.2.2 releases and is present as a synonym-based wrapper over a General Ledger object.

In an EBS context, the view functions as a lightweight pass-through that presents conversion rate type information without requiring the calling application or report to query GL_DAILY_CONVERSION_TYPES directly. This is consistent with the standard EBS design pattern in which the Projects module references GL-owned reference data through APPS-owned views rather than through direct access to the GL base tables. The view therefore plays a supporting role in currency conversion processing for project accounting, where rate types such as Spot, Corporate, User, and any user-defined types are required when translating amounts between currencies.

Underlying Base Objects

The documented base object for PA_CONVERSION_TYPES_V is GL_DAILY_CONVERSION_TYPES, referenced in the ETRM metadata as a SYNONYM. The view text is a simple select from that object:

Because the view performs no joins, filters, or aggregations, it inherits the row set of the underlying conversion type definition table and mirrors its contents one-for-one. There is no additional PA-specific logic embedded in the view; its purpose is to surface the GL conversion type definitions within the Projects namespace. Any change made to conversion rate types in General Ledger — for example, adding a user-defined rate type — is immediately reflected through this view without any additional synchronization.

Key Columns

The view exposes three columns, each corresponding directly to a column on GL_DAILY_CONVERSION_TYPES:

  • USER_CONVERSION_TYPE — The user-facing name of the conversion rate type. This is the value typically displayed on forms, reports, and concurrent program parameters where a rate type must be selected or printed.
  • CONVERSION_TYPE — The internal code for the conversion rate type. This is the value typically stored in transactional and setup tables and used in joins and lookups.
  • DESCRIPTION — The descriptive text associated with the conversion rate type, used for reporting and for disambiguation where multiple rate types share similar short names.

Because both the user-facing name and the internal code are exposed, the view supports both display-oriented reporting and code-driven lookups. For example, a report can display USER_CONVERSION_TYPE while storing or matching on CONVERSION_TYPE, and a lookup query can return DESCRIPTION to populate a descriptive flexfield or a value set.

Common Use Cases and Queries

Typical uses include populating value sets for concurrent program parameters, validating rate type values in custom PL/SQL, building LOVs in custom forms or OAF pages, and generating ad hoc reports that require the list of available conversion rate types alongside project currency conversion activity.

A simple query to list all available conversion rate types is:

  • SELECT USER_CONVERSION_TYPE, CONVERSION_TYPE, DESCRIPTION FROM APPS.PA_CONVERSION_TYPES_V ORDER BY USER_CONVERSION_TYPE;

A more targeted query, retrieving the code and description for a single rate type by name, might read:

  • SELECT CONVERSION_TYPE, DESCRIPTION FROM APPS.PA_CONVERSION_TYPES_V WHERE USER_CONVERSION_TYPE = :p_rate_type;

Because the view is a direct projection of the GL conversion type table, it should be used where a read-only, validated list of rate types is required. It is not intended for insert, update, or delete operations; maintenance of conversion rate types is performed in General Ledger, and the view simply reflects the resulting definitions within the Projects reporting and integration layer.