Search Results oks_status_forecast




Overview
Explore in AI Chat

Overview

The OKS_STATUS_FORECAST table resides in the OKS schema and belongs to the Service Contracts module of Oracle E-Business Suite. Its documented purpose is the storage of service forecast details — aggregated, point-in-time snapshots of contract bookings, contract value, revenue-recognition value, and forecast value that are produced when a forecasting concurrent program is executed against the service contract population. In Oracle EBS 12.1.1 and 12.2.2 the table therefore acts as a reporting and analysis staging area: rather than recomputing contract financial projections on demand, the application materializes them into rows that can be queried, compared across runs, and exported to downstream reporting tools.

From a dimensional modeling perspective, the ETRM heuristic Data Vault classification for this object is standalone. It carries no outbound foreign keys to other business entities and is not itself referenced as a parent, so it does not behave as a hub, link, or satellite. The most appropriate modeling interpretation is that of a periodic snapshot fact table, where each row represents a measured state of the service contract portfolio at the moment a forecast run was executed.

Key Information Stored

The table is documented with twelve columns. The most significant groupings are as follows.

  • Forecast measurement columns — CONTRACT_VALUE, REV_REC_VALUE, and FORECAST_VALUE hold the monetary amounts for the contract portfolio, recognized revenue, and projected forecast respectively. NUMBER_OF_CONTRACTS captures the count of contracts contributing to the row. BOOKING_FORECAST identifies the booking-oriented forecast measure.
  • Run identification columns — RUN_FLAG and RUN_TIME record whether a given forecasting run is the active/current one and when it was executed. CONC_REQUEST_ID ties the row to the concurrent request that generated it, enabling traceability back to the program log and parameters through FND_CONCURRENT_REQUESTS.
  • Categorization columns — STATUS_TYPE and STATUS_CODE classify the summarized records (for example, by contract or line status), while CURRENCY documents the currency in which the monetary columns are expressed.
  • Security column — SECURITY_GROUP_ID supports multi-tenant and operating-unit level data isolation.

No surrogate primary key is documented in the supplied metadata beyond the column list; the row is best treated as a composite of the run identifier and status categorization. Because the classification is standalone, no business-key unique index is asserted.

Common Use Cases and Queries

Typical usage centers on extracting the latest forecast run for management reporting, comparing current and prior runs, and validating that a concurrent program completed successfully.

  • Retrieve the active forecast: SELECT STATUS_TYPE, STATUS_CODE, CURRENCY, NUMBER_OF_CONTRACTS, CONTRACT_VALUE, REV_REC_VALUE, FORECAST_VALUE FROM OKS.OKS_STATUS_FORECAST WHERE RUN_FLAG = 'Y';
  • Trace a run back to its concurrent request: join CONC_REQUEST_ID to FND_CONCURRENT_REQUESTS.REQUEST_ID to obtain submission time, requesting user, and completion phase.
  • Trend forecast value across runs by grouping on RUN_TIME and CURRENCY.
  • Feed downstream revenue or booking dashboards by joining currency to FND_CURRENCIES and status codes to the appropriate OKS status lookup.

Related Objects

  • FND_SECURITY_GROUPS — the sole documented foreign key, joined on SECURITY_GROUP_ID, controlling row-level access.
  • FND_CONCURRENT_REQUESTS — joined via CONC_REQUEST_ID to identify the concurrent program run that populated the row.
  • OKS_CONTRACTS (and the OKS contract header/line family) — the source entities whose values are summarized into the forecast columns.
  • FND_CURRENCIES — resolves the CURRENCY column for display and conversion.
  • OKS service contract reporting views referenced by the Service Contracts dashboard, which consume the latest RUN_FLAG = 'Y' snapshot.