Results for “cgp_renew_id”

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

Overview

OKS_K_DEFAULTS is a Service Contracts (OKS) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the default value sets applied when a service contract is renewed or when a service contract is created directly from an order. Each row describes a defaulting rule that determines which contract group, process definition, quality checklist, price list, payment terms, billing profile, and renewal behavior are proposed to the user or applied automatically during contract authoring.

The table distinguishes between two rule categories through the CDT_TYPE column. A "Master" default (CDT_TYPE = 'MDT') applies broadly to qualifying contracts, whereas a "Segmented" default (CDT_TYPE = 'SEG') targets a specific combination of segments identified by SEGMENT_ID1 and SEGMENT_ID2. This two-tier structure allows administrators to define a general fallback rule while refining behavior for selected customer, product, or organizational segments.

The documented primary key is OKS_K_DEFAULTS_PK, defined on the ID column, which is also exposed through the unique index OKS_K_DEFAULTS_U1. From a Data Vault modeling perspective, the metadata's heuristic classification is link: the table primarily exists to associate reference entities—contract groups, process definitions, checklists, price lists, and payment terms—with a defaulting rule context. Treating it as a link with descriptive satellite attributes is a reasonable modeling suggestion, since many of its 58 columns are non-key contextual attributes rather than independent business entities.

Key Information Stored

The most significant columns fall into several functional groups:

• ID — Surrogate primary key (OKS_K_DEFAULTS_PK, unique index OKS_K_DEFAULTS_U1). No separate alphanumeric business key is documented; the unique index is on the same surrogate column.
• CDT_TYPE — Rule category, either 'MDT' (Master) or segmented.
• SEGMENT_ID1 / SEGMENT_ID2 — Segment qualifiers that scope a segmented defaulting rule.
• CGP_NEW_ID / CGP_RENEW_ID — Contract groups applied when a contract is newly created versus renewed (FK to OKC_K_GROUPS_B).
• PDF_ID — Process definition driving contract lifecycle events (FK to OKC_PROCESS_DEFS_B).
• QCL_ID — Quality check list applied during validation (FK to OKC_QA_CHECK_LISTS_B).
• JTOT_OBJECT_CODE — JTF object code identifying the source object, notably the order entity when contracts originate from order lines (FK to JTF_OBJECTS_B).
• PRICE_LIST_ID1 / PRICE_LIST_ID2, RENEWAL_PRICING_TYPE, MARKUP_PERCENT, PRICE_UOM — Pricing defaults for new and renewed contracts.
• PAYMENT_TERMS_ID1 / PAYMENT_TERMS_ID2, PAYMENT_METHOD, BILLING_PROFILE_ID — Financial and billing defaults.
• RENEWAL_TYPE, PERIOD_TYPE, PERIOD_START, GRACE_PERIOD, GRACE_DURATION — Renewal timing and evergreen behavior.
• START_DATE / END_DATE — Effective dating of the defaulting rule.
• SECURITY_GROUP_ID — Multi-org/security grouping (FK to FND_SECURITY_GROUPS).
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, OBJECT_VERSION_NUMBER — Standard EBS audit and concurrency columns.

Common Use Cases and Queries

Typical scenarios include diagnosing why a contract received an unexpected default, auditing which rules are active for a given date, and reporting configuration coverage across segments.

• Retrieve all master defaults effective today:

  SELECT id, cdt_type, cgp_new_id, cgp_renew_id, pdf_id, price_list_id1
FROM oks.oks_k_defaults
WHERE cdt_type = 'MDT'
AND TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, SYSDATE);

• Locate segmented defaults for a specific segment pair:

  SELECT id, segment_id1, segment_id2, renewal_type, markup_percent
FROM oks.oks_k_defaults
WHERE cdt_type = 'SEG' AND segment_id1 = :seg1 AND segment_id2 = :seg2;

• Join to contract groups to describe default destinations:

  SELECT d.id, g.name
FROM oks.oks_k_defaults d, okc.okc_k_groups_b g
WHERE d.cgp_new_id = g.id;

• Reporting on renewal pricing posture across payment terms and price lists for governance or SOX reviews.
• Troubleshooting order-to-contract creation by filtering on JTOT_OBJECT_CODE to confirm the default rule is bound to the correct source object.

Related Objects

The table participates in several FK relationships that define its integration surface:

• OKC_K_GROUPS_B — joined via CGP_NEW_ID and CGP_RENEW_ID to resolve the contract groups applied to new and renewed contracts.
• OKC_PROCESS_DEFS_B — joined via PDF_ID for lifecycle process definitions.
• OKC_QA_CHECK_LISTS_B — joined via QCL_ID for validation checklists.
• JTF_OBJECTS_B — joined via JTOT_OBJECT_CODE to identify the source object type, particularly order entities.
• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID for row-level security and multi-org filtering.
• OKS_K_DEFAULTS_PK / OKS_K_DEFAULTS_U1 — the primary key constraint and unique index on ID, referenced by dependent child objects and used for direct row access when application code resolves a specific defaulting rule.

Together these relationships make OKS_K_DEFAULTS the central configuration link between the Service Contracts defaulting engine and the reference data that governs contract creation and renewal in Oracle EBS.