Search Results ce_currency_rates_temp




Overview

CE_CURRENCY_RATES_TEMP is a transient staging table within the Oracle Cash Management (CE) module of Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as a forecast currency amount staging area, holding intermediate exchange rate and currency conversion data generated during cash forecasting and cash positioning processing. The table is owned by the CE schema and is registered as VALID in the EBS data dictionary.

The table captures per-request currency conversion inputs prior to final aggregation into forecast result tables. Because rows are tied to a specific forecast request, the contents are typically short-lived and are cleared or regenerated each time a forecast run executes.

From a heuristic Data Vault modeling perspective, the mined FK structure classifies CE_CURRENCY_RATES_TEMP as standalone. In Data Vault terms this suggests the object behaves as an isolated staging construct rather than a conventional hub, link, or satellite. There is no documented foreign key dependency joining it to a parent business entity, so any downstream model should treat it as a load-time work table whose rows are scoped by the forecast request that produced them.

Key Information Stored

The documented physical schema for 12.2.2 contains four columns. All are listed below because the column set is small; the most significant are highlighted first.

  • FORECAST_REQUEST_ID — Identifier of the forecast execution that owns the staged rows. This is part of the composite primary key and is the principal scoping column for every query against the table.
  • CURRENCY_CODE — The source currency being converted. Part of the composite primary key.
  • TO_CURRENCY — The target (functional or reporting) currency into which the source amount is converted. Part of the composite primary key.
  • EXCHANGE_RATE — The conversion rate applied between CURRENCY_CODE and TO_CURRENCY for the given request.

The unique primary key is CE_CURRENCY_RATES_TEMP_U1, defined over (FORECAST_REQUEST_ID, CURRENCY_CODE, TO_CURRENCY). This composite key is the natural business key: it guarantees one rate row per request per currency pair and enforces uniqueness at the staging grain. There is no separate single-column surrogate key documented; the composite key itself serves as the identifier. No FK-based business-key candidate beyond this index is reported in the metadata.

Common Use Cases and Queries

Typical usage centers on diagnosing currency conversion behavior in cash forecasting. Analysts query the table to confirm which rates were applied to a given forecast request before results were aggregated into the permanent forecast tables.

  • Inspecting all rates captured for a specific run: SELECT currency_code, to_currency, exchange_rate FROM ce_currency_rates_temp WHERE forecast_request_id = :request_id;
  • Isolating a single currency pair: filter by CURRENCY_CODE and TO_CURRENCY to verify that the expected rate was sourced correctly.
  • Detecting missing conversions: compare distinct currency pairs present here against the currencies expected in the source forecast data, flagging pairs that never received a staged rate.
  • Reconciliation reporting: join staged rates to forecast result tables on FORECAST_REQUEST_ID to explain variances that arise from rate application rather than from underlying cash flows.

Because rows are request-scoped and transient, reporting patterns generally anchor on a single FORECAST_REQUEST_ID rather than performing broad historical analysis. Persistent trend reporting should rely on the final forecast tables, not on this staging object.

Related Objects

The 2.2 metadata documents no outgoing foreign keys, consistent with its standalone classification, so related objects are inferred from the cash forecasting flow rather than from declared referential constraints.

  • CE_FORECAST_REQUESTS — Parent request record; join on FORECAST_REQUEST_ID to associate staged rates with a forecast run.
  • CE_FORECASTS and the forecast results tables — consume the converted amounts produced from these staged rates.
  • CE_FORECAST_TEMP — Sibling staging table holding forecast cash flow lines for the same request.
  • GL_DAILY_RATES — the underlying rate source from which EXCHANGE_RATE values are derived.
  • FND_CURRENCIES — validates CURRENCY_CODE and TO_CURRENCY values against defined ISO currencies.

Together these objects form the currency conversion segment of the Cash Management forecast pipeline, with CE_CURRENCY_RATES_TEMP acting as the short-lived intermediate store between rate lookup and final forecast output.