Search Results okc_assents




Overview
Explore in AI Chat

Overview

The OKC_ASSENTS table is a core configuration table within the Oracle E-Business Suite Contracts Core module (OKC). It functions as a rule engine that governs permissible business operations for specific contract subclasses based on their current status. Essentially, it defines the workflow by answering a critical question: "Is a particular operation allowed for a given contract subclass when that contract is in a specific status?" This table is fundamental to enforcing business logic and maintaining data integrity throughout the contract lifecycle, from creation through amendment to termination.

Key Information Stored

The table acts as a junction, storing associations between three key entities: contract subclass, status, and operation. While the full column list is not detailed in the provided metadata, the foreign key relationships explicitly identify the critical columns that form the composite key for these associations. The primary columns are SCS_CODE (linking to the contract subclass in OKC_SUBCLASSES_B), STS_CODE (linking to the status in OKC_STATUSES_B), and OPN_CODE (linking to the operation code). The STE_CODE column, referenced alongside OPN_CODE in a foreign key, likely indicates a sub-type or context for the operation. A typical implementation would also include an ID column (the primary key) and a flag or indicator column (e.g., ALLOWED_FLAG) to explicitly permit or prohibit the operation for the given subclass-status combination.

Common Use Cases and Queries

The primary use case is the validation of user actions within the Contracts application. For instance, before the system allows a user to "Amend" a "Standard Sales" contract that is currently in an "Approved" status, it will query OKC_ASSENTS to check if this operation is permitted. A common reporting need is to audit or review the defined workflow rules. A sample query to list all permitted operations for a subclass would be:

  • SELECT scs.code subclass_code, sts.code status_code, opn.code operation_code
  • FROM okc_assents ass, okc_subclasses_b scs, okc_statuses_b sts, okc_included_operations opn
  • WHERE ass.scs_code = scs.code AND ass.sts_code = sts.code AND ass.opn_code = opn.code
  • AND ass.allowed_flag = 'Y';

Administrators may also query this table to troubleshoot why a specific action button is disabled in the application interface.

Related Objects

OKC_ASSENTS is centrally linked to three key reference tables via foreign key constraints, forming the backbone of the Contracts workflow configuration:

  • OKC_SUBCLASSES_B: Defines the contract types (e.g., Sales, Procurement, Lease). Joined via OKC_ASSENTS.SCS_CODE = OKC_SUBCLASSES_B.CODE.
  • OKC_STATUSES_B: Defines the lifecycle statuses a contract can hold (e.g., Draft, In Process, Signed, Active). Joined via OKC_ASSENTS.STS_CODE = OKC_STATUSES_B.CODE.
  • OKC_INCLUDED_OPERATIONS: Defines the list of possible operations or actions (e.g., Create, Amend, Terminate, Copy). Joined via the composite key OKC_ASSENTS.STE_CODE, OPN_CODE = OKC_INCLUDED_OPERATIONS.STE_CODE, CODE.

The primary key constraint OKC_ASSENTS_PK on the ID column ensures each rule association is uniquely identifiable.