Search Results pa_mc_draft_inv_items

Overview

GL_DAILY_CONVERSION_TYPES is the Oracle General Ledger reference table that defines foreign currency daily conversion rate types in Oracle E-Business Suite 12.1.1 and 12.2.2. Each row represents a named rate type — such as Spot, Corporate, User, or EMU Fixed — that determines which rate from GL_DAILY_RATES is applied when a foreign currency transaction is converted, revalued, or translated. The table resides in the GL schema and is maintained at the application level through the Daily Rates and Conversion Rate Types setup forms.

Because almost every subledger transaction carries a rate type reference, this table functions as a central reference point for currency conversion throughout the EBS data model. In Data Vault terms, the mined foreign-key structure classifies GL_DAILY_CONVERSION_TYPES as a hub — a modeling suggestion consistent with its role as a stable, low-volume list of business keys (CONVERSION_TYPE) that is referenced by more than one hundred dependent tables. The table is registered as VALID under the GL product and is populated with seeded rate types during implementation.

Key Information Stored

The table contains 30 documented columns. The most significant are:

• CONVERSION_TYPE — the business key and single-column primary key (GL_DAILY_CONVERSION_TYPES_PK). Values such as Spot, Corporate, User, or user-defined codes identify the rate type.
• USER_CONVERSION_TYPE — the user-facing display name for the same rate type, backed by the unique index GL_DAILY_CONVERSION_TYPES_U2.
• DESCRIPTION — free-text explanation of the rate type’s intended usage.
• SECURITY_FLAG — indicates whether the rate type is restricted to specific users or responsibilities.
• FEM_ENABLED_FLAG, FEM_SCENARIO, FEM_RATE_TYPE_CODE, and FEM_TIMEFRAME — attributes introduced to map GL rate types to Enterprise Performance Foundation (FEM) rate-type codes and scenarios.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN — standard WHO audit columns tracking creation and modification.
• ATTRIBUTE1 through ATTRIBUTE15 and CONTEXT — the standard Oracle descriptive flexfield (DFF) columns for customer-defined attributes.
• ZD_EDITION_NAME — the editioning column supporting multiple ledger/edition definitions in the 12.2.2 architecture.

Two unique indexes are documented: GL_DAILY_CONVERSION_TYPES_U1 on (CONVERSION_TYPE, ZD_EDITION_NAME) and GL_DAILY_CONVERSION_TYPES_U2 on (USER_CONVERSION_TYPE, ZD_EDITION_NAME). The primary key should therefore be treated as the surrogate/business-key anchor, with edition-aware uniqueness enforced by these secondary indexes.

Common Use Cases and Queries

The most frequent application use is validating that a rate type exists and resolving its user-facing name for display. A typical join from a subledger table to the rate type definition looks like:

• SELECT inv.invoice_num, inv.exchange_rate_type, g.user_conversion_type, g.description FROM ap_invoices_all inv, gl_daily_conversion_types g WHERE inv.exchange_rate_type = g.conversion_type;
• Reporting rate types that are used as ledger default translation, period-average, or period-end rates: SELECT led.name, led.daily_translation_rate_type, led.period_end_rate_type, led.period_average_rate_type FROM gl_ledgers led;
• Identifying rate types configured with FEM integration: SELECT conversion_type, fem_enabled_flag, fem_rate_type_code FROM gl_daily_conversion_types WHERE fem_enabled_flag = 'Y';

Common scenarios include troubleshooting a revaluation or translation failure caused by a missing rate for a given rate type, auditing which default rate types are assigned in AP, PO, or GL system parameters, and building currency-conversion audit reports that trace each foreign transaction back to its rate-type definition.

Related Objects

Because the table is a hub, dependencies are numerous. The most significant referencing objects, with their actual join columns, are:

• GL_DAILY_RATES via CONVERSION_TYPE — holds the actual daily rates stored against each rate type.
• GL_LEDGERS via DAILY_TRANSLATION_RATE_TYPE, PERIOD_AVERAGE_RATE_TYPE, and PERIOD_END_RATE_TYPE — defines the default rate types per ledger.
• GL_JE_HEADERS via CURRENCY_CONVERSION_TYPE — records the rate type used on each journal entry.
• AP_INVOICES_ALL via EXCHANGE_RATE_TYPE and PAYMENT_CROSS_RATE_TYPE — invoice-level rate type defaults.
• AP_SYSTEM_PARAMETERS_ALL via DEFAULT_EXCHANGE_RATE_TYPE — Payables system defaults.
• PO_HEADERS_ALL via RATE_TYPE and PO_SYSTEM_PARAMETERS_ALL via DEFAULT_RATE_TYPE — Purchasing defaults and documents.
• GL_CROSS_RATE_RULES via CONVERSION_TYPE — cross-rate rule definitions.
• CE_STATEMENT_LINES via EXCHANGE_RATE_TYPE — Cash Management bank statement conversion.
• GL_REVALUATIONS via CONVERSION_RATE_TYPE — revaluation rate-type assignments.
• PA_BUDGET_LINES, PA_EXPENDITURE_ITEMS_ALL, and other Projects tables — multiple project cost and revenue rate-type columns.

These references confirm that GL_DAILY_CONVERSION_TYPES is a foundational currency setup table. Deletion or renaming of a rate type in use will be blocked by these foreign keys, so changes should be managed through the application forms rather than direct DML.