Results for “oks_process_control”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The OKS_PROCESS_CONTROL table is a control and tracking object owned by the OKS schema, the schema that underpins the Oracle Service Contracts module in Oracle E-Business Suite. Its documented purpose is narrow and operational: it stores the execution statistics of SQL script files so that the EBS patching infrastructure can determine whether a given script has already been applied. When a SQL file is designed to run only once during a patch or upgrade, the application consults this table to verify the prior execution state before running it again. This makes OKS_PROCESS_CONTROL a lightweight idempotency guard rather than a functional business entity.

In heuristic Data Vault terms, the table is classified as standalone, which suggests modeling it as an independent satellite or reference structure rather than as a hub or link. This classification is consistent with its role: it does not participate in transactional relationships, it carries no meaningful foreign keys other than a security context, and it exists purely to record whether a processing step has occurred.

Key Information Stored

The documented physical schema in ETRM 12.2.2 exposes three columns, all of which are relevant to its operation:

• FILENAME – The name of the SQL file or script whose execution is being tracked. This is the principal business-key candidate, since the identity of the process step is defined by the file being run.
• PROCESSFLAG – A flag column indicating the processing state or completion status of the associated file. In practice this acts as the gate that the patching driver reads to decide whether a script should be skipped.
• SECURITY_GROUP_ID – The security group context, which references FND_SECURITY_GROUPS. This column supports the multi-org and security-group model used throughout EBS.

No surrogate primary key column is documented among the three attributes, indicating that uniqueness, where enforced, is likely driven by FILENAME in combination with the security context rather than a system-generated sequence. The absence of a documented surrogate key reinforces the table's nature as a control record set rather than a normalized master entity.

Common Use Cases and Queries

The primary use case is diagnostic: during patch troubleshooting, a DBA or technical consultant queries the table to confirm whether a one-time SQL file has already been processed, which explains why a script may have been silently skipped during an upgrade.

A typical verification query would resemble:

• SELECT filename, processflag, security_group_id FROM oks.oks_process_control WHERE filename LIKE '&script_name%';

Reporting use cases include auditing which Service Contracts setup or data-migration scripts have executed within a given environment, particularly after applying OKS-related patches or family packs. Because the table is small and updated only by administrative processes, it should never be truncated or modified manually; attempting to reset a PROCESSFLAG to force a script to rerun can cause duplicate data if the original script was not truly idempotent. Cross-environment comparison of FILENAME and PROCESSFLAG values is a useful practice when reconciling behavior between development, test, and production instances.

Related Objects

The documented relationship data is limited, with a single foreign key defined:

• FND_SECURITY_GROUPS – referenced via the SECURITY_GROUP_ID column, providing the security-group context for each control row.

Beyond this explicit relationship, the table is referenced operationally by the AD patching and upgrade driver utilities that consult it before invoking one-time SQL scripts. Related functional objects in the OKS schema, such as the core Service Contracts transaction tables, are not joined to this table, since it serves no business reporting purpose. Practitioners typically treat OKS_PROCESS_CONTROL alongside other schema-level process control tables that share the same FILENAME / PROCESSFLAG pattern, and it should be understood as an infrastructure artifact rather than a source of contract data.