Search Results mv_yn

Overview

OKI.OKI_REFRESHS is a table in the OKI (Contracts Intelligence / Oracle Knowledge and Information) schema that maintains operational metadata about the most recent refresh execution of tables and materialized views within the OKI product family. As documented in the ETRM metadata, the table holds "data about the latest run of a concurrent manager program which refreshed a table in OKI," and by design there is only one row per refreshed object. This makes OKI_REFRESHS a control and audit table rather than a transactional data store: it answers the question of when, by which concurrent request, and under which job run a given OKI object was last refreshed.

The table is classified as VALID and resides in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10. It carries no foreign key references outward beyond SECURITY_GROUP_ID pointing to FND_SECURITY_GROUPS, and the heuristic Data Vault classification derived from its key structure is standalone. In Data Vault modeling terms, this pattern suggests the table behaves as a satellite-like status record keyed by the refreshed object name, with no hub-and-link join topology of its own. It is a low-volume, high-value operational reference used by the OKI loaders to determine incremental refresh boundaries.

Key Information Stored

The table contains 14 documented columns. The most significant include:

• OBJECT_NAME (VARCHAR2, 60, mandatory) — the name of the refreshed OKI object; this is the natural business-key candidate, since the metadata states there is exactly one row per table.
• MV_YN (VARCHAR2) — flag indicating whether the refreshed object is a materialized view; this is the column matched by the user's "mv_yn" search and is central to distinguishing MV refreshes from ordinary table loads.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — standard Concurrent Manager audit columns identifying the concurrent request and program that performed the refresh.
• JOB_RUN_ID (NUMBER) — the job run identifier of the last incremental refresh, used to sequence and gate downstream incremental loads.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Who columns and row versioning attributes.
• SECURITY_GROUP_ID (NUMBER) — used for application hosting, with a documented foreign key to FND_SECURITY_GROUPS.

No explicit surrogate primary key column is documented; OBJECT_NAME functions as the de facto unique identifier. Object version tracking is provided by OBJECT_VERSION_NUMBER rather than a numeric PK.

Common Use Cases and Queries

Typical uses include auditing refresh history, diagnosing stale materialized views, and driving incremental load logic. A frequent query checks which objects are materialized views and when they last refreshed:

• SELECT OBJECT_NAME, MV_YN, JOB_RUN_ID, LAST_UPDATE_DATE FROM OKI.OKI_REFRESHS WHERE MV_YN = 'Y';
• Joining to FND_CONCURRENT_REQUESTS on REQUEST_ID to trace the concurrent program that performed the refresh.
• Filtering by SECURITY_GROUP_ID when operating in a multi-org or hosted context.
• Reporting on objects not refreshed within a threshold by comparing LAST_UPDATE_DATE against SYSDATE.

Related Objects

OKI_REFRESHS is referenced by several OKI loader packages that read refresh state before executing incremental loads:

• OKI_LOAD_ENR_PVT
• OKI_LOAD_ETR_PVT
• OKI_LOAD_FBO_PVT
• OKI_LOAD_OKV_PVT
• OKI_LOAD_RAG_PVT
• OKI_LOAD_RBK_PVT
• OKI_LOAD_RBS_PVT
• OKI_LOA (additional dependent object)
• FND_SECURITY_GROUPS — referenced via the SECURITY_GROUP_ID foreign key.

These dependencies confirm that OKI_REFRESHS acts as the shared refresh-state registry consumed across the OKI loading layer.