Search Results oks_k_defaults




Overview
Explore in AI Chat

Overview

The OKS_K_DEFAULTS table is a core data object within the Oracle E-Business Suite Service Contracts (OKS) module. It functions as a repository for predefined values that automate and standardize the creation of service contracts. Specifically, it holds the default settings applied during two critical business processes: the renewal of an existing service contract and the generation of a new service contract from a sales order. The table supports a flexible defaulting mechanism by distinguishing between "Master" defaults (CDT_TYPE = 'MDT') and "Segmented" defaults (CDT_TYPE = 'SDT'), allowing for both broad and granular control over the attributes populated in the resulting contract.

Key Information Stored

The table's primary purpose is to map default values to specific contract attributes. Its structure is defined by key columns that establish relationships and specify the defaults. The primary key is the ID column, uniquely identifying each default record. The CDT_TYPE column is fundamental, classifying the record as a Master or Segmented default. Critical foreign key columns, such as CGP_NEW_ID and CGP_RENEW_ID, link to the OKC_K_GROUPS_B table to specify the default contract templates (groups) for new contracts and renewals, respectively. Other significant columns include PDF_ID, which references a default process definition (OKC_PROCESS_DEFS_B), QCL_ID for a default quality checklist (OKC_QA_CHECK_LISTS_B), and JTOT_OBJECT_CODE, which ties the defaults to a specific object type in the JTF_OBJECTS_B table, enabling object-specific defaulting rules.

Common Use Cases and Queries

The primary use case is the automated application of business rules during contract generation. For instance, when a user initiates a renewal, the application queries this table based on the original contract's attributes to find the appropriate default template, process, and checklist to apply to the renewed contract. A common reporting need is to audit all configured defaulting rules. A sample query to list Master defaults and their associated templates would be:

  • SELECT d.id, d.cdt_type, g_new.name new_template, g_renew.name renew_template FROM oks_k_defaults d, okc_k_groups_b g_new, okc_k_groups_b g_renew WHERE d.cgp_new_id = g_new.id(+) AND d.cgp_renew_id = g_renew.id(+) AND d.cdt_type = 'MDT';

Technical consultants may also query this table to diagnose issues where contracts are being created with unexpected default values, tracing the problem back to a specific record in OKS_K_DEFAULTS.

Related Objects

OKS_K_DEFAULTS is centrally connected to several key tables via foreign key constraints, as documented in the ETRM. These relationships are critical for its functionality:

  • OKC_K_GROUPS_B: Linked twice via CGP_NEW_ID and CGP_RENEW_ID to provide the default contract templates for new contracts and renewals.
  • JTF_OBJECTS_B: Linked via JTOT_OBJECT_CODE to associate defaults with a specific E-Business Suite object type.
  • OKC_PROCESS_DEFS_B: Linked via PDF_ID to define a default business process (workflow) for the contract.
  • OKC_QA_CHECK_LISTS_B: Linked via QCL_ID to assign a default quality assurance checklist.

The table's primary key constraint is OKS_K_DEFAULTS_PK on the ID column, ensuring the uniqueness of each defaulting rule.