Search Results oki_wip_by_customers




Overview
Explore in AI Chat

Overview

OKI_WIP_BY_CUSTOMERS is a table belonging to the OKI (Contracts Intelligence) product family within Oracle E-Business Suite. Its documented purpose is to hold information about renewals by customer for a given period, effectively capturing work-in-progress forecasting and booked-versus-lost amounts recorded against customer parties within an authoring organization for a specific accounting period. This places the table in the contract renewal analytics space, where periodic snapshots of forecast, booked, and lost base amounts are aggregated by customer and by sales compensation or service code.

The ETRM documentation classifies the product module as "OKI - Contracts Intelligence (Obsolete)," and record-level implementation notes confirm the object is "Not implemented in this database." In Oracle EBS 12.1.1 and 12.2.2, this indicates the table is a legacy Contracts Intelligence (OKI) schema object that is not created by the standard installation of those releases. It is documented for reference and migration analysis rather than for active transactional use.

Mined from its foreign key structure, the heuristic Data Vault classification for this table is standalone. From a dimensional modeling perspective, this suggests it behaves as a satellite-style fact container keyed by a surrogate identifier, with no subordinate hub-and-link dependencies other than the security group reference. Analysts should treat it as a self-contained period snapshot rather than a normalized master-data hub.

Key Information Stored

The table is documented with 17 physical columns in the OKI schema. The most significant are:

Two unique indexes define business-key candidates: OKI_WIP_BY_CUSTOMERS_U1 covers (PERIOD_NAME, PERIOD_SET_NAME, CUSTOMER_PARTY_ID, AUTHORING_ORG_ID, SCS_CODE), making this the natural grain of the table; OKI_WIP_BY_CUSTOMERS_U2 covers the surrogate ID.

Common Use Cases and Queries

Because the table is obsolete and not implemented in 12.1.1 or 12.2.2, its primary use cases are historical reporting, migration validation, and gap analysis when comparing legacy Contracts Intelligence data against current EBS renewal reporting. Typical queries select the period and customer grain and compare forecast against booked and lost amounts to compute renewal win/loss ratios:

  • Renewal attainment by customer: sum BASE_BOOKED_AMOUNT grouped by CUSTOMER_PARTY_ID and PERIOD_NAME.
  • Forecast variance analysis: BASE_FORECAST_AMOUNT minus BASE_BOOKED_AMOUNT less BASE_LOST_AMOUNT by AUTHORING_ORG_ID.
  • Period-over-period trending by joining PERIOD_NAME to GL period definitions or FND calendars.
  • Security-scoped extracts filtered on SECURITY_GROUP_ID, joined to FND_SECURITY_GROUPS.

A representative pattern joins the business-key unique index columns to resolve the natural grain, then aggregates the base amounts. Data lineage checks should reference REQUEST_ID against concurrent request history.

Related Objects

The documented relationship data identifies the following significant dependencies:

  • FND_SECURITY_GROUPS — referenced via OKI_WIP_BY_CUSTOMERS.SECURITY_GROUP_ID, providing the multi-tenant security grouping.
  • OKI_WIP_BY_CUSTOMERS_PK — the primary key constraint on ID.
  • OKI_WIP_BY_CUSTOMERS_U1 — the unique business-key index on PERIOD_NAME, PERIOD_SET_NAME, CUSTOMER_PARTY_ID, AUTHORING_ORG_ID, and SCS_CODE.
  • OKI_WIP_BY_CUSTOMERS_U2 — the unique index on ID.

Additional OKI Contracts Intelligence sibling tables (renewal, forecast, and organization-level snapshots) are the likely companion objects within the same legacy schema, joined on PERIOD_NAME, PERIOD_SET_NAME, and AUTHORING_ORG_ID. Because the object is marked obsolete and unimplemented, no active APIs or views are documented as depending on it in 12.1.1 or 12.2.2.