Search Results okc_included_operations




Overview
Explore in AI Chat

Overview

The OKC_INCLUDED_OPERATIONS table is a core setup and validation table within the Oracle E-Business Suite Contracts Core (OKC) module. Its primary function is to define the permissible business operations for a given contract status, thereby enforcing a rules-based workflow. This table acts as a junction or mapping table, linking status types (STE_CODE) to allowed operations (OPN_CODE). It is fundamental to the application's integrity, ensuring that users can only perform actions appropriate to a contract's current lifecycle stage, such as preventing the approval of a contract that is still in a draft status.

Key Information Stored

The table's structure is concise, centered on the relationship between two key codes. The primary key is a composite of the STE_CODE and OPN_CODE columns, ensuring a unique mapping. The STE_CODE column stores the status type code, which references statuses defined in related tables. The OPN_CODE column stores the operation code, which corresponds to specific business actions or functions defined within the OKC_OPERATIONS_B table. This simple two-column structure effectively governs the complex business logic of contract state transitions.

Common Use Cases and Queries

A primary use case is validating user actions within the Contracts UI. When a user attempts an operation, the application queries this table to verify if the OPN_CODE is permitted for the contract's current STE_CODE. System administrators and functional implementers use this table during configuration to define the operational workflow for custom contract types. Common reporting queries involve listing all allowed operations for a specific status or identifying which statuses permit a critical operation like termination. A sample query to retrieve all operations allowed for a 'DRAFT' status would be:

  • SELECT i.opn_code, o.name FROM okc_included_operations i, okc_operations_b o WHERE i.opn_code = o.code AND i.ste_code = 'DRAFT';

Related Objects

This table is centrally connected to other key OKC entities. It has a foreign key relationship to OKC_OPERATIONS_B, which defines the master list of all possible operations (OPN_CODE). It also has a foreign key relationship, via the composite of STE_CODE and OPN_CODE, to the OKC_ASENTS table, which appears to be involved in assent or agreement tracking. The table's primary purpose is to feed validation logic into the core Contracts engine, influencing the behavior of APIs and UI flows throughout the module whenever a status change or operational action is initiated.